Sorry this isn't an answer to the posted question.
How will you handle field constraints such as primary key, foreign key, auto increment (not a true constraint), unique key, check, and other constraints? I am not away of much useful SQL that doesn't have at least some constraints.
Can you abstract it so that you have a well defined data structure, then you can spit out SQL? This would allow you to store your SQL as not just INI, but YAML, JSON, Storable, and possibly XML simple.
I'm sorry if you already address these issues in your module's documentation.
If you have abstracted things, then I'd say that the module names ending in INI might be good - but then you may want something like
- SQL::CreateTable
- SQL::CreateTable::INI
- SQL::CreateTable::YAML
With a name like this, you could have SQL::CreateTable do the hard work of translating data structure to schema and vice versa. The ::INI and other variants then are used by SQL::CreateTable to serialize to file based on the extention of the filename, or by passing in a parameter.
my @a=qw(random brilliant braindead); print $a[rand(@a)];