dc, You should create a ticket for this in http://datamapper.lighthouseapp.com/
In the ticket please include your OS/Ruby/MySQL version, and your DM/ Merb gems with versions using: gem list '\A(?:d[mo]|merb)\b' Also if your project is open source, then please include a link to the repository. > i went through upgrading datamapper today, and now get the following > errors booting a merb app: > > Mysql Error 500 > This connection has already been closed You should look in the logs to if any SQL query is executed consistently prior to the connection being closed. Just yesterday we were discussing ticket #457 (http://is.gd/9TGU) and how the MySQL connection is closed when there's an error. (we're not sure, but we believe this is probably incorrect behavior and are following up with the original author) This could be related to your problem, perhaps there's a query that is executing each time on startup that has an error and is causing the connection to be closed. > we are also using: > dm-polymorphic-0.9.6 > > (0-9-7 does not exist) > > could this be root of a problem? Maybe, but I don't know for sure. Sometimes its good to try disabling everything non-essential, seeing if the problem goes away, and then re- enabling things one at at a time until you pinpoint where the issue is. 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 -~----------~----~----~----~------~----~------~--~---
