I am an application programmer by trade, programming accountancy and
inventory type packages using various SQLs.
2000 columns/tableis plenty for my use. I do not see needing to go
above that in any scneario. If the need requires that you do need to go
above that either the database design is
[EMAIL PROTECTED] wrote:
>Darn, I was going to have 500,000 columns in my table. The, each column
>would be named like this: Record1, Record2, Record3, and so on up to
>Record500. Each column type was going to be varchar and I was going to
>store my first record in xml format in my Record1 col
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 17, 2005 10:44 AM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] Proposal: limit the number of columns
> in a table to 2000.
>
> Darn, I was going to
It seems a multidimentional or hash file. Am i right?
There are different ways to fisically store the data
with gain of simplicity.
Cláudio Leopoldino
--- [EMAIL PROTECTED] wrote:
> Darn, I was going to have 500,000 columns in my
> table. The, each column
> would be named like this: Record1, Rec
Darn, I was going to have 500,000 columns in my table. The, each column
would be named like this: Record1, Record2, Record3, and so on up to
Record500. Each column type was going to be varchar and I was going to
store my first record in xml format in my Record1 column of the first row,
and so o
> > > There is code in SQLite that has to deal with the general
> > > case of tables with millions or billions of columns. That
> > > code can be simplified (and made faster) if we know that
> > > the maximum number of columns is some reasonable limit,
> > > such as 2000.
> >
> > Oh. Go for it!
-Original Message-
From: Jay [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 17, 2005 10:32 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Proposal: limit the number of columns in a table
to 2000.
> > A stupid question:
> >
> > Why introduce more code, one
> > A stupid question:
> >
> > Why introduce more code, one more thing to test,
> > and possibly bugs? Is there a problem that needs fixing?
> >
>
> There is code in SQLite that has to deal with the general
> case of tables with millions or billions of columns. That
> code can be simplified
There is an difference about technical limit and
practical. I think that a good number is 2048 or 1024.
Are more "binary".
Adding information:
Using DBase, i found that the limit was 128 columns.
Cláudio Leopoldino
--- "D. Richard Hipp" <[EMAIL PROTECTED]> wrote:
> On Thu, 2005-03-17 at 09:09
I agree, it's like creating one object (C++, Java, C#) in an application
with 40,000 methods, you might be using an object oriented language but
you aren't using OO techniques. I would hone it down before SQLite
developers exploit this and you're stuck supporting it, it could come back
to haunt you
On Thu, 2005-03-17 at 08:39 -0700, David Fletcher wrote:
> > "DRH" == D Richard Hipp <[EMAIL PROTECTED]> writes:
>
> DRH> On Thu, 2005-03-17 at 06:32 -0500, D. Richard Hipp wrote:
> >> I am proposing to limit the value of K to something like 2000.
> >>
>
> DRH> Further study shows that in or
Off topic, but people creating tables with that number of columns
should really think about normalizing their data structures.
-- Gerhard
signature.asc
Description: Digital signature
> "DRH" == D Richard Hipp <[EMAIL PROTECTED]> writes:
DRH> On Thu, 2005-03-17 at 06:32 -0500, D. Richard Hipp wrote:
>> I am proposing to limit the value of K to something like 2000.
>>
DRH> Further study shows that in order to implement the
DRH> optimizations I have in mind, I'll need to l
D. Richard Hipp said:
> As currently implemented, there is no fixed limit to the number
> of columns you can put in a table in SQLite. If the CREATE TABLE
> statement will fit in memory, then SQLite will accept it. Call
> the number of columns in a table K. I am proposing to limit the
> value o
On Thu, 2005-03-17 at 06:32 -0500, D. Richard Hipp wrote:
> I am proposing to limit the value of K to something like 2000.
>
Further study shows that in order to implement the
optimizations I have in mind, I'll need to limit the
number of columns in a single table to 1820. That is
still more tha
> So who out there needs a value of K larger than 2000?
> What is the largest K that anybody is using? Who would
> object if I inserted a limit on K that was in the range
> of 1000 or 2000?
I have never, in SQLite or any other SQL DB product I've worked with,
created or used a table with more tha
On Thu, 2005-03-17 at 09:09 -0600, Fred Williams wrote:
> BTW, Most of the "enterprise" database engines I have worked with have
> had either published or "stealth" column count limits. All those that I
> remember were below 2000. But I must admit I have not worked with any
> of the current releas
On Thu, 2005-03-17 at 06:52 -0800, Jay wrote:
> A stupid question:
>
> Why introduce more code, one more thing to test,
> and possibly bugs? Is there a problem that needs fixing?
>
There is code in SQLite that has to deal with the general
case of tables with millions or billions of columns. T
I must admit I have not worked with any
of the current releases of the "big boys."
Fred
-Original Message-
From: Bert Verhees [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 17, 2005 6:38 AM
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Proposal: limit the number of columns
A stupid question:
Why introduce more code, one more thing to test,
and possibly bugs? Is there a problem that needs fixing?
It certainly will not cause me any problems.
--- "D. Richard Hipp" <[EMAIL PROTECTED]> wrote:
> As currently implemented, there is no fixed limit to the number
> of col
as a suggestion to the list, this issue should be answered only by those
that disagree, else we will get 2k messages saying why not..
How about a constant that can be changed at compile time?
D. Richard Hipp wrote:
As currently implemented, there is no fixed limit to the number
of columns you can put in a table in SQLite. If the CREATE TABLE
statement will fit in memory, then SQLite will accept it. Call
the number of columns in
I cannot imagine ever needing more then 2000 columns in a table, if I
would, I could always create a parallel table
As currently implemented, there is no fixed limit to
the number
of columns you can put in a table in SQLite. If the
CREATE TABLE
statement will fit in memory, then SQLite will
a
It's rarely a good idea to use binary numbers for limits such as that -
you're exposing yourself to more corner case bugs.
Interesting issue...
I thing that we may use 2048 instead 2000. It´s an
number more "binary". I think that it´s sufficient to
99.99% of the possible applications.
That´s a go
I've got no problem with that. Frankly I think if you have a sqlite
table in real-life with that many columns you are probably doing
something wrong :)
On Thu, 17 Mar 2005 06:32:55 -0500, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
> As currently implemented, there is no fixed limit to the number
Interesting issue...
I thing that we may use 2048 instead 2000. It´s an
number more "binary". I think that it´s sufficient to
99.99% of the possible applications.
That´s a good idea. The DBase accepted 128 collumns
and that is my reference. I've need more than this.
In a future development thi
As currently implemented, there is no fixed limit to the number
of columns you can put in a table in SQLite. If the CREATE TABLE
statement will fit in memory, then SQLite will accept it. Call
the number of columns in a table K. I am proposing to limit the
value of K to something like 2000.
Woul
27 matches
Mail list logo