Chris, > Thanks, it's really weird, because UTF8 is what MySQL uses in table > definitions etc:
In general we would use Ruby's own conventions as authoritative not any one specific database. > Changing to utf-8, or UTF-8 (with or without quotes) produces a crash in > ActiveRecord instead of a warning from DO: Are you using the same database.yml for DataMapper as for ActiveRecord? If so, I would probably recommend against that.. there are likely to be differences here and there, and we don't make any strong claims to provide backwards compatible support for ActiveRecord syntax. (i.e. we try to use similar names when it is the best name possible, but if they're using something for legacy reasons or there's a better name then we don't hesitate to break compatibility) > Using UTF8 (without the hypen, in uppercase) produces the warning, but Rails > starts successfully. Oh, so you haven't disabled ActiveRecord? I'm trying to understand how your app is setup and why you would be getting this error. > With regards to DataObjects vs. DataMapper, excuse my ignorance, but are they > not all part of the same group of projects? They all come under the > data-mapper github account and seem to have the same contributors. They started life together, but they are distinct projects and can be used independently of each other. -- Dan -- 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.
