2007/9/5, Oleg Broytmann <[EMAIL PROTECTED]>:
>Mea culpa! I found a brown paper bag bug a minute after I have released
> 0.9.1, so I tried to hide my fault... and failed. Sorry.
No problem. I could also be blamed for eagerly downloading
immediately after the release e-mail ;)
---
On Wed, Sep 05, 2007 at 02:41:53PM +0200, Markus Gritsch wrote:
> making
> changes in already released versions without increasing the version
> number is not optimal.
Mea culpa! I found a brown paper bag bug a minute after I have released
0.9.1, so I tried to hide my fault... and failed. Sorry
2007/9/5, Oleg Broytmann <[EMAIL PROTECTED]>:
>Please add "?debug=1" to your DB URI and show the output. What version
> of SQLObject are you using?
I used SQLObject-0.9.1-py2.5.egg which I downloaded on 2007-07-26. If
I compare this version with a recently downloaded version of the same
file,
On Tue, Sep 04, 2007 at 08:35:09PM +0200, Markus Gritsch wrote:
> Test(name=r'C:\some\path')
> print Test.get(1).name # C:somepath when using MySQL
SQLite:
4/QueryIns: INSERT INTO test (name) VALUES ('C:\some\path')
C:\some\path
Postgres:
1/QueryIns: INSERT INTO test (id, name) VALUES
Hi,
when running the self contained test script below using the SQLite
backend, the output correctly reads
C:\some\path
When using the MySQL backend is reads
C:somepath
Is this a bug? What is the behavior of other backends. Shouldn't
SQLObject escape the backslashes for the MySQL backend?
K
