RE: [sqlite] Re: philosophy behind public domain?

2005-06-04 Thread Fred Williams
Much ado about nothing...

-Original Message-
From: D. Richard Hipp [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 04, 2005 6:08 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Re: philosophy behind public domain?


On Fri, 2005-06-03 at 21:01 +0200, Andreas Rottmann wrote:
> There is
> no such thing as "disclaiming copyright" in Europe (or at least
> Germany and Austria).
> 
> Rotty

This would be a problem for any citizen of Germany or Austria
that wanted to contribute code to the SQLite project.  I cannot
see that this would ever be a problem for an SQLite users.

Can citizens of Germany and Austria assign their copyright interest
to third parties?  If so, then if you want to contribute code to
SQLite, just assign the copyright to me and I will then dedicate
the code to the public domain, which I can do since I am not a
citizen of Austria or Germany.  If citizens of Germany and Austria
are not allowed to assign copyright, then you will not be allowed
to contribute code to SQLite regardless of what license SQLite uses.
Either way, the fact that SQLite has been dedicated to the public
domain seems unimportant.
-- 
D. Richard Hipp <[EMAIL PROTECTED]>



Re: [sqlite] Re: philosophy behind public domain?

2005-06-04 Thread D. Richard Hipp
On Fri, 2005-06-03 at 21:01 +0200, Andreas Rottmann wrote:
> There is
> no such thing as "disclaiming copyright" in Europe (or at least
> Germany and Austria).
> 
> Rotty

This would be a problem for any citizen of Germany or Austria
that wanted to contribute code to the SQLite project.  I cannot
see that this would ever be a problem for an SQLite users.

Can citizens of Germany and Austria assign their copyright interest
to third parties?  If so, then if you want to contribute code to
SQLite, just assign the copyright to me and I will then dedicate
the code to the public domain, which I can do since I am not a
citizen of Austria or Germany.  If citizens of Germany and Austria
are not allowed to assign copyright, then you will not be allowed
to contribute code to SQLite regardless of what license SQLite uses.
Either way, the fact that SQLite has been dedicated to the public
domain seems unimportant.
-- 
D. Richard Hipp <[EMAIL PROTECTED]>



Re: [sqlite] Re: philosophy behind public domain?

2005-06-04 Thread Clay Dowling

Eric Bohlman wrote:

This is a rather sticky point.  It's unlikely that someone who 
unofficially "disclaimed copyright" would willingly change his mind 
afterwards, but that assumes ideal circumstances.  In the Real World, 
people sometimes die, get divorced, or get sued by people they owe money 
to.  It seems to me that if someone from a country that doesn't 
recognize voluntary relinquishment of copyright (and, AFAIK, that's most 
countries) contributes code to SQLite or something similar, his heirs, 
ex-spouse, or creditors could end up with a proprietary interest in part 
of the code.  Not good.


I think that maybe everyone is getting their nickers in a bunch over 
nothing here.  It seems a little paranoid to get worried because 
somebody is giving something away for free.  What's somebody going to 
sue for?  Lost earnings because they didn't get their share of royalties 
for the code their former spouse/ancestor wrote?  The code was written 
with the understanding that it would not generate any revenue.


Copyright on the code has been renounced in the U.S.  So somebody in 
Germany wants to sue Mr. Hipp because he can't renounce it there. 
That's really great, but German courts have very little ability to act 
against foreign citizens who are in another country.  The same applies 
to other courts in other countries.  You can get all the judgements 
against a foreign citizen you want in a Russian, Spanish or Chinese 
court.  So long as the citizen stays on their native soil there's 
blessed little that can be done about collecting on those judgements.


Before somebody chimes in about how it'll be your own company that gets 
sued for using the code, sit down and relax.  Unless you have very deep 
pockets, you're more likely to be struck by lightning than to be a 
target of such a suit.  There's no point in going after somebody who'll 
be bankrupted by fighting the case, since there'll be no money to 
collect.  That's the sort of thing that happens to Daimler-Chrysler or 
IBM, because they can afford to fight the case.  If your company is that 
size, you should be fretting the matter with your lawyers, not a mailing 
list.


My advice?  Stop fretting and get on with using this great little 
library.  There's a lot more profit in that than there is in worrying 
about the unlikely event of a lawsuit that can't be collected on.


Clay Dowling
--
http://www.lazarusid.com/notes/
Lazarus Notes
Articles and Commentary on Web Development


Re: [sqlite] Re: 'int n' parameter in sqlite3_bind_*() functions

2005-06-04 Thread Kiel W.
Thanks Kurt. After reading the archive you posted I remembered reading it a 
few days ago when it came across! So much for my memory :-)

On 6/4/05, Kurt Welgehausen <[EMAIL PROTECTED]> wrote:
> 
> http://www.mail-archive.com/sqlite-users@sqlite.org/msg08319.html>
> >
> 



-- 
Kiel W.
[EMAIL PROTECTED]
--
>> time is swift <<


Re: [sqlite] Re: 'int n' parameter in sqlite3_bind_*() functions

2005-06-04 Thread Kurt Welgehausen



[sqlite] Re: 'int n' parameter in sqlite3_bind_*() functions

2005-06-04 Thread Kiel W.
Sorry... hit a wrong key...


What is the 'int n' parameter used for in the sqlite3_bind_*() functions. 
The one I am speciffically looking at is:

 int sqlite3_bind_text(sqlite3_stmt*, int, const char*, int n, void(*)(void*));


And it would be the forth parameter. I didn't see any reference to it in the 
documentation at: http://www.sqlite.org/capi3ref.html#sqlite3_prepare


-- 
Kiel W.
[EMAIL PROTECTED]
--
>> time is swift <<


[sqlite] 'int n' parameter in sqlite3_bind_*() functions

2005-06-04 Thread Kiel W.
What is the 'int n' parameter used for in the sqlite3_bind_*() functions. 
The one I am speciffically looking at is:

-- 
Kiel W.
[EMAIL PROTECTED]
--
>> time is swift <<


[sqlite] Newbie sql: query and joining more than two tables

2005-06-04 Thread Karim Ryde
Hi!

I hope to get some feedback whether the query time is what I should expect.
Running this query below takes several seconds - typically 1-3s. 

SELECT  package.id, package.name, package.description, 
package.size, package.latest, version.version
FROMcategory, package, version
WHERE   package.idCategory = category.id
AND category.name = '" + category + "'"
AND version.idPackage = package.id "
ORDER BY lower( package.name );

The three tables are like this:
CREATE TABLE category ( id INTEGER UNIQUE, 
name VARCHAR(32) );
CREATE INDEX index_name ON category ( name );

CREATE TABLE package (  id INTEGER UNIQUE, 
idCategory INTEGER,  
name VARCHAR(32), 
latest VARCHAR(32), 
description VARCHAR(255), 
size VARCHAR(32), 
keyword VARCHAR(32));
CREATE INDEX index_name ON package ( name );

CREATE TABLE version (  id INTEGER UNIQUE,
idPackage INTEGER,
version VARCHAR(32),
date VARCHAR(32));

The table category has 136 rows, package 9379 rows and version 19369 rows.

Regards,
/Karim


[sqlite] Connecting to SQLite with Crystal Reports Writer

2005-06-04 Thread RAY BORROR
Users,

I am wanting to connect to a SQLite DB with CRW.
Has anyone had any experience doing this?
I was thinking of using the SQLite ODBC Driver.

Any help would be appreciated

Ray Borror


Re: [sqlite] Re: philosophy behind public domain?

2005-06-04 Thread Eugene Wee
Well, since D. Richard Hipp would be the copyright holder if SQLite was 
licensed, that would be up to him, but he hasnt replied to the update yet.


If the licensing policy changes, probably the MIT license or (new/revised) BSD 
license would be good choices, though it seems to me (as a non-lawyer) that 
Larry Rosen's AFL would provide better protection against patent problems - but 
then whether or not it really would affect GPLed code is debatable, and that's 
not fun if you're just interested in coding.


Eugene Wee

Darren Duncan wrote:
Considering everything brought forth here, can anyone think of a reason 
not to have SQLite officially released from now on under a permissive 
free software license like the modified BSD license or the very similar 
X11 license?  Aside from a bit of time to search-n-replace some text, 
what would we stand to lose from such an action? -- Darren Duncan