Re: [sqlite] understanding the logic of licensing various parts of the sqlite family

On Thu, Jun 24, 2010 at 3:19 PM, Richard Hipp wrote: > On Thu, Jun 24, 2010 at 4:15 PM, P Kishor wrote: > >> >> Right then. That explains #3 above. Are you saying that #5 is >> available for a fee? And, is there a description of #5 and how it >> differs from

Re: [sqlite] understanding the logic of licensing various parts of the sqlite family

On Thu, Jun 24, 2010 at 4:15 PM, P Kishor wrote: > > Right then. That explains #3 above. Are you saying that #5 is > available for a fee? And, is there a description of #5 and how it > differs from #4? Not that I will understand the differences, nor will > I ever need it. I

Re: [sqlite] understanding the logic of licensing various parts of the sqlite family

On Thu, Jun 24, 2010 at 3:04 PM, Richard Hipp wrote: > On Thu, Jun 24, 2010 at 3:58 PM, P Kishor wrote: > >> I am simply curious, and want to expand my knowledge of this -- >> >> 1. sqlite3 code is in public domain. >> 2. sqlite mark is trademarked. >> 3.

Re: [sqlite] understanding the logic of licensing various parts of the sqlite family

On Thu, Jun 24, 2010 at 3:58 PM, P Kishor wrote: > I am simply curious, and want to expand my knowledge of this -- > > 1. sqlite3 code is in public domain. > 2. sqlite mark is trademarked. > 3. sqlite3 encryption extension is licensed and for a fee, and comes > with a

[sqlite] understanding the logic of licensing various parts of the sqlite family

I am simply curious, and want to expand my knowledge of this -- 1. sqlite3 code is in public domain. 2. sqlite mark is trademarked. 3. sqlite3 encryption extension is licensed and for a fee, and comes with a contract to not distribute it further. 4. sqlite code tests are available as long as they