Nikki Locke wrote:
JOOI, were you on CIX?
Still am.
Thought the name was familiar. I don't get on much these days. :-/
Martin
-
To unsubscribe, send email to [EMAIL PROTECTED]
To save someone the trouble, it's about 2924 centuries. :-)
--BQ
[EMAIL PROTECTED] wrote:
Dixon Hutchinson <[EMAIL PROTECTED]> wrote:
If I actually specify AUTOINCREMENT, then an insert will fail when I
have reached the max row value, even if there are unused rows in the
table. So I
I know.
I checked them all and at least they are dangerous and probably not obvious.
I think the one in os_win.c is really a bug unless the intention were to
always return OK.
-
To unsubscribe, send email to [EMAIL
hidden variables might very well not be a problem, if it was done that
way on purpose.
On 8/30/06, Miguel Angel Latorre Díaz <[EMAIL PROTECTED]> wrote:
I already filtered out all the "common" warnings but these:
build.c(1969): remark #1599: declaration hides variable "v" (declared at
line
I already filtered out all the "common" warnings but these:
build.c(1969): remark #1599: declaration hides variable "v" (declared at
line 1883)
Vdbe *v = sqlite3GetVdbe(pParse);
^
expr.c(1520): remark #1599: declaration hides variable "op" (declared at
line 1489)
Martin Jenkins wrote:
> Nikki Locke wrote:
> > Martin Jenkins wrote:
> > Using [] is a Microsoft thing. More portable to use double quotes...
>
> Thanks, I didn't know that. I avoid spaces in column names so I haven't
> actually use it in anger.
>
> JOOI, were you on CIX?
Still am.
--
On Wed, 30 Aug 2006 [EMAIL PROTECTED] wrote:
> > I have to go along with Mario, here. This is a potential show stopper,
>
> Show stopper? Really? The bug has been there for years, literally,
> and nobody has even noticed it until now - despite thousands of users
> and millions and millions of
Roger wrote:
But is this a Code design issue because Between A and D is supposed to
be inclusive.
It is. Any Surname which consists of the single character "D" will be
included. Which is just what you told sqlite to check for.
You need to check for the first char of the name being
Rob Sciuk <[EMAIL PROTECTED]> wrote:
> On Wed, 30 Aug 2006, Mario Frasca wrote:
> > On 2006-0829 13:15:02, [EMAIL PROTECTED] wrote:
> >
> > >> To my surprise (perhaps "horror") I find that SQLite has
> > >> for a very long time allowed NULL values in PRIMARY KEY
> > >> columns. [...]
> >
> > I
Has anybody tried to estimate how many end-users are using sqlite? This
would include actual firefox users and users of any other product that
uses sqlite.
Somebody asked me, "how many people are using sqlite" (or sqlite based
products)?
jp.
On Wed, 30 Aug 2006, Mario Frasca wrote:
> On 2006-0829 13:15:02, [EMAIL PROTECTED] wrote:
>
> >> To my surprise (perhaps "horror") I find that SQLite has
> >> for a very long time allowed NULL values in PRIMARY KEY
> >> columns. [...]
>
> I understand your concern about legacy programs, but most
Dixon Hutchinson wrote:
But I need ROWID to auto increment until the largest 64-bit integer
value is used
You'll never get there - 2^64 is huge. 2^31 seconds is about 68 years so
even if you're getting billions of inserts/sec you'll be dead before the
rowid wraps.
Martin
> 9,223,372,036,854,775,807 / (1,000,000 * 60seconds * 60minutes * 24hours *
> 365days) = 292471 years
>
> On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>> The maximum rowid is 9223372036854775807. You're going to take
>> a long time to reach that value if you start with 1.
>>
>> Do
It's great to design your application to be future proof and all, but I
think Dr. Hipp has a point: that failure point probably isn't in your
lifetime, or the lifetime of 32 bit computing.
Do you have a particular reason for needing this behavior, other than your
own desires? If choosing
I did the math once, came to the same conclusion, then somewhere in the
last moths, forgot it and slipped into 32-bit mode for some reason :-[
Specifying AUTOINCREMENT should work fine for what I need.
[EMAIL PROTECTED] wrote:
Dixon Hutchinson <[EMAIL PROTECTED]> wrote:
If I actually
9,223,372,036,854,775,807 / (1,000,000 * 60seconds * 60minutes * 24hours *
365days) = 292471 years
On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
The maximum rowid is 9223372036854775807. You're going to take
a long time to reach that value if you start with 1.
Do the math: If you
Brandon,
I think you tickled the right neurons. I misread the SQLite web page.
Below is the statement from the web page. The italics is how I
mis-interpreted it.
If no ROWID is specified on the insert, an appropriate ROWID is
created automatically. The usual algorithm is to give the
But "AUTOINCREMENT" has slightly different behavior that what I desire.
The difference is what happens when the ROWID reaches the "largest
possible integer". If AUTOINCREMENT is specified, then the next insert
after "largest possible integer" is reach will fail, regardless of the
Dixon Hutchinson <[EMAIL PROTECTED]> wrote:
>
> If I actually specify AUTOINCREMENT, then an insert will fail when I
> have reached the max row value, even if there are unused rows in the
> table. So I don't want to specify AUTOINCREMENT.
>
The maximum rowid is 9223372036854775807. You're
Dixon Hutchinson wrote:
H:\b>sqlite3.exe t.dat
SQLite version 3.3.7
Enter ".help" for instructions
sqlite> CREATE TABLE abc
...> (
...> c TEXT,
...> p INTEGER,
...> t TEXT,
...> masked INTEGER PRIMARY KEY,
...>
* Nikki Locke <[EMAIL PROTECTED]> [2006-08-30 14:40]:
> Using [] is a Microsoft thing. More portable to use double
> quotes...
I’d use the square brackets anyway.
sqlite> create table foo ( "bar baz" text );
sqlite> insert into foo values ( "quux" );
OK…
sqlite> select [bar baz]
I thought actually specifying a ROWID would be harmless. So I tried
your idea, same results:
H:\b>sqlite3.exe t.dat
SQLite version 3.3.7
Enter ".help" for instructions
sqlite> CREATE TABLE abc
...> (
...> c TEXT,
...> p INTEGER,
...>
ROWID is a reserved word. Each row has one and you don't need to specify
it. In fact you probably shouldn't, since it seems to be causing you
problems.
If you want the column to be explicitly declared in your table, call it
something else like id. If you don't want to do that just use the
Nikki Locke wrote:
Martin Jenkins wrote:
Using [] is a Microsoft thing. More portable to use double quotes...
Thanks, I didn't know that. I avoid spaces in column names so I haven't
actually use it in anger.
JOOI, were you on CIX?
Martin
Roger <[EMAIL PROTECTED]> wrote:
> I have a question.
>
> I trying to write a query as follows
>
> Select *
> >From People
> Where Surname Between 'A%' and 'E%'
> Order by UPPER(Surname);
>
> Now the problem i have is that i get only the Surnames from A up to D
> and the E's are excluded.
>
On Wed, 2006-08-30 at 13:33 +0200, Arjen Markus wrote:
> Roger wrote:
>
> >On Wed, 2006-08-30 at 12:03 +0100, Martin Jenkins wrote:
> >
> >
> >>Roger wrote:
> >>
> >>
> >>>I have a question.
> >>>
> >>>I trying to write a query as follows
> >>>
> >>>Select *
> From People
> >>>Where
Arjen Markus wrote:
Well, the character after 'Z' is 'a' in the ASCII table. You could try:
BETWEEN 'Z' and 'a'
Not quite. It's "XYZ[\]^_`abc".
Martin
-
To unsubscribe, send email to [EMAIL PROTECTED]
Roger wrote:
Thanks for the response guys but then my problem comes when i try and
query a range between T and Z i tried to make it query between T to A
but got no result. Anyway i will have to add a constraint in my PHP code
for T to Z.
I saw that coming, but you didn't ask about that bit. ;)
Roger wrote:
On Wed, 2006-08-30 at 12:03 +0100, Martin Jenkins wrote:
Roger wrote:
I have a question.
I trying to write a query as follows
Select *
From People
Where Surname Between 'A%' and 'E%'
Order by UPPER(Surname);
Now the problem i have is that i get only the Surnames from
On Wed, 2006-08-30 at 12:03 +0100, Martin Jenkins wrote:
> Roger wrote:
> > I have a question.
> >
> > I trying to write a query as follows
> >
> > Select *
> >>From People
> > Where Surname Between 'A%' and 'E%'
> > Order by UPPER(Surname);
> >
> > Now the problem i have is that i get only the
Roger wrote:
I have a question.
I trying to write a query as follows
Select *
From People
Where Surname Between 'A%' and 'E%'
Order by UPPER(Surname);
Now the problem i have is that i get only the Surnames from A up to D
and the E's are excluded.
Can anyone help me out, i am writing a web
Roger wrote:
I have a question.
I trying to write a query as follows
Select *
From People
Where Surname Between 'A%' and 'E%'
Order by UPPER(Surname);
Now the problem i have is that i get only the Surnames from A up to D
and the E's are excluded.
Can anyone help me out, i am writing a web
Sripathi Raj wrote:
This is on a NFS on Windows XP Xeon - 2.8 Ghz, 1 Gig RAM and the database
size is 395 MB. I'm connecting to the database from Perl. There is no
discernible difference b/w Perl and sqlite shell.
NFS? Hmm... You have been following the locking threads, haven't you? ;)
How
I have a question.
I trying to write a query as follows
Select *
>From People
Where Surname Between 'A%' and 'E%'
Order by UPPER(Surname);
Now the problem i have is that i get only the Surnames from A up to D
and the E's are excluded.
Can anyone help me out, i am writing a web based
T wrote:
Hi all,
I've just joined this mail list.
I've read through the syntax page and other sources as to how to
create a table using SQLite, and it's all working fine. But I can't
find any specifications for the format of a column name. Does the
spec permit spaces in the name? It seems to
On 2006-0829 13:15:02, [EMAIL PROTECTED] wrote:
To my surprise (perhaps "horror") I find that SQLite has
for a very long time allowed NULL values in PRIMARY KEY
columns. [...]
I understand your concern about legacy programs, but most of us expect PRIMARY
KEY to imply NOT NULL... don't
Sripathi Raj wrote:
> This is on a NFS
If you really mean that then you have two problems.
#1 - http://www.sqlite.org/faq.html#q7
The second is that you have network and server latency in addition to
disk latency for all disk accesses. When iterating over so much data,
those latencies soon add
Hi,
This is on a NFS on Windows XP Xeon - 2.8 Ghz, 1 Gig RAM and the database
size is 395 MB. I'm connecting to the database from Perl. There is no
discernible difference b/w Perl and sqlite shell.
Raj
On 8/29/06, Martin Jenkins <[EMAIL PROTECTED]> wrote:
Sripathi Raj wrote:
> Main
38 matches
Mail list logo
