[sqlite] Binding binary data in 3.0.4

[SQLite]

The docs for sqlite3_bind_blob() states that passing in SQLITE_STATIC
mean that the blob data will be around until "SQLite has finished with
it." But when exactly is this? For an INSERT/UPDATE, is it when the
statement is executed, or the current transaction commmited, or some
other time?

Re: [sqlite] Multiple INSERT problem

[Demitri Muna]

On 28 Aug 2004, at 20:22, Kurt Welgehausen wrote:
Is there a limit on the number of intersects I can use?
No, this is a bug.  I confirmed it in v3.0.3.  I think you should
write a bug ticket.
This bug does not exist in v2.8.15.
Regards
Thanks for confirming that. I have submitted a bug report.
Cheers,
Demitri

Re: [sqlite] Multiple INSERT problem

[Kurt Welgehausen]

> Is there a limit on the number of intersects I can use?

No, this is a bug.  I confirmed it in v3.0.3.  I think you should
write a bug ticket.

This bug does not exist in v2.8.15.

Regards

Re: [sqlite] SQLite for large bulletin board systems?

[Darren Duncan]

At 1:44 AM -0600 8/28/04, John LeSueur wrote:
Also PearDB for PHP has some nice wrappers for a variety of 
different databases, that make this simpler, and other languages 
would have similar(at least I think perl does).
I'll say it has.  Practically every open-source database abstraction 
layer in use today is cloned from Perl's popular and mature DBI, 
which came out roughly 10 years ago.  This is particularly true for 
PearDB.  In fact, I think Pear in general even advertises itself as 
being a smaller but more micro-managed clone of CPAN, which is one 
type of resource that is fairly unique to the Perl community. -- 
Darren Duncan

[sqlite] Multiple INSERT problem

[Demitri Muna]

Hello,
I'm getting an error that I'm not sure what to do about. (I'm using 
v3.0.4.) Starting with this table:

sqlite> create temporary table test (label);
sqlite> insert into test values ('aaa');
sqlite> insert into test values ('abb');
sqlite> insert into test values ('acc');
sqlite> insert into test values ('abc');
This returns four rows: SELECT * FROM test WHERE label LIKE '%a%';
This returns two rows: SELECT * FROM test WHERE label LIKE '%a%' 
INTERSECT SELECT * FROM test WHERE label LIKE '%b%';

This returns: SELECT * FROM test WHERE label LIKE '%a%' INTERSECT 
SELECT * FROM test WHERE label LIKE '%b%' INTERSECT SELECT * FROM test 
WHERE label LIKE '%c%';
SQL error: database disk image is malformed

Is there a limit on the number of intersects I can use? Is there a 
better way that I can accomplish the same thing?

Cheers,
Demitri

Re: [sqlite] OLE/DB provider for SQLite?

[Nuno Lucas]

Hi,
I'm going to implement an OLE/DB provider for SQLite, but as I don't
like to program in COM I will not release the control free (but it will
not be expensive, either).
I was curious if there was any interest on this, as I see it as a way to
open the SQLite door to many other languages which support COM/ActiveX
controls (and ADO with it), but don't have any wrapper for it.
I am thinking of releasing the beta versions of it free of charge (for
non-commercial use, off course) but I don't know if I should bother to
do it (having to create a web page for it, support, etc.) if there is no
interest (as it will not be free).
One possible step would be porting it for Windows CE, giving more choice
for those that don't use C as a Windows CE language.
As this may be a little off topic for this ML, those that could be
interested just reply me directly to [EMAIL PROTECTED]
Regards,
~Nuno Lucas

Re: [sqlite] SQLite for large bulletin board systems?

[John LeSueur]

Andrew Piskorski wrote:
On Fri, Aug 27, 2004 at 05:30:40PM -0400, D. Richard Hipp wrote:
 

The best design would be to make the application generic so
that it could use either SQLite or a client/server database.
   

In an ideal world, yes.  In practice...  My guess is it's probably a
LOT more trouble than it's worth.
 

We have an enterprise application that we host, and we needed to write a 
desktop version that executives could use on planes, etc.  Being able to 
easily change from postgresql to sqlite was a big help in getting that 
done.  It is a little extra work(only a little) to be generic, but with 
some wrapper functions, its worth a lot more than the trouble you might 
run into by not doing it.  Also PearDB for PHP has some nice wrappers 
for a variety of different databases, that make this simpler, and other 
languages would have similar(at least I think perl does).

John LeSueur