Re: RFC: Name and/or API for module ("Type::FromData")

The first practical problem I run into with this module is that the user really isn't free to choose any name for a field -- in your example the use of 'when' in unacceptable in PostgreSQL. Perhaps some kind of target setting like 'forMYSQL' or 'forPostgres' would generate some kind of error when a reserved word is utilized for a field name (or maybe munge it with something to make it acceptable).

Second, I would prefer to be able to override the regexes that define what a particular thing is -- a date, a numeric type, or a string -- with my own regexes.

Third, some RDBMS allow for custom data types to be defined. This module should have some allowance for those.

Otherwise I think this module is a good idea. The name seems okay. I would slap some pod into it and give it a very low version number.

BTW, this line is wrong:

$dt->guess( @$data );
[download]

Should be,

$dt->guess( @data );
[download]

Celebrate Intellectual Diversity

Comment on Re: RFC: Name and/or API for module ("Type::FromData") Select or Download Code

Replies are listed 'Best First'.
Re^2: RFC: Name and/or API for module ("Type::FromData") by Corion (Patriarch) on Apr 09, 2014 at 20:42 UTC
Indeed - I have thought about extensibility and the SQL dialects, but I really think those should come after there is some generic type definition instead of strings getting passed around. But I don't want to write the code for the generic data type myself :)	[reply]
Re^2: RFC: Name and/or API for module ("Type::FromData") by chacham (Prior) on Apr 10, 2014 at 18:48 UTC
WHEN is not a good name as it is a keyword in the CASE statement.	[reply]


Think about Loose Coupling
	PerlMonks