Lothar Märkle <[EMAIL PROTECTED]> writes:
>>> Assuming you have a cgi-like application with many processes
>>> that just looks up a row, displays and then exits. You can
>>> simple use the rename call to atomically replace the db file
>>> (see man 2 rename for bordercases) with another and
On Sat, 12 Mar 2005, Andrew Piskorski wrote:
On Sat, Mar 12, 2005 at 10:03:25AM -0700, Ara.T.Howard wrote:
does anyone have a strategy for doing massive updates to a db and atomicly
replacing it in a multi-process situation?
Why would you want to do that? SQLite properly supports transactions, so
I'm in the airline game. 379 columns is the widest table that I can find in
our production DB2 sub-systems - a highly denormalised table as I'm sure you
can imagine. Perhaps someone like FedEx or UPS may have requirements to go
real wide for their warehousing apps.
Nothing I can find in this big
On Mar 17, 2005, at 4:27 PM, Kurt Welgehausen wrote:
Well, I might as well use the substr() function, then ...
Yes, unless you think %m is more expressive than 6,2 or
you want to extract more than one component.
sqlite> select * from datetest;
k d
-- ---
1
Hi,
I was wondering there is a roadmap of SQLite since many users are
concerning what will the upcoming SQLite look like. :)
_
与世界各地的朋友进行交流，免费下载 MSN Messenger:
http://messenger.msn.com/cn
> Well, I might as well use the substr() function, then ...
Yes, unless you think %m is more expressive than 6,2 or
you want to extract more than one component.
sqlite> select * from datetest;
k d
-- ---
1 2005-03-17T16:21:30
2
On Mar 17, 2005, at 2:59 PM, Kurt Welgehausen wrote:
Sorry, I misunderstood the context.
No problem.
sqlite> select * from datetest;
k d
-- ---
1 2005-03-17T16:21:30
sqlite> select strftime("%m", substr(d,1,10)||' '||substr(d,-8,8))
Sorry, I misunderstood the context.
sqlite> select * from datetest;
k d
-- ---
1 2005-03-17T16:21:30
sqlite> select strftime("%m", substr(d,1,10)||' '||substr(d,-8,8))
...> from datetest;
strftime("%m",
On Mar 17, 2005, at 2:21 PM, Matt Sergeant wrote:
You can force the binding type in DBD::SQLite - see the DBI docs (grep
for ":sql_types").
True, but in our application, that would require a lot more
book-keeping than we'd like. Adding "+0" seems to do the cast we need
to keep up with how
On Mar 17, 2005, at 2:24 PM, Kurt Welgehausen wrote:
Yes, I know it supports it without the "T" ...
sqlite> select strftime("%Y-%m-%dT%H:%M:%S", 'now', 'localtime');
strftime("%Y-%m-%dT%H:%M:%S", 'now', 'localtime')
-
2005-03-17T16:21:30
No:
sqlite>
> Yes, I know it supports it without the "T" ...
sqlite> select strftime("%Y-%m-%dT%H:%M:%S", 'now', 'localtime');
strftime("%Y-%m-%dT%H:%M:%S", 'now', 'localtime')
-
2005-03-17T16:21:30
On 17 Mar 2005, at 15:13, David Wheeler wrote:
Probably off-topic for a SQLite list :-)
I'm not sure Perl will cast a non-numeric string
("2005-03-22T00:00:00") to a number. What number are you
looking for?
Actually the code that was cast was "substr(a, 6, 2)", which was
evaluating to "03", and
John O'Neill wrote:
Hi Dennis,
Thanks for the reply. In the original "INSERT" commands, my intention was to update a field in the
columns as they were being copied to the new table. Sorry, I didn't mean just "SELECT ... WHERE
id=1" as the only condition...I'd like to select those items and
Unfortunately, as the syntax on the website points out, this is not
supported. As you pointed out previously, it is doable with a few extra
commands.
Bob
Envision Information Technologies
Associate
[EMAIL PROTECTED]
v. 608.256.5680
f. 608.256.3780
-Original Message-
From: John
On Mar 17, 2005, at 1:23 PM, Kurt Welgehausen wrote:
strftime doesn't support the ISO-8601 format ...
I does if you give it the correct format string.
Yes, I know it supports it without the "T", but ISO-8601 mandates the
presence of the T.
Regards,
David
Hi Dennis,
Thanks for the reply. In the original "INSERT" commands, my intention was to
update a field in the columns as they were being copied to the new table.
Sorry, I didn't mean just "SELECT ... WHERE id=1" as the only condition...I'd
like to select those items and update their primary
John O'Neill wrote:
Hello all,
I have a fairly simple DB with two tables. I'm trying to combine a SELECT and
UPDATE command, if it is possible:
CREATE TABLE a (id PRIMARY KEY, data INT);
CREATE TABLE b (id INT, data INT);
INSERT INTO a VALUES( 1, 100 );
INSERT INTO b VALUES( 1, 101 );
INSERT
> Is there a way to do the following:
>
> INSERT INTO acopy SELECT * FROM a WHERE id = 1 ( SET id = some value X );
> INSERT INTO bcopy SELECT * FROM b WHERE id = 1 ( SET id = X );
http://www.sqlite.org/lang_insert.html
sql-statement ::= INSERT [OR conflict-algorithm] INTO
> strftime doesn't support the ISO-8601 format ...
I does if you give it the correct format string.
Regards
On Thu 17 Mar 05, 4:10 PM, Reid Thompson <[EMAIL PROTECTED]> said:
>
> > I read that in a NSP book awhile ago (Linux Cookbook). It's
> > faster than "%s/ //g". Very handy. But which problem does this
> > address? :)
> >
> > Pete
>
> This is some PHP code on Linux. I suspect it was
> I read that in a NSP book awhile ago (Linux Cookbook). It's
> faster than "%s/ //g". Very handy. But which problem does this
> address? :)
>
> Pete
This is some PHP code on Linux. I suspect it was originally written
> > on a Microsoft operating system because when I edit the files, my
On Mar 17, 2005, at 11:40 AM, Clark Christensen wrote:
Probably off-topic for a SQLite list :-)
I'm not sure Perl will cast a non-numeric string
("2005-03-22T00:00:00") to a number. What number are you
looking for?
Actually the code that was cast was "substr(a, 6, 2)", which was
evaluating to
Hello all,
I have a fairly simple DB with two tables. I'm trying to combine a SELECT and
UPDATE command, if it is possible:
CREATE TABLE a (id PRIMARY KEY, data INT);
CREATE TABLE b (id INT, data INT);
INSERT INTO a VALUES( 1, 100 );
INSERT INTO b VALUES( 1, 101 );
INSERT INTO b VALUES( 1,
--- David Wheeler <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> Given the below script (using DBD::SQLite 1.08, which
> uses SQLite
> 3.1.3), the output is just:
>
>+0 Cast: 2005-03-22T00:00:00
>
> I'm wondering, however, if unary + shouldn't also be able
> to cast an
> expression to a
On Thu 17 Mar 05, 2:26 PM, Reid Thompson <[EMAIL PROTECTED]> said:
> Peter Jay Salzman wrote:
> > Hi Mike,
> >
> > To be perfectly honest, other than being a Microsoft thing, I
> > don't really know what .NET is. Pretty pathetic, huh? :)
> >
> > This is some PHP code on Linux. I suspect it
Peter Jay Salzman wrote:
> Hi Mike,
>
> To be perfectly honest, other than being a Microsoft thing, I
> don't really know what .NET is. Pretty pathetic, huh? :)
>
> This is some PHP code on Linux. I suspect it was originally
> written on a Microsoft operating system because when I edit
> the
Well the [ ] aren't a .NET thing, SQLite supports them, using [ ] are a
standard supported SQLite feature and they make you're life way, way,
easier, see: http://www.sqlite.org/lang_keywords.html
[keyword] A keyword enclosed in square brackets is always understood as
an identifier. This is not
On Thu, 17 Mar 2005 06:56:04 -0500
"D. Richard Hipp" <[EMAIL PROTECTED]> wrote:
> On Thu, 2005-03-17 at 12:39 +0100, Gerald Dachs wrote:
> > Why do you not use my patch? Do you not agree that this is a bug?
> >
>
> No I do not. The arch.png image is no longer used in the
> documentation. It
[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
> -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 have 500,000 columns in my
Hi Eugene,
Yes, this worked great. I just find it hard to believe that it's all
necessary.
Without using sqlite_escape_string, single quotes cause "SQL Logic or
missing database" errors. So I'm forced to use that function on variables
set via a form.
But then to avoid the "backslash in the
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
Hi Mike,
To be perfectly honest, other than being a Microsoft thing, I don't really
know what .NET is. Pretty pathetic, huh? :)
This is some PHP code on Linux. I suspect it was originally written on a
Microsoft operating system because when I edit the files, my editor reports
the textfiles as
> > > 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!
Hi,
Am Donnerstag, 17. März 2005 15:45 schrieb [EMAIL PROTECTED]:
> I agree.
[snip]
I disagree. make doc works fine w/o the patch.
Regrads
Uwe
-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 more thing to test,
> >
Dear All,
I am compiling the new 3.1.6 version using Devcpp (versione 4.9.9.2 using
MINGW with GCC 3.4.2). Compiling the source code
I got the following warning
gcc.exe -c vdbeaux.c -o objects/vdbeaux.o -I"D:/Dev-Cpp/include" -DNO_TCL
-DNDEBUG=-1 -ansi -fexpensive-optimizations -O3
> > 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
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
> I used google to dig up the column count limits on some
> common database engines:
>
> DB2 255
> Oracle 1000
> SQL Server 1024
> PostgreSQL 1600
> MySQL 3398
> Informix 32767
>
Sybase ASE 12.5 - 1024 or 254, depending on whether columns are
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
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
On Thu, Mar 17, 2005 at 09:47:16AM +0800, cross wind wrote:
> Thanks Gehard. Finally, I am seeing the pattern on how the scripts
> ought to be run.
In the pysqlite2 alpha *source* releases, there's a script included to
run tests.
Because it's just that single file, you can download it here,
On Wed, Mar 16, 2005 at 06:45:23PM +0800, cross wind wrote:
> [...]
> ### When ran, I get the ff messages:
>
> C:/PYTHON23/pythonw.exe -u "Z:/devpy/test/sqlite.pyw"
> Traceback (most recent call last):
> File "Z:/devpy/test/sqlite.pyw", line 1, in ?
> import sqlite
> File
> "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
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
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
> 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
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
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.
I'd bet there is someone out there using more than 2000 columns. Either
they probably won't admit it or will be the first to brag about it :-)
I'd say if it relates to performance/footprint the smaller the column
count the better as an upper limit. In over thirty years of consulting
I've seen
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
> What's the proper way to ensure that ' characters are properly quoted but
> don't show up in the output?
Honestly, we use the SQLite .NET managed driver and pass all data in via
parameters, therefore we have no escape issues and more importantly no SQL
injection woes, if you're taking data
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
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
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
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
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
On Thu, 2005-03-17 at 12:39 +0100, Gerald Dachs wrote:
> Why do you not use my patch? Do you not agree that this is a bug?
>
No I do not. The arch.png image is no longer used in the documentation.
It was replaced by arch2.gif some time ago.
> 'make doc' on linux is still broken, attached patch
Why do you not use my patch? Do you not agree that this is a bug?
'make doc' on linux is still broken, attached patch for 3.1.3 still
works.
Gerald
--- sqlite-3.1.3/Makefile.in.orig 2005-03-07 22:56:04.833954328
+0100 +++ sqlite-3.1.3/Makefile.in2005-03-07 22:56:41.189427456
+0100 @@
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.
Anirban Sarkar wrote:
Hi all,
I know that this is a sqlite forum and not the right place to post any TCL
related questions. However, I have posted this question on many TCL forums
including comp.lang.tcl but unfortunately did not get any respond. So just
thought if anyone on this forum can help me
Hi all,
I know that this is a sqlite forum and not the right place to post any TCL
related questions. However, I have posted this question on many TCL forums
including comp.lang.tcl but unfortunately did not get any respond. So just
thought if anyone on this forum can help me out. It is very
64 matches
Mail list logo
