Patches item #3588789, was opened at 2012-11-20 12:30
Message generated for change (Comment added) made by phd
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=3588789&group_id=74338
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Darren Janeczek (darren_janeczek)
>Assigned to: Oleg Broytman (phd)
Summary: Columns with keyword names are problematic for some queries
Initial Comment:
Assume you create a SQLObject out of an existing table that happens to have a column named "group".
This crude patch will protect most queries that involve columns with names like "group" etc, by using a function that wraps the names with back quotes: `group`.
NOT THOROUGHLY TESTED.
----------------------------------------------------------------------
>Comment By: Oleg Broytman (phd)
Date: 2012-11-20 12:43
Message:
Thanks. Alas, the patch quotes special names with backticks which AFAIK are
only valid on MySQL. Any idea if there are other backends that use
backticks to quote names?
Postgres, as well as most other databases use double quotes (") to quote
names. Can you rework the patch so it takes the quote character from the DB
Connection?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=3588789&group_id=74338
|