I haven't looked closely at the problem, so these are just first ideas
extending CM's approach. Basically there should be no reason to perform
any analysis of the SQL since that has already been done and the
metalanguage generated. My approach would be to prepare the SQL
statement and then use the compiled SQL to generate an UPDATE statement.
The existing SQLite VM gives you a model for the framework of your engine.
The process may be simpler than you think if you integrate your concept
with the core of SQLite. By doing all processing at the token level you
achieve much more efficiency compared to having to repeat the lexical
analysis and parsing already performed by SQLite.
JS
Cariotoglou Mike wrote:
one idea. run an EXPLAIN fist, and then analyze the query plan. it will
tell you if there are more than one tables,
and maybe you can get info about aggregate functions and such. of
course, there is a cost to this...
-----Original Message-----
From: Will Leshner [mailto:[EMAIL PROTECTED]
Sent: Monday, December 19, 2005 11:12 PM
To: Forum SQLite
Subject: [sqlite] implementing editable result sets
Hi. I apologize in advance for the length of this question,
but it is a little involved.
I am the author of a wrapper for SQLite and in that wrapper
there is an object called a RecordSet that represents the
results of a query.
One of the things you can do with a RecordSet is edit
records. The way I've implemented editing a RecordSet is to
construct an UPDATE statement based on the new values for the
<snip>
