Dear Group, I may be mistaken, but I find I'll have to set some low level mysql table-level settings. Unfortunately, the current property list for a table doesn't appear to support the following:
ENGINE = InnoDB (or does dm fake transaction support?) Just don't want to be tripping on toes here. CHARACTER SET seems its utf8 by default, but: COLLATE I'll need to set to 'utf8_bin' (or it messes up some german strings) *prior* to adding string columns. AVG_ROW_LENGTH, and MAX_ROWS I'll have to set on large deployments or I'll run into a file size limitation. I'm still digging into sqlite3 and postgres, but I'm pretty sure they don't have these quirky bits to their configurations. Unfortunately, your properties do not appear to allow me to set these for migrations. It would be helpful to be able to set an adapter-specific property with all these kinds of things so I can be assured it will operate within the desired requirements. I'm digging around with dm-migrations to attempt to overcome all this. Any advice anyone has to share on the subject (particulary if they've already invented the wheel here) would be appreciated and welcome. Thanks for your time, G. Gibson --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
