OMG... I do apologize for this, it seems that there was indeed a "details-temp" table in the production database that isn't part of our production schema. I've dropped the table and everything worked perfectly...
No to figure out whose responsible for the rogue table... Thanks! On 11/8/06, Jamis Buck <[EMAIL PROTECTED]> wrote: > Kenneth, > > It's definitely not capistrano, though. I would make absolutely sure > that you're migrating the database that you think you're migrating. > Rails is, somehow, finding a table named 'details-temp' and is trying > to dump it's schema. > > - Jamis > > On Nov 8, 2006, at 9:50 AM, Kenneth Kalmer wrote: > > > > > Hi Jamis > > > > Will follow up there, but as I mentioned in my original post, it only > > happens when I migrate use capistrano, and we don't have a single > > table in that database that has a hyphen, or the word 'details' in > > their name... > > > > Best > > > > On 11/8/06, Jamis Buck <[EMAIL PROTECTED]> wrote: > >> Kenneth, > >> > >> This is actually a rails issue, that you might want to bring up on > >> the rails list. When the last migration finishes, Rails rebuilds your > >> db/schema.rb file. It does this by grabbing a list of all tables in > >> the current database, and writing their definitions out. Apparently, > >> in your database there is an existing table named details-temp. > >> Rails needs to be wrapping the table name in ` characters so that the > >> hyphen is allowed. > >> > >> - Jamis > >> > >> On Nov 8, 2006, at 4:55 AM, Kenneth Kalmer wrote: > >> > >>> > >>> Hi folks > >>> > >>> First off, Jamis (and others), thanks for the great app. It really > >>> simplified my life significantly the last couple of weeks and I'm > >>> forever grateful for rake remote:deploy... > >>> > >>> On one specific project I'm having an issue with remote migrations > >>> that I cannot pin down. Whenever I run the remote migrations it > >>> successfully runs through the entire list of migrations, but fails > >>> mysteriously after the last migration with the following MySQL error > >>> > >>> Mysql::Error: #42000You have an error in your SQL syntax; check the > >>> manual that corresponds to your MySQL server version for the right > >>> syntax to use near '-temp' at line 1: SHOW FIELDS FROM details-temp > >>> > >>> This isn't part of my migration, and we don't have a table called > >>> "details-temp", or even "details" for that matter. I've even grep'ed > >>> the entire source on the server and cannot find any mention of the > >>> term in question. > >>> > >>> Any ideas? > >>> > >>> -- > >>> > >>> Kenneth Kalmer > >>> [EMAIL PROTECTED] > >>> > >>> [EMAIL PROTECTED] stats > >>> http://fah-web.stanford.edu/cgi-bin/main.py? > >>> qtype=userpage&username=kenneth%2Ekalmer > >>> > >>>>> > >> > >> > >> > >> > > > > > > -- > > > > Kenneth Kalmer > > [EMAIL PROTECTED] > > > > [EMAIL PROTECTED] stats > > http://fah-web.stanford.edu/cgi-bin/main.py? > > qtype=userpage&username=kenneth%2Ekalmer > > > > > > > > > > -- Kenneth Kalmer [EMAIL PROTECTED] [EMAIL PROTECTED] stats http://fah-web.stanford.edu/cgi-bin/main.py?qtype=userpage&username=kenneth%2Ekalmer --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
