Thanks. So just curious, is this because of some design philosophy, or it's just because you just haven't got time to do it. If so, I can try to help by submit a patch to you after I made the change.
Thanks Yi On Fri, Sep 12, 2008 at 7:38 PM, Jeremy Evans <[EMAIL PROTECTED]>wrote: > > On Sep 12, 11:08 am, Yi Wen <[EMAIL PROTECTED]> wrote: > > When I declare a schema, I want to use "string", not "varchar" for > > create a varchar type. The reason is I want to keep my code to be > > database independent (mysql should map string to VARCHAR(255), while > > ORACLE should map string to VARCHAR2(255), for example). > > > > Poking around the source code, I found out a TYPES hash in the code > > can be used, but it's almost empty. Am I supposed to build my own > > TYPES hash according to different DBMS? or there is some configuration > > I can do? > > Sequel doesn't make much of an attempt to convert data types. Other > than converting double to double precision, it just gives the database > what you give it. To do what you want, you'll want to override > Database#type_literal in each database subclass you want to support. > > Jeremy > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
