On 06/11/2010, at 21:28, Jay A. Kreibich wrote:
On Sat, Nov 06, 2010 at 08:35:10PM -0300, Tito Ciuro scratched on the wall:
Hello,
I have a question about manifest typing/data affinity. Assume I have
created this table:
CREATE TABLE foo (ROWID INTEGER PRIMARY KEY, key TEXT, attr TEXT,
Hello everyone,
Sorry about my last email... I clicked Send too quickly.
Jay, the book is great, I have discovered quite a few details I had overlooked
(or perhaps missed, since I worked with earlier versions of SQLite and some
current features were not available yet).
Thank you and all who
Hello,
I have a question about manifest typing/data affinity. Assume I have created
this table:
CREATE TABLE foo (ROWID INTEGER PRIMARY KEY, key TEXT, attr TEXT, value NONE);
I was reading the Using SQLite book and came across page #38 (#60 on the PDF
version) where it states:
None: A column
Tito Ciuro tci...@mac.com wrote:
My main question has to do with binding values to precompiled statements. For
the value column, should I:
a) use sqlite3_bind_value()?
No, except in certain special cases. You would normally have no way to obtain
sqlite_value pointer, anyway.
b) store it
On 6 Nov 2010, at 11:35pm, Tito Ciuro wrote:
My main question has to do with binding values to precompiled statements. For
the value column, should I:
a) use sqlite3_bind_value()?
b) store it as a string using sqlite3_bind_text()? Will sqlite3_bind_text()
allow SQLite to choose the
Quoth Tito Ciuro tci...@mac.com, on 2010-11-06 20:35:10 -0300:
None: A column with a none affinity has no preference over storage
class. Each value is stored as the type provided, with no attempt to
convert anything.
Note that type affinities are not usually specified as column types
directly.
On Sat, Nov 06, 2010 at 08:35:10PM -0300, Tito Ciuro scratched on the wall:
Hello,
I have a question about manifest typing/data affinity. Assume I have
created this table:
CREATE TABLE foo (ROWID INTEGER PRIMARY KEY, key TEXT, attr TEXT, value NONE);
I was reading the Using SQLite book
