All,
Coming up with good meaningful names seems to be harder than writing the code. I am writing a class that given an INI style configuration file representing a DB schema will build that DB.
[TABLE1]
FIELD1 = INTEGER
FIELD2 = TEXT
Due to reasons beyond my control, I am stuck with this implementation. I understand the limitations and I also understand existing prior art. Suggestions for alternatives, while appreciated, are futile. With that in mind, can you offer a good meaningful namespace?
Suggestions from the CB (thanks Corion, castaway, and rhesa ) include:
- Schema::Description::Ini
- SQL::Translator::FromINI
- SQL::Translator::INI
- SQL::CreateStatement::FromIni
- SQL::Translator::Producer::INI
- SQL::Schema::FromINI
- DBIx::Schema::FromINI
While the implementation is being forced by in-house politics, I don't expect there would be any resistance in releasing the code. If there is any interest in that, let me know.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.