[issue20587] sqlite3 converter not being called

Erlend E. Aasland added the comment: Closing as out-of-date. If anyone disagrees, please reopen :) -- resolution: -> out of date stage: -> resolved status: pending -> closed ___ Python tracker

[issue20587] sqlite3 converter not being called

Erlend E. Aasland added the comment: I'm unable to reproduce this on 3.8 though 3.11a0. It's unclear to me if this even was an issue. (I have no ancient Python versions to test with.) Closing as out-of-date in a day or two, unless someone disagrees. -- nosy: +erlendaasland status: op

[issue20587] sqlite3 converter not being called

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue20587] sqlite3 converter not being called

Changes by Gerhard Häring : -- assignee: -> ghaering nosy: +ghaering ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue20587] sqlite3 converter not being called

Mark Lawrence added the comment: Can somebody try my code on 2.7 as I don't run it anymore. You'll probably have to undo the str => bytes dance I've just performed. Any reason why the default convertors and adapters described here https://docs.python.org/2/library/sqlite3.html#default-adapte

[issue20587] sqlite3 converter not being called

Kathryn M Kowalski added the comment: See attached file with output from both python versions. It is using the converter as shown in demo2a. The code using the converter was working on 2.5 for years - it quit working on the move to 2.7 because it couldn't compare a datetime to the text strin

[issue20587] sqlite3 converter not being called

Ned Deily added the comment: Perhaps the external pysqlite distribution from PyPI was installed on 2.5. Kathryn, can you supply the output from the two versions? import sqlite3 print(sqlite3.version) print(sqlite3.sqlite_version) -- nosy: +ned.deily __

[issue20587] sqlite3 converter not being called

Peter Otten added the comment: Are you sure that the converter is called in Python 2.5? I've looked into the source (Modules/_sqlite/cursor.c), and if I understand the code correctly it uses the sqlite3_column_decltype() function from the sqlite3 API to determine the column type. So Python wou

[issue20587] sqlite3 converter not being called

Serhiy Storchaka added the comment: Use "select alpha". -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing

[issue20587] sqlite3 converter not being called

Kathryn M Kowalski added the comment: Worked on my machine too - but if you add "union all" AND "order by" it breaks -- Added file: http://bugs.python.org/file34047/demo2.py ___ Python tracker _

[issue20587] sqlite3 converter not being called

Peter Otten added the comment: I have condensed your code into a self-contained demo. Unfortunately that seems to work on 2.7 (I don't have 2.5). -- nosy: +peter.otten Added file: http://bugs.python.org/file34035/demo.py ___ Python tracker

[issue20587] sqlite3 converter not being called

R. David Murray added the comment: Hmm. Looks like I would need a copy of your database to be able to run this? Maybe you could add something to create the schema and add the rows to be queried? There are tests for the converter/adapter functionality, so it must be something specific about

[issue20587] sqlite3 converter not being called

Changes by Kathryn M Kowalski : Added file: http://bugs.python.org/file34029/check_with_output.txt ___ Python tracker ___ ___ Python-bugs-list

[issue20587] sqlite3 converter not being called

R. David Murray added the comment: Can you pare it down further so that it only uses stdlib code? -- nosy: +r.david.murray ___ Python tracker ___

[issue20587] sqlite3 converter not being called

New submission from Kathryn M Kowalski: I have a timestamp converter that works on 2.5 but doesn't on 2.7.2 (ActiveState 2.7.2.5 Attached is some pared down test code and output from a machine running 2.5 and one running 2.7. At one point I even put print statements in the converter - they s