On Mon, Jun 09, 2008 at 12:54:09PM +0200, Diez B. Roggisch wrote:
> I'm actually less than satisfied with the way SO currently deals with
> parameters - because it essentially does the escaping itself, and then
> creates full SQL-statements.
>
> The better way to go would of course be to use the
> Currently I'm working around this by duplicating the
> backslash in python, which generates the same error from postgres but
> actually returns records beginning with a single backslash. It looks like
> postgres has a special E'' syntax for escaping which I don't entirely
> understand, but would
Hi everyone,
I'm having trouble with backslash escapes in PostgreSQL 8.3 and SQLObject.
I currently have a Resource class that looks like:
class Resource(SQLObject):
resource = UnicodeCol(unique=True)
@classmethod
def autocomplete(cls, input):
""" Controller for the auto
