> --- Ursprüngliche Nachricht --- > Von: John Stanton <[EMAIL PROTECTED]> > An: sqlite-users@sqlite.org > Betreff: Re: [sqlite] BLOB > Datum: Sat, 13 May 2006 08:17:29 -0700 >People with English as a first language can have difficulty >understanding the description of manifest typing in the Sqlite >documenation. When you have less English it is more difficult :-).
Yes, it is ;-) ...but the good message is: I have solve my problem :-D And its so simple. And its really famous. But i have to do a "mind-jump". It is similar to the jump from C to C++. To think object-oriented, lost the top-down-control and handled by events was heavy as i started with c++ 10 years ago. My awareness, the internal SQLite-Column-Type is absolutely not importand to me. I think, SQLite is always clever enough, to choose one of the correct internal storage-classes. I only fetch the declared type and use this to control my Wrapper-Class to cast a lot of Variant-Type-Values before Write and after Read ... and it runs ;-) Indeed... the Name "sqlite3_column_type()" is confusing. The Name suggest, that the return applies to all rows. If i understand the the meaning of this Function, a better name was "sqlite3_current_cell_type(). *hmmm* Imho should sqlite3_column_type() works in interaction with the sqlite-interpreted results from userdefined sqlite3_column_decltype() Maybe.. sometime... at the moment, not important to me. Greetings from Germany Anne -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl
