Gerhard Häring [EMAIL PROTECTED] added the comment:
Implemented in r62702.
--
resolution: - accepted
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2157
__
Gerhard Häring added the comment:
The same question came up in the external pysqlite project once. My
answer is the same here: this won't be fixed because of backwards
compatibility reasons. The current behaviour is well documented.
I acknowledge that it would be nice to be able to use
wrobell added the comment:
fair enough, but...
1. i really do not see that behaviour documented, i.e.
http://docs.python.org/lib/node347.html
says nothing about types being broken on space character.
2. i am bit missing the point about backward compability.
when looking on
Gerhard Häring added the comment:
It's mentioned here: http://docs.python.org/lib/sqlite3-Module-Contents.html
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2157
__
___
Gerhard Häring added the comment:
Yes, I acknowledge the backwards incompatibility is rather a one in a
billion case than a one in a million case.
I'll reopen this one and integrate your patch or something similar for
Python 2.6 and 3.0.
--
resolution: wont fix -
status: closed - open
New submission from wrobell:
Numeric type conversion does not always work when using SQLite module.
Let's assume schema:
create table test_num(no numeric);
Fetching a `test_num.no` table gives float by default.
Now, let's register some converter
sqlite3.register_converter('numeric',
