Re: [sqlite] Q about new SQLite API

[EMAIL PROTECTED] uttered: I'm working on a new API routine for SQLite and I have questions for the community. The working name of the new api is sqlite3_prepare_v2(). sqlite3_prepare_v2() works like sqlite3_prepare() in that it generates a prepared statement in an sqlite3_stmt structure. The

Re: [sqlite] Q about new SQLite API

At 1:17 PM + 11/7/06, [EMAIL PROTECTED] wrote: QUESTION 1: sqlite3_prepare_v2 is the merely the working name for the new function. What should the official name be? I like sqlite3_prepare_v2. It lets me know that it's very similar to sqlite3_prepare, so lots of existing documentation

Re: [sqlite] Q about new SQLite API

[EMAIL PROTECTED] wrote: I'm working on a new API routine for SQLite and I have questions for the community. The working name of the new api is sqlite3_prepare_v2(). sqlite3_prepare_v2() works like sqlite3_prepare() in that it generates a prepared statement in an sqlite3_stmt structure. The

Re: [sqlite] Q about new SQLite API

[EMAIL PROTECTED] wrote: * sqlite3_step() returns the correct error code right away, rather than just returning SQLITE_ERROR and making you call sqlite3_reset() to find the true reason for the error. I actually prefer the existing behaviour. If you do start returning the error

Re: [sqlite] Q about new SQLite API

sday, November 7, 2006 5:17:37 AM Subject: [sqlite] Q about new SQLite API I'm working on a new API routine for SQLite and I have questions for the community. The working name of the new api is sqlite3_prepare_v2(). sqlite3_prepare_v2() works like sqlite3_prepare() in that it generates a pr

Re: [sqlite] Q about new SQLite API

On Nov 7, 2006, at 5:17 AM, [EMAIL PROTECTED] wrote: QUESTION 1: sqlite3_prepare_v2 is the merely the working name for the new function. What should the official name be? What about introducing an options mechanism in place of a second prepare mechanism? Do you foresee any situations

Re: [sqlite] Q about new SQLite API

Hello, Thanks for the improvements! Q1 Any name would be find, though the 'ex' extension seems to be popular for that sought of thing. Q2 A non-blocking resultset API? :) Sorry, had to try. Q3 I think this should be a new error for the caution's sake. But overall I prefer more, finer grain,

Re: [sqlite] Q about new SQLite API

On 11/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: * You never get an SQLITE_SCHEMA error. sqlite3_prepare_v2 retains the original SQL and automatically reprepares and rebinds it following a schema change. Does this part of the change require a new API at all? *

RE: [sqlite] Q about new SQLite API

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 07, 2006 6:18 AM > To: sqlite-users@sqlite.org > Subject: [sqlite] Q about new SQLite API > > I'm working on a new API routine for SQLite and I have > questions

Re: [sqlite] Q about new SQLite API

"Klemens Friedl" <[EMAIL PROTECTED]> wrote: > > Btw. are there plans to implement grouping operator (i.e. parentheses) > and a real "NOT" (not just "exclude") features in "Fts Two" ? > Maybe and no. -- D. Richard Hipp <[EMAIL PROTECTED]>

Re: [sqlite] Q about new SQLite API

[EMAIL PROTECTED] writes: > QUESTION 1: sqlite3_prepare_v2 is the merely the working name > for the new function. What should the official name be? > Some possibilities include: > > sqlite3_prepare_ex1 > sqlite3_prepare_ng > sqlite3_new_prepare > sqlite3_compile sqlite3_compile

Re: [sqlite] Q about new SQLite API

This is a very good news: 1. sqlite3_compile 2. maybe with the new sqlite3_compile routine there should also be a way to retrieve the rowid of the current row (NULL is no valid rowid is found), a possible API could be sqlite3_rowid to call after each sqlite3_step only if it returns an

Re: [sqlite] Q about new SQLite API

1. sqlite3_re_prepare or simply sqlite3_reprepare On 11/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: QUESTION 1: sqlite3_prepare_v2 is the merely the working name for the new function. What should the official name be? Some possibilities include: sqlite3_prepare_ex1

Re: [sqlite] Q about new SQLite API

[EMAIL PROTECTED] wrote: QUESTION 3: Suppose there is a schema change and the SQL statement is automatically reprepared. But the schema change is such that the SQL is no longer valid. (Perhaps one of the tables mentioned in a SELECT statement was dropped.) What error code should sqlite3_step()

Re: [sqlite] Q about new SQLite API

2006/11/7, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: QUESTION 1: "sqlite3_prepare_ex" (or "sqlite3_compile") QUESTION 3: maybe: "SQLITE_INVALID_SQL" Btw. are there plans to implement grouping operator (i.e. parentheses) and a real "NOT" (not just "exclude") features in "Fts Two" ? Best

RE: [sqlite] Q about new SQLite API

PROTECTED] Sent: Tuesday, November 07, 2006 8:18 AM To: sqlite-users@sqlite.org Subject: [sqlite] Q about new SQLite API I'm working on a new API routine for SQLite and I have questions for the community. The working name of the new api is sqlite3_prepare_v2(). sqlite3_prepare_v2() works like

[sqlite] Q about new SQLite API

I'm working on a new API routine for SQLite and I have questions for the community. The working name of the new api is sqlite3_prepare_v2(). sqlite3_prepare_v2() works like sqlite3_prepare() in that it generates a prepared statement in an sqlite3_stmt structure. The differences is in the