StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
647876
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-03-15T14:19:25.537
FavoriteCount
0
LastActivityDate
2009-03-15T14:25:49.313
LastEditDate
2009-03-15T14:25:49.313
LastEditorUserId
78259
OwnerUserId
78259
ParentId
647781
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
Chas. Owens
text
Body
<a href="http://oreilly.com/catalog/9780596001735/" rel="noreferrer">Perl Best Practices</a> warns against exactly what you want. It states that config files should be simple and avoid the sort of baroque features you desire. It goes on to recommend three modules (none of which are Core Perl): <a href="http://search.cpan.org/dist/Config-General/General.pm" rel="noreferrer">Config::General</a>, <a href="http://search.cpan.org/dist/Config-Std/lib/Config/Std.pm" rel="noreferrer">Config::Std</a>, and <a href="http://search.cpan.org/dist/Config-Tiny/lib/Config/Tiny.pm" rel="noreferrer">Config::Tiny</a>. The general rational behind this is that the editing of config files tends to be done by non-programmers and the more complicated you make your config files, the more likely they will screw them up. All of that said, you might take a look at <a href="http://www.yaml.org/" rel="noreferrer">YAML</a>. It provides a full featured, human readable<code>*</code>, serialization format. I believe the currently recommend parser in Perl is <a href="http://search.cpan.org/dist/YAML-LibYAML/lib/YAML/XS.pm" rel="noreferrer">YAML::XS</a>. If you do go this route I would suggest writing a configuration tool for end users to use instead of having them edit the files directly. ETA: Based on Chris Dolan's answer it sounds like YAML is the way to go for you since Catalyst is already using it (.yml is the de facto extension for YAML files). <code>*</code> I have heard complaints that blind people may have difficulty with it
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat's the best Perl module for hierarchical and inheritable configuration?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USChas. Owens
UserOwnerUserId
1. USChas. Owens
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTDownMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.