wow, I really have to learn much more about the SQL, thanks for your great
help!
-Original Message-
From: Dennis Cote [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 11, 2006 7:13 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] How to handle large amount of data?
André Goliath
André Goliath wrote:
Unless you have ebtter suggestions my DB will look like this.
('Takes' are the objects)
CREATE TABLE [takefields]
(
[take] integer NOT NULL ,
[field] integer NOT NULL ,
[content] memo,
PRIMARY KEY ([field])
);
Primary keys must be unique. You will have
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 11, 2006 1:00 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] How to handle large amount of data?
André Goliath wrote:
>Do you (or anyone else) have any experience with those large DBs in terms
of
>SELECT execution times?
>ms, seconds o
André Goliath wrote:
Do you (or anyone else) have any experience with those large DBs in terms of
SELECT execution times?
ms, seconds or minutes?
Since I would mainly use field numbers in the WHERE clause I´d create an
index on them I guess?
With an index on the field number and the
: Dennis Cote [mailto:[EMAIL PROTECTED]
Sent: Monday, April 10, 2006 10:23 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] How to handle large amount of data?
André Goliath wrote:
>Denis,
>I didn´t knew references where possible in Sqlite 3.2,
>thanks for pointing that out!
>
>
André Goliath wrote:
Denis,
I didn´t knew references where possible in Sqlite 3.2,
thanks for pointing that out!
The reference keyword in the column declaration doesn't really do
anything in SQLite. I use it more as a comment for human readers so they
know which column to use when joining
Subject: Re: [sqlite] How to handle large amount of data?
On 4/10/06, André Goliath <[EMAIL PROTECTED]> wrote:
> Good point ;)
>
> I´m a bit branded when it comes to joins since I once had a co-worker that
> created
> an mySQL join resulting in the cartesian product of two 1GB Ta
On 4/10/06, André Goliath <[EMAIL PROTECTED]> wrote:
> Good point ;)
>
> I´m a bit branded when it comes to joins since I once had a co-worker that
> created
> an mySQL join resulting in the cartesian product of two 1GB Tables ;)
> But I guess that won´t happen this time, would it?
LOL! Crashed
: Monday, April 10, 2006 8:54 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] How to handle large amount of data?
André Goliath wrote:
>HI List,
>
>I´m curently in the design phase of a rather large DB project
>and would love to hear your qualified thoughts on this.
>
André Goliath wrote:
HI List,
I´m curently in the design phase of a rather large DB project
and would love to hear your qualified thoughts on this.
You can think of the data to be stored as objects with some properties, an
unique ID and then 21 fields which will contain TEXT data,
The DB
On 4/10/06, André Goliath <[EMAIL PROTECTED]> wrote:
>
> All objects need to contain all fields, however not all will be filled.
> It may be the case that the user wants to UPDATE a field that was empty
> before, it´s not read-only.
>
> btw, I´m using Sqlite 3.2
Have you looked at the full text
Sprenkle [mailto:[EMAIL PROTECTED]
Sent: Monday, April 10, 2006 7:43 PM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] How to handle large amount of data?
On 4/10/06, André Goliath <[EMAIL PROTECTED]> wrote:
> HI List,
>
> I´m curently in the design phase of a rather large DB proj
On 4/10/06, André Goliath <[EMAIL PROTECTED]> wrote:
> HI List,
>
> I´m curently in the design phase of a rather large DB project
> and would love to hear your qualified thoughts on this.
>
> You can think of the data to be stored as objects with some properties, an
> unique ID and then 21 fields
13 matches
Mail list logo
