hello, I am looking for a way to reuse dm-migrations for the dm-hibernate- adapter. but the code is too tightly bound to dm-XYZ_DB-adapter: dm- sqlite-adapter, dm-mysql-adapter, dm-postgres-adapter and any adapter which carry the word "sqlite:, "mysql", "postgres" in its adaper name.
with the dm-hibernate-adapter which is the same adapter for all DBs this naming convention just fails badly in any case. but dm-hibernate-adapter makes only sense if it offers a drop in replacement to the do-adapters. but without migrations that is not the case. "drop in" also means that if I have both dm-mysql-adapter and dm- hibernate-adapter in my local rubygems than I would like to switch back and forth with just changing DataMapper.setup - the rest should remain as is. first I though I just create a dm-hibernate- migrations.gem as well dm-hibernate-constraints.gem BUT that might not really coexist nicely with dm-migrations.gem as well dm- constraints.gem - maybe it does . . . it just feels nicer just to use dm-migrations.gem I guess. I really would appreciate if someone could look at the patch http://github.com/mkristian/dm-migrations/commit/fd551c0eab221501d633a2305b3649dde0c240ce I have not look into dm-constraints yet but we need this soon too. and I am about add hsqldb support for dm-migrations since these pure java DBs are just a nice alternative to sqlite. regards Kristian -- You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en.
