Hi Ralf > --- Ursprüngliche Nachricht --- > Von: Ralf Junker <[EMAIL PROTECTED]> > An: sqlite-users@sqlite.org > Betreff: Re: [sqlite] Charset-Confusions > Datum: Tue, 16 May 2006 11:10:28 +0200
> You have asked "How is it so complicated? *hmmm*" Well, because SQLite > does not have an interface to save values back to the database for any > arbitrary select statement. In order to update a cell, its database, > table,column, and row must be determined, which is unfortunately not > always possible, for example if the query does not contain the RowID > as part of its result set. Then SQLiteSpy would have to modify > the query, and so on. Ooops... i dont have considered this. But the Background as i look at this feature is, i have allways and in every Table a First-Field named "RecID", Autoincremental, Primary Key, not editable. Also I ever have a RowID and never got this problem. But this i even my way... and now I understand the problem that have a public tool. > I wish there was a function like > long long int sqlite3_column_rowid(sqlite3_stmt*, int iCol); Yep. That's it. Best Regards, Anne -- GMX Produkte empfehlen und ganz einfach Geld verdienen! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner
