-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 08.06.2013 16:25, schrieb Richard Kelsall:

Hello Python Docs,

TLDR: I think it should probably say 'REAL' not 'FLOAT' as the SQLite datatype in 11.13.1 of sqlite3.

I am reading the sqlite3 page

http://docs.python.org/2/library/sqlite3.html

for Python v2.7.5. It says in 11.13.1:

"SQLite natively supports only the types TEXT, INTEGER, FLOAT, BLOB and NULL."

This made me wonder, is this a double or single FLOAT? (I have not used this database or this Python module before.) And I looked in the SQLite documentation here

http://sqlite.org/datatype3.html

This says that SQLite version 3 uses an 8 byte (i.e. double) float and has this as type REAL. So I go back to the python page thinking maybe this is an earlier version of SQLite - maybe Python 2 provides SQLite 2 for backwards compatibility and the module name 'sqlite3' does not follow the SQLite version number for some reason. I cannot see on this page mention of what version of SQLite this module provides, maybe I missed that? But I see in 11.13.5.1:

"SQLite natively supports the following types: NULL, INTEGER, REAL, TEXT, BLOB."

So this internal contradiction makes me think section 11.13.1 is incorrect.

I feel posting to this public list, of unknown proportions, may be a rather loud way of reporting such a minor problem, but the documentation page seems to ask me to do this. A wiki might have been an easier and less noisy way to suggest corrections. I expect many people would not go to the trouble of emailing a public mailing list to get a detail like this corrected and that there are many similar bugs which are found but not immediately reported for this reason.

Hi Richard, posting here is exactly the right way of reporting, even if it sometimes takes a while :) Thanks for the report, I've fixed this now and it will appear online soon. cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iEYEARECAAYFAlJRPfsACgkQN9GcIYhpnLDhiwCgqDZhLgO747r5Y1B4M959NUBr i7oAoIZstIh7LVI72b+NFB4LHcYmUMEr =3xIi -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 08.06.2013 16:25, schrieb Richard Kelsall:

Hello Python Docs,

TLDR: I think it should probably say 'REAL' not 'FLOAT' as the SQLite datatype in 11.13.1 of sqlite3.

I am reading the sqlite3 page

http://docs.python.org/2/library/sqlite3.html

for Python v2.7.5. It says in 11.13.1:

"SQLite natively supports only the types TEXT, INTEGER, FLOAT, BLOB and NULL."

This made me wonder, is this a double or single FLOAT? (I have not used this database or this Python module before.) And I looked in the SQLite documentation here

http://sqlite.org/datatype3.html

This says that SQLite version 3 uses an 8 byte (i.e. double) float and has this as type REAL. So I go back to the python page thinking maybe this is an earlier version of SQLite - maybe Python 2 provides SQLite 2 for backwards compatibility and the module name 'sqlite3' does not follow the SQLite version number for some reason. I cannot see on this page mention of what version of SQLite this module provides, maybe I missed that? But I see in 11.13.5.1:

"SQLite natively supports the following types: NULL, INTEGER, REAL, TEXT, BLOB."

So this internal contradiction makes me think section 11.13.1 is incorrect.

I feel posting to this public list, of unknown proportions, may be a rather loud way of reporting such a minor problem, but the documentation page seems to ask me to do this. A wiki might have been an easier and less noisy way to suggest corrections. I expect many people would not go to the trouble of emailing a public mailing list to get a detail like this corrected and that there are many similar bugs which are found but not immediately reported for this reason.

Hi Richard, posting here is exactly the right way of reporting, even if it sometimes takes a while :) Thanks for the report, I've fixed this now and it will appear online soon. cheers, Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iEYEARECAAYFAlJRPfsACgkQN9GcIYhpnLDhiwCgqDZhLgO747r5Y1B4M959NUBr i7oAoIZstIh7LVI72b+NFB4LHcYmUMEr =3xIi -----END PGP SIGNATURE-----