This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Lauren.Foutz
Recipients Lauren.Foutz, eric.snow, ghaering, jcea, ned.deily, petri.lehtinen
Date 2012-05-22.19:13:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CANja8=6XQzURSo-5pcyzVWz4ciiGAWBZ08ULNA-xTOVzPBVEgw@mail.gmail.com>
In-reply-to <1328260654.65.0.0876518474051.issue13445@psf.upfronthosting.co.za>
Content
It is not possible to compile pysqlite to link with both, and even if it
was it would not be a good idea, since databases created by bdbsql cannot
be accessed by sqlite, and visa versa.

Because of the incompatibility I think a runtime flag would lead to a lot
of user error, but a separate connection class in the sqlite3 module might
work, but because the libraries share the same external functions, linking
them both with the python library will be difficult if not impossible.

Lauren

On Fri, Feb 3, 2012 at 4:17 AM, Petri Lehtinen <report@bugs.python.org>wrote:

>
> Petri Lehtinen <petri@digip.org> added the comment:
>
> Is it possible to compile pysqlite so that it links with both, or so that
> the linking type can be changed at run time?
>
> I'm -1 on adding a compile-time option to switch the storage backend to
> Python itself, but a runtime flag or a separate connection class for the
> sqlite3 module would do.
>
> ----------
> nosy: +petri.lehtinen
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue13445>
> _______________________________________
>
History
Date User Action Args
2012-05-22 19:13:11Lauren.Foutzsetrecipients: + Lauren.Foutz, jcea, ghaering, ned.deily, eric.snow, petri.lehtinen
2012-05-22 19:13:10Lauren.Foutzlinkissue13445 messages
2012-05-22 19:13:10Lauren.Foutzcreate