On Oct 16, 10:48 pm, mdub <[EMAIL PROTECTED]> wrote: > I've been happily using Sequel database migrations to evolve my > schema. Up until now we've just targeted Oracle, but I'm now looking > at getting the app running on another DBMS, too (PostgreSQL, most > likely). > > It doesn't look like Sequel makes any attempt to translate the column > types used in migrations, ie. there's no type abstraction. Am I > right, or did I miss something? Has it been intentionally omitted to > reduce complexity, or is it simply the case that no-one's put the > effort in yet?
You are correct. No one has put in the effort. I don't need the functionality, so it isn't something I plan to work on. I'd be willing to accept patches that implemented it, as long as they didn't break backwards compatibility. > How would you suggest I create migrations that can be run on multiple > DBMSs? Currently, it shouldn't be too hard if you use mostly standard SQL. If you have to use a certain column type on one database and a different column type on another database, you should be able to check the database adapter class and act accordingly. Generally, if you only use cross platform SQL features, writing cross platform migrations shouldn't be too difficult. If you have a specific case you'd like to discuss, I'm all ears. 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 -~----------~----~----~----~------~----~------~--~---
