> ODBC-Driver == frontend ??? In this context - probably, yes.
> I'am pretty sure that it's an odbc-driver problem (so nothing to worry in this > group?) and I posted her for a workaround as short and elegant like the UNIQUE > constraint I am not allowed to use. If your ODBC driver doesn't allow you to have any UNIQUE constraint then, as Darren said, you better consider using some other driver, not a workaround for this one. I believe there are several ODBC drivers for SQLite out there. Pavel On Mon, Jun 28, 2010 at 11:00 AM, Oliver Peters <oliver....@web.de> wrote: > Pavel Ivanov <paiva...@...> writes: > >> >> > there are no NULLS in my example and I don't believe in a frontend-problem >> > (I >> > wouldn't interpret the SQL.LOG this way). >> >> If you don't believe that it's your frontend problem then go ahead and >> reproduce it in sqlite3 command line utility. If you were able to >> reproduce it there then it would be indeed an SQLite library problem. >> Otherwise it's frontend problem believe it or not. > > ODBC-Driver == frontend ??? > > I'am pretty sure that it's an odbc-driver problem (so nothing to worry in this > group?) and I posted her for a workaround as short and elegant like the UNIQUE > constraint I am not allowed to use. > > [...] > > Oliver > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
