D. Richard Hipp wrote: > On Feb 2, 2008, at 7:57 PM, Scott Chapman wrote: > > >> I've looked high and low and can't find a way to invoke the other 2 >> affinity modes. Are they available? I'm on 3.5.4. >> > The concept of "strict" affinity mode was briefly discussed years > ago, but we never implemented it, having never seen any benefit > for such a thing. Can you explain why you think strict affinity mode > might be beneficial to you? If somebody can provide a good > enough rational to justify strict affinity mode, we might just put it > in. > I'm working on a Python adapter that goes on top of APSW. It will enable you to use the column types NUMERIC, DATE, TIME, TIMESTAMP and automatically convert these to and from Python's respective data types.
The case I'm dealing with that is not working like I want is the case of NUMERIC column type. In SQLite, this column type gets an affinity of REAL. If I put in a value to the column as a string literal, say '123.23', it's stored as a REAL even though I specified it as a string in quotes. I want it to store it as a string. The only way I've found to fix this is to use a column type of NUMERIC_TEXT. The presense of "TEXT" in the column type changes the affinity to string. This is not very elegant and I was looking for any other way to make this work correctly. "No Affinity" would probably work, if I understand it correctly. I want to avoid the use of REAL types in this case because they can lead to rounding errors, which is the whole purpose of the NUMERIC type to begin with, in my understanding. I also would like to be able to make the column type just NUMERIC as that is compilant with the SQL standard. Strict Affinity and No Affinity are mentioned in the SQLite3 Datatypes page. If there are no plans to implement these, please consider removing them from the docs. Thanks! Scott _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
