On Dec 5, 12:42 am, Joe Van Dyk <[EMAIL PROTECTED]> wrote: > Hi, > > I'm used to being able to do this in rails-land: > add_column :some_table :some_date, :datetime > > And have that be a timestamp in postgres and a datetime in mysql. > > However, sequel complains about there not being a datetime datatype in > postgres (which there isn't). > > Am I missing something obvious? I don't want to use the timestamp > data type in mysql.
No, Sequel doesn't translate types. Technically, that's only mostly true, as you'll see if you look at the code.. I'm not opposed to adding a more generic translation ability, but I don't plan to work on it myself. Feel free to send in a patch or pull request with the appropriate specs and I'll consider it. 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 -~----------~----~----~----~------~----~------~--~---
