Hi,
I made another post related to this since the topic changed.
Problem was solved using sqlite3_prepare_v2() instead of sqlite3_prepare().
All is fine now ! :)
Oyvind
On Wed, Nov 26, 2008 at 5:41 PM, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
>
> On Nov 26, 2008, at 11:02 AM, Oyvind
On Nov 26, 2008, at 11:02 AM, Oyvind Idland wrote:
> Seems my problem are related to sqlite not handling multiple prepared
> statements properly.
Before every release of SQLite, we run scripts that do literally
millions of prepared statements. They all work correctly before we
make the
Seems my problem are related to sqlite not handling multiple prepared
statements properly.
Oyvind
On Tue, Nov 25, 2008 at 6:25 PM, Oyvind Idland <[EMAIL PROTECTED]>wrote:
> Thanks for the reply,
>
> I misunderstood the concept of dimensions here (i have fairly good
> knowledge about r-trees)
Thanks for the reply,
I misunderstood the concept of dimensions here (i have fairly good knowledge
about r-trees)
Still i am stuck with binding values, and cant really figure out why
(possibly been looking
myself blind on the code ?)
Here is a portion of the code that shows what I do, the bind
On Tue, Nov 25, 2008 at 01:26:48PM +0100, Oyvind Idland scratched on the wall:
> Hi,
>
> as far as I can see from docs, the r-tree extension uses 32-bit floats to
> store rectangles.
>
> However, when I try to insert this one
>
> INSERT INTO points_index (id, x, y) VALUES (3, 731.293, 74.463);
Hi,
as far as I can see from docs, the r-tree extension uses 32-bit floats to
store rectangles.
However, when I try to insert this one
INSERT INTO points_index (id, x, y) VALUES (3, 731.293, 74.463);
i get "SQL error: constraint failed".
Reducing the x to 31.293 works.
Is the r-tree limitied
6 matches
Mail list logo