On 8/22/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
SQLite accepts the above and does the right thing with it.
It is the equivalent of saying:
SELECT a FROM (SELECT a,b FROM qqq GROUP BY b);
The subquery here doesn't make any sense to me. How a single 'a' is
chosen for the grouped
--- [EMAIL PROTECTED] wrote:
> "Alexei Alexandrov" <[EMAIL PROTECTED]> wrote:
> > I noticed something like a bug in the SQLite parser: queries with
> > "group by" expression should accept only fields listed in the "group
> > by" clause or aggregated fields (with sum(), max() etc). For example,
> >
"Alexei Alexandrov" <[EMAIL PROTECTED]> wrote:
> I noticed something like a bug in the SQLite parser: queries with
> "group by" expression should accept only fields listed in the "group
> by" clause or aggregated fields (with sum(), max() etc). For example,
> given the table
>
> create table qqq
Tito Ciuro wrote:
Due to application requirements, I must rely on LIKE and GLOB in
order to match data, matching data that contains some value
(sensitive or insensitive match).
Now, it seems to me that using either LIKE or GLOB will force a row
scan anyhow, since it can't use the
Hi Denis,
I've been reading your email carefully and I'd like to comment it.
On 28/03/2006, at 14:24, Dennis Cote wrote:
With these tables you will have 25K rows in the File table, one per
file, and 250K rows in the Attribute table assuming an average of
10 attributes per file (your
Tito,
I am replying off list because I don't want to contribute to turning
this thread into a flame war...
You have shown wonderful patience and politeness on this list. You
have my gratitude and respect for this.
Regards,
e
Tuesday, March 28, 2006, 5:35:37 PM, Tito Ciuro wrote:
> Hi Dennis,
ch 28, 2006 4:24 PM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] [SOLVED] Re: [sqlite] LIKE and GLOB bug with
> numbers?
>
>
> Tito Ciuro wrote:
>
> >
> > I have no idea why you're so angry. Anyway, there are so
...
> While the tone of MGC's post may have been a
Tito Ciuro wrote:
I have no idea why you're so angry. Anyway, there are so many things
I can think of saying, I'll just make it brief and to the point.
This thing won't scale. I'd like to see it when you have the 4.5
million records my database contains,
and that is still tiny for all
John,
Did you read my replies at all? If not, please take 15 seconds to do
so. I thanked *all of you* in all three emails.
Just in case, if that wasn't enough, allow me to do that for the
fourth time: I most sincerely appreciate the time and effort that you
guys have taken to answer my
Tito,
Several people have bothered to spend the time and effort to give you
some well considered help. That is what forums like this are for,
professional guidance and development. Thank them.
Tito Ciuro wrote:
MGC,
I have no idea why you're so angry. Anyway, there are so many things I
MGC,
I have no idea why you're so angry. Anyway, there are so many things
I can think of saying, I'll just make it brief and to the point.
1) Regarding your statement:
This thing won't scale. I'd like to see it when you have the 4.5
million records my database contains,
and that is still
Tito Ciuro wrote:
Oh!... just a quick message for the row-scan non-believers out there:
SQLite flies, even under this scenario. I'm getting wonderful
performance numbers by keeping everything within SQLite-land. The
code is simple and I let SQLite do all the magic. What else can I ask
Hi Martin,
I haven't been able to pick up pace my email until this morning.
Sorry about that.
As it turns out, the error was on my side (surprise). The code seemed
to be working fine: early tests showed data being churned as
expected, so I started cleaning it up and factoring up the
Tito,
I knocked up a quick test with python and apsw and it worked as intended. My
data isn't exactly the same as yours in that I don't have the variety in the
keys, but you're not having problems with those. My test database contains
your data with/without embedded carriage returns - as
Hello everybody,
On 26/03/2006, at 10:08, John Stanton wrote:
LIKE and GLOB do a row scan, and give you none of the advantages of
an RDBMS. Why not use a flat file and grep and get simplicity and
greater speed?
I'm very well aware that LIKE and GLOB perform a row scan. I do
appreciate
John Stanton wrote:
Tito Ciuro wrote:
On 26/03/2006, at 10:51, MGC wrote:
Your design is fundamentaly wrong.
I don't know what your intended use
is for this data, but I am logging identical fstat file info along
with an
MD5 sums.
Well... if you don't know what is the intended use for
Tito Ciuro wrote:
On 26/03/2006, at 10:51, MGC wrote:
Your design is fundamentaly wrong.
I don't know what your intended use
is for this data, but I am logging identical fstat file info along
with an
MD5 sums.
Well... if you don't know what is the intended use for the data, how
can you
On 26/03/2006, at 10:51, MGC wrote:
Your design is fundamentaly wrong.
I don't know what your intended use
is for this data, but I am logging identical fstat file info along
with an
MD5 sums.
Well... if you don't know what is the intended use for the data, how
can you say that my design
There may be an issue, but.
Your design is fundamentaly wrong.
I don't know what your intended use
is for this data, but I am logging identical fstat file info along with an
MD5 sums.
Each informational element needs
to be stored in an individual column.
Stuffing all those fields into a
"Sylko Zschiedrich" <[EMAIL PROTECTED]> wrote:
>
> I try to create a trigger with following statements
>
> create trigger tU_TabTest
>after Update on TabTest
> FOR EACH ROW
> begin
>SELECT RAISE(FAIL, 'Error')
>WHERE (SELECT 1
Thanks, All. I totally missed the nuance between single and double quotes.
Tom
--
Tom Shaw - Chief Engineer, OITC
<[EMAIL PROTECTED]>, http://www.oitc.com/
US Phone Numbers: 321-984-3714, 321-729-6258(fax),
321-258-2475(cell/voice mail,pager)
Text Paging:
Tom Shaw wrote:
Using PHP 5 and SQLite 2.8.14 (This also occurs when commanding SQLite
directly)
I create a table:
CREATE TABLE dnsbl (ip INTEGER PRIMARY KEY, flags VARCHAR(8), ctime
INTEGER, mtime INTEGER, cnt INTEGER, ptr TEXT, refcon INTEGER);
Then I insert a record:
INSERT INTO dnsbl
On Sun, Jul 03, 2005 at 02:59:19PM -0400, Tom Shaw wrote:
> Using PHP 5 and SQLite 2.8.14 (This also occurs when commanding
> SQLite directly)
>
> I create a table:
>
> CREATE TABLE dnsbl (ip INTEGER PRIMARY KEY, flags VARCHAR(8), ctime
> INTEGER, mtime INTEGER, cnt INTEGER, ptr TEXT, refcon
On Jul 3, 2005, at 11:59 AM, Tom Shaw wrote:
Now there should be nothing wrong with the above that I can see BUT
if I change the DB variable name from ip to ip_num all works OK
Strings are quoted with single quotes, not double quotes. Double-
quoted strings are interpreted as column
On Wed, 19 Jan 2005 10:57:13 -0800, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> If you were to guarantee that there is only one reader and only one
> writer-- not just one process, but a single thread and only one
> sqlite3_open() against any one file-- accessing the SQLite database,
> then it
On Jan 19, 2005, at 10:43 AM, Will Leshner wrote:
Bug #301 says that, because fcntl isn't supported for remove volumes
on OS X, SQLite can't acquire a lock, which, I think, pretty much
means you can't use SQLite databases that are on AFP or SMB volumes on
OS X. What would happen if I simply made
> there might be a bug in the replace-conflict handler of sqlite-2.8.15...
What you are seeing is the correct behavior; the entire row
is replaced. Perhaps you are confusing insert with update.
Regards
Michael Hunley wrote:
I am getting an assertion in the following code because pTos->flags is
set to 0x26, which translates into MEM_Static | MEM_Str | MEM_Int. The
value on the top of the stack is 1024. pTos->i is correctly 1024. It
is being used in an expression "UPDATE DBPrefs set
Helphand wrote:
At 08:32 PM 12/17/03 -0500, D. Richard Hipp wrote:
Version 2.8.8 of SQLite is now available on the website
http://www.sqlite.org/
Version 2.8.8 fixes a critical bug that can result in
database corruption. The bug was introduced in version
2.8.0. All users of SQLite version
At 08:32 PM 12/17/03 -0500, D. Richard Hipp wrote:
Version 2.8.8 of SQLite is now available on the website
http://www.sqlite.org/
Version 2.8.8 fixes a critical bug that can result in
database corruption. The bug was introduced in version
2.8.0. All users of SQLite version 2.8.0 and later
> CREATE TABLE User ( Name VARCHAR (40),
> UID INTEGER,
> DeviceID VARCHAR (64) DEFAULT 'Unknown',
> PRIMARY KEY (Name, UID, DeviceID) );
> INSERT INTO User (Name,DeviceID) VALUES
201 - 231 of 231 matches
Mail list logo
