what happens if you say:
import sqlite3
import os
sqlite3.connect(os.path.abspath("test.db"))
?
thats essentially what SQLA 0.7 does in order to guard against os.chdir()
changes as subsequent connections occur.
On Oct 22, 2011, at 11:28 AM, jmsilva wrote:
> On Oct 22, 2:18 pm, Michael Bayer <[email protected]> wrote:
>> strange. what happens if you examine the "test.db" file more closely, is it
>> created with odd permissions (like not readable or something strange ?) is
>> there a filesystem problem, can you reproduce this issue on any workstation
>> /environment ? the test case obviously works fine for me. The
>> OperationalError you see, while branded by SQLAlchemy, is ultimately derived
>> from the pysqlite error object so that's their operational error, not ours.
>>
>
> I don't think it's a permission problem, since I'm on Windows and,
> again, creating and reading the file from the sqlite3 module works
> fine. I've also checked the permissions, and everything was as it
> should be. Nevertheless, I've tested it on the Ubuntu VM I had lying
> around and indeed it works. So the question becomes: is there some
> sort of installation problem that can cause this? If not, and I try to
> debug the library, what should I be looking for?
>
> Thanks for the quick responde
> -- João
>
> --
> You received this message because you are subscribed to the Google Groups
> "sqlalchemy" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/sqlalchemy?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
