Mister, > 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.
Greg Campbell committed some fixes in dm-more that will make it into the next gem release: http://github.com/datamapper/dm-more/commit/ba9e29e13ffa506978530b729cd615e2e3d52a70 NOTE: To use edge dm-more, you'll also need the edge versions of dm- core, DO, and extlib. The tables will all be created with InnoDB. The character set and collation are determined by your connection settings. With do_mysql I believe you can specify the :encoding option when setting up your connection, but I do not think there is a way to specify the collation yet. You may want to look at MySQL's docs to see if there's a way to configure the default collation in the my.cnf. I'm sure there is, I've never found anything I wasn't able to configure that way. > AVG_ROW_LENGTH, and MAX_ROWS I'll have to set on large deployments or > I'll run into a file size limitation. DM and DO don't have ways to configure these options. For these you will need to consult the MySQL config docs. -- Dan (dkubb) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
