Ok, here's one step closer to a fix! This is what had to be manually changed in order to quote the names of tables/fields to load a postgres database into MySQL.
This won't work for other databases. And this only works for importing a database—table creation, with foreign keys, and insert statements. Nothing else (e.g. selects, updates) was tested. And we had to guide it manually through the table creation, to get foreign key constraints satisfied in the right order. But this will show an interested developer exactly where to begin fixing the code for this bug... that seems to be biting a few of us. On Jun 20, 2012, at 1:19 PM, Rene Dohmen wrote: > I'm having the same problem: > https://groups.google.com/d/msg/web2py/hCsxVaDLfT4/K6UMbG5p5uAJ > > > On Mon, Jun 18, 2012 at 9:30 AM, Michael Toomim <[email protected]> wrote: > I just got bit by the reserved-word problem: > https://groups.google.com/d/msg/web2py/aSPtD_mGXdM/c7et_2l_54wJ > > I am trying to port a postgres database to a friend's mysql database, but we > are stuck because the DAL does not quote identifiers. > > This problem has been discussed a fair amount: > https://groups.google.com/d/msg/web2py/QKktETHk3yo/Mwm3D-JhNmAJ > > ...and it seems all we need to do is add some quoting mechanisms to the DAL. > In postgresql you surround names with "quotes" and in mysql you use > `backticks`. > > Does anyone have ideas for what to do? > > --
On Jun 20, 2012, at 1:19 PM, Rene Dohmen wrote: I'm having the same problem: |
dal.py.changes
Description: Binary data
