[sqlite] Share an sqlite3 struct between multiple threads

I know based on http://www.sqlite.org/faq.html#q8 that it is not safe to share the same sqlite3 structure between multiple threads. But what if I protect its access with a mutex? It is safe? --- Marco Bambini

Re: [sqlite] Problem with floating point fields, and a feature request

On 9/20/05, Cariotoglou Mike <[EMAIL PROTECTED]> wrote: > > nothing, when you hand-code. everything, when the code is > auto-generated, which very frequently it is Automatically generated bad code is still bad code. If it's generating floating point comparisons now it's bad code. It only works

RE: [sqlite] Problem with floating point fields, and a feature request

also, it kills the usage of indexes, whereas what I propose would not. > -Original Message- > From: Jay Sprenkle [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 20, 2005 5:04 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Problem with floating point fields, and > a

RE: [sqlite] Problem with floating point fields, and a feature request

nothing, when you hand-code. everything, when the code is auto-generated, which very frequently it is > -Original Message- > From: Jay Sprenkle [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 20, 2005 5:04 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Problem with

RE: [sqlite] Problem with floating point fields, and a feature request

collating sequences do not apply to floating point comparisons, do they ? > -Original Message- > From: Dan Kennedy [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 20, 2005 5:12 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] Problem with floating point fields, and > a

Re: [sqlite] Problem with floating point fields, and a feature request

> two floats A and B should be compared with this algorithm : > > diff=A-B > if (diff>tolerance) then A>B > else if (diff<-tolerance) then A else A = B You could define a new collation sequence to do all that. However, it's difficult to say what will happen when you have three numbers A, B and

Re: [sqlite] Problem with floating point fields, and a feature request

On 9/20/05, Cariotoglou Mike <[EMAIL PROTECTED]> wrote: > > There is an issue with floating point fields, which exists in every > database I have dealt with, and of course exists in sqlite as well, all > versions. > Essentially, the issue is this: > > "When are two floating point values considered

[sqlite] Problem with floating point fields, and a feature request

There is an issue with floating point fields, which exists in every database I have dealt with, and of course exists in sqlite as well, all versions. Essentially, the issue is this: "When are two floating point values considered equal ?" Why is this an issue ? Floating point values are some

RE: [sqlite] problems compiling 3.2.6

drh already fixed it. see http://www.sqlite.org/cvstrac/chngview?cn=2720 > -Original Message- > From: Maurizio Ferraris [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 20, 2005 4:13 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] problems compiling 3.2.6 > > I also have

RE: [sqlite] problems compiling 3.2.6

Or download the CVS version, it has already been fixed by drh in there! -Oorspronkelijk bericht- Van: Maurizio Ferraris [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 20 september 2005 15:13 Aan: sqlite-users@sqlite.org Onderwerp: Re: [sqlite] problems compiling 3.2.6 I also have the same

Re: [sqlite] problems compiling 3.2.6

I also have the same problems with VC6, and unfortunately I cannot switch to VC7 for other reasons. At the moment I reverted back to 3.2.5. When I will have some spare time I will try to fix it myself and I will inform the list. My guess is: update too the latest SDK (that unfortunately does not

Re: [sqlite] group by error in 3.2.6?

Edzard Pasma wrote: There is a difference in the behaviour of GROUP BY in version 3.2.6. If you group by a column that contains NULL values, each NULL value comes on a seperate output line. Conceptually not so bad, if we read NULL as "unknown" and not as "empty". But I guess it is an error.

Re[2]: [sqlite] Storing RTF text in a field

Hello, Use functions sqlite3_prepare(), then sqlite3_bind_blob to assign RTF text to a blob parameter Tuesday, September 20, 2005, 5:39:59 PM, you wrote: >> Now when I try to save it to database, I get an error: unrecognized token: >> "\". What should I do? -- Best regards Sergey Startsev

[sqlite] group by error in 3.2.6?

There is a difference in the behaviour of GROUP BY in version 3.2.6. If you group by a column that contains NULL values, each NULL value comes on a seperate output line. Conceptually not so bad, if we read NULL as "unknown" and not as "empty". But I guess it is an error. For the rest I'm very

Re: [sqlite] Storing RTF text in a field

Simple convert it to 2byte hex "0AFF00..." etcc. So the update query should use X'your hex data here' - Original Message - From: "Gaurav Patole" <[EMAIL PROTECTED]> To: Sent: Tuesday, September 20, 2005 7:14 AM Subject: [sqlite] Storing RTF text in a field

Re: [sqlite] Re: query problem

On Tue, 2005-09-20 at 06:57 +0200, Alain Bertrand wrote: > Do you have an approximativ dateframe to see > this fix incorporated in a release ? > No. The problem is obscure so I am not in a big rush to get it out. You can fix the problem in your copy by downloading the latest from CVS. Or you