On Thu, 17 Feb 2005 10:00:08 -0800, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On Feb 17, 2005, at 9:53 AM, H. Wade Minter wrote:
> > I'm playing around with some Python stuff, and was wondering if there
> > were any reasonably stable bindings for SQLite 3? I've got an
> > existing SQLite 3 da
On Feb 17, 2005, at 9:53 AM, H. Wade Minter wrote:
I'm playing around with some Python stuff, and was wondering if there
were any reasonably stable bindings for SQLite 3? I've got an
existing SQLite 3 database that I want to work against, so I'd rather
not drop back to SQLite 2?
I have been usi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm playing around with some Python stuff, and was wondering if there were
any reasonably stable bindings for SQLite 3? I've got an existing SQLite
3 database that I want to work against, so I'd rather not drop back to
SQLite 2?
I've found http://w
At 2:13 PM -0600 8/25/04, Dennis Cote wrote:
I agree with Michael and also Matt Wilson's previous posts.
This is a good idea, but it should stick to the SQL standard way of naming
vaiables; a colon, ":", followed by an identifier. This scheme is used by
most other SQL engines for this purpose. It i
Michael Roth wrote:
> We already have ?, ?nnn and :nnn: IIRC. Adding $xyz, %xyz, @xyz and
> possible other ones in parallel isn't a good thing, I think.
>
> Maybe :xyz: is good enought and binding language neutral. Maybe @xyz.
>
> How this is handled in other engines? Maybe there is a
> 'semi-stand
On Wed, Aug 25, 2004 at 12:27:28AM -0700, David M. Cook wrote:
>
> Yeah, it's read-only, though, (no __setitem__), you have to "cast" to a dict
> if you want to use the rows in your app.
Hmmm. Anything beyond providing the sequence protocol for the result
of a fetchone() is an extension anyway..
On Wed, Aug 25, 2004 at 12:10:39AM -0400, Matt Wilson wrote:
> On Tue, Aug 24, 2004 at 08:43:47PM -0700, David M. Cook wrote:
> >
> > * DBAPI compliance is important to me. sqlite is only one of the DBs I'd
> > like to support in my apps.
>
> Do you know what's currently lacking in conformance
On Tue, Aug 24, 2004 at 08:43:47PM -0700, David M. Cook wrote:
>
> * DBAPI compliance is important to me. sqlite is only one of the DBs I'd
> like to support in my apps.
Do you know what's currently lacking in conformance?
> * I use pyformat pretty heavily. I like being able to use dictionar
On Tue, Aug 24, 2004 at 02:07:58PM -0400, Matt Wilson wrote:
> Hi. I've been working on some refactoring of the Python bindings for
Sounds great, thanks for your work on this. Some things I'd like to see in
a sqlite wrapper:
* DBAPI compliance is important to me. sqlite is only one of the DBs
Kurt Welgehausen wrote:
db eval {UPDATE t1 SET value=$bigblob WHERE rowid=$id}
Is this more efficient than
db eval "UPDATE t1 SET value='$bigblob' WHERE rowid=$id" ?
In particular, does it save a copy of the character data?
Yes, it does save you from making a copy of the data, which
can be signi
> db eval {UPDATE t1 SET value=$bigblob WHERE rowid=$id}
Is this more efficient than
db eval "UPDATE t1 SET value='$bigblob' WHERE rowid=$id" ?
In particular, does it save a copy of the character data?
Regards
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
We already have ?, ?nnn and :nnn: IIRC. Adding $xyz, %xyz, @xyz and
possible other ones in parallel isn't a good thing, I think.
Maybe :xyz: is good enought and binding language neutral. Maybe @xyz.
How this is handled in other engines? Maybe the
On Tue, 24 Aug 2004, D. Richard Hipp wrote:
Matt Wilson wrote:
Normally python programmers would like to see named arguments in
dictionary substation format:
d = { 'blob': 'a\0b', 'id': 2 }
cursor.execute("UPDATE t1 SET value=%(bigblob)s WHERE rowid=%(id)d", d)
I'd be willing to extend the lexer/pa
On Tue, Aug 24, 2004 at 03:37:15PM -0400, D. Richard Hipp wrote:
> >
> >d = { 'blob': 'a\0b', 'id': 2 }
> >cursor.execute("UPDATE t1 SET value=%(bigblob)s WHERE rowid=%(id)d", d)
> >
>
> I'd be willing to extend the lexer/parser of SQLite to accept this kind
> of thing. The only problem here is t
Matt Wilson wrote:
Normally python programmers would like to see named arguments in
dictionary substation format:
d = { 'blob': 'a\0b', 'id': 2 }
cursor.execute("UPDATE t1 SET value=%(bigblob)s WHERE rowid=%(id)d", d)
I'd be willing to extend the lexer/parser of SQLite to accept this kind
of thing.
On Tue, Aug 24, 2004 at 02:55:51PM -0400, D. Richard Hipp wrote:
>
> I do not know if this new technique will be helpful to Python
> or not, but I thought I would bring it to your attention, just
> in case it is. Please note that the changes to support this
> are in CVS but have not be added to a
Matt Wilson wrote:
1) Wildcards in the SQL passed to cursor.execute() now use the sqlite
native '?' or ':N:' format. Previously Python syntax was allowed.
Making this change lets us bind parameters to compiled SQL
statements natively, without converting them to strings. This will
also
Hi. I've been working on some refactoring of the Python bindings for
sqlite. I now have a working Python binding for sqlite 3 which is
fairly different than the bindings for sqlite 2. I created a quick
test case that creates a new table, inserts 500,000 rows, then selects
all of them. Memory ut
18 matches
Mail list logo
