On Feb 3, 2009, at 8:18 AM, Efthimios Toulas wrote: > Hi, > > I encountered a problem with the UNIQUE column-constraint in my setup. > Searching the web and the archives I couldn't find any discussion on > this topic. > > When trying to access the SQLite database via ODBC from MS Access > (linked tables) everything works fine except for the tables containing > a UNIQUE column-constraint. I simply get all fields displayed with > #######. > > It is only a guess on the UNIQUE statement for this was the only real > difference I could find between the "faulty" and the working tables. > After removing the statement it worked. > > Accessing the table via the provided command-line tool works as > expected. Reading and writing to the database from Python (using Storm > ORM which depends on pysqlite2) works just great on any of the tables.
Sounds like a problem your ODBC driver therefore.... > > > It is no problem to simply remove the unique contraint in this > particular application. > I wonder if this issue is known and/or if there is a better way of > achieving what I want to do. > > Regards, > Efthimios Toulas > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
