> > Myself, I'm not a big fan of high-level abstraction from the sql
> > being performed, so I wouldn't use the originally posted idea of
> > editing a recordset.
>
> I don't tend to use it either. But some people like to do things that
> way and I'd like to make it as easy as possible for
Will Leshner wrote:
On May 18, 2005, at 8:02 AM, Jay Sprenkle wrote:
When I wrote applications that allowed the user to enter queries
I added the unique key row to their query. I presented them with the
data they requested and either did not show the record id, or made
it read only. This allowed
I believe you are wrong. The rowid is the primary key in the SQLite
B-tree representation. It is always unique and allows you not to use
your own primary key. But if you have a column of type INTEGER PRIMARY
KEY, the values in this column become rowid. Otherwise a new
autoincremented column is
On May 17, 2005, at 8:11 PM, Ken & Deb Allen wrote:
By ensuring that each record receives a unique identifier and
including that in all queries, the main issue is resolved.
Right, but the problem is that the user didn't use the unique
identifier in the query and now I'm faced with the prospect
All database tables should be defined with a unique primary key.
Ideally this should consist of one or more integer columns; tect
columns can be used but they are universally less efficient. If the
data being stored does not contain a natural unique identifier, then
one should be added; you
On May 17, 2005, at 2:07 PM, Jay Sprenkle wrote:
rowid won't work in a multiuser database. It's just the row number
within
the result set you retrieved. This sort of problem is the reason
why people
use a unique id field. The database automatically assigns you a number
that won't change and
rowid won't work in a multiuser database. It's just the row number within
the result set you retrieved. This sort of problem is the reason why people
use a unique id field. The database automatically assigns you a number
that won't change and isn't shown to the user (they can't change it either).
I develop a database wrapper for SQLite and I have an interesting
problem that I'm curious how other people solve. Basically, the users
of my wrapper have the option of editing database records indirectly
through the wrapper, rather than directly, using UPDATE. The database
wrapper is a
8 matches
Mail list logo
