On 11/15/06 10:42 PM, Jonathan wrote: > That said, supporting MySQL is a good thing to do. BUT since rose > tends to focus people on doing stuff more intelligently, I would > suggest that the "SET" support require people to set a global > Rose::DB variable ( $Rose::DB::enable_mysql_set = 1; ) in order for > it to work right -- and the documentation on that would post a notice > to people that using a SET/ENUM value will lock you into a Mysql > specific database, and that your code would be more portable if you > used a normalized data structure that is portable.
The thing is, ENUM is pretty easily emulated in other databases (with a varchar and a check constraint) and SET exists in at least one other database (Informix). I think requiring a special flag var to be set is pretty user-hostile. Also, when porting from MySQL to other databases, enum and set columns are the least of your problems... -John ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
