I may have mentioned in passing in another post, I use MySQLWorkbench. If you copy/paste the sequel to create the table into the query browser, you will get a red X to the left of the offending line, and the part that is wrong will be in another color than the "good" sql. It's pretty easy to see or determine at that point what the problem is. I would think just about any SQL tool would have some kind of feature like this.
Bob On Mar 21, 2011, at 10:21 AM, Peter Haworth wrote: > Thanks Bob, that's a good start. I'll search for the post with the link to > differences. > > I hope you're right that my queries will all still work fine. tRight now, > I'm struggling to get the database created. I was hoping I could export the > db structure using the Firefox SQLite manager and then import the resulting > file with the SequelPro Import feature but I get a host of syntax error > messages when I do the import. The error messages are pretty useless because > they are just generalised messages like"Syntax error near xyz, refer to your > mySQL manual". I think almost all of them are something to with either > PRIMARY KEY or foreign key definitions specified with the REFERENCES keyword > but haven't tracked down just what the problem is yet. > > Pete Haworth > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
