> I wonder what the reason was to limit the number of table joins to 32.
http://www.sqlite.org/cvstrac/chngview?cn=3622
Finding fabulous fares is fun.
Let Yahoo! FareChase search your favorite travel sites
t, plus a nicer
looking SQL.
I wonder what the reason was to limit the number of table joins to 32.
RBS
-Original Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED]
Sent: 01 February 2007 00:42
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Limit statement size?
--- RB Smissaert &l
--- RB Smissaert <[EMAIL PROTECTED]> wrote:
> There is one important problem though that I just discovered.
> Just found out that the maximum number of tables in a join is 32!
> So, with my base table that is only 31 to add.
Let's do some grepping...
#define BMS (sizeof(Bitmask)*8)
...
/* T
what I could do is
see how many tables are to be added and pick the method accordingly.
RBS
-Original Message-
From: RB Smissaert [mailto:[EMAIL PROTECTED]
Sent: 31 January 2007 17:54
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Limit statement size?
Actually make that about 5
Actually make that about 5 to 6 times as fast.
RBS
-Original Message-
From: RB Smissaert [mailto:[EMAIL PROTECTED]
Sent: 31 January 2007 17:39
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Limit statement size?
Can confirm now that the method with INSERT OR REPLACE is faster indeed
for the assistance.
RBS
-Original Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED]
Sent: 31 January 2007 00:51
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Limit statement size?
--- RB Smissaert <[EMAIL PROTECTED]> wrote:
> I can see now what the trouble is if I do t
e Wilson [mailto:[EMAIL PROTECTED]
Sent: 31 January 2007 03:49
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Limit statement size?
Your INSERT OR REPLACE statement is in error.
You have fewer columns in your SELECT clause than are specified
in your INSERT column name list. You should have seen
Your INSERT OR REPLACE statement is in error.
You have fewer columns in your SELECT clause than are specified
in your INSERT column name list. You should have seen an error like
this in SQLite version 3.3.12:
SQL error: X values for Y columns
Assuming PATIENT_ID is the sole unique key for A3
; id e2_ae2_be3_a e3_b
> 3 30 31 23 230
> 4 40 41 24 240
> 5 50 51 25 250
>
> id e2_ae2_be3_ae3_b
> 3 300 310 23.1230.1
> 4 400 410 24.1240.1
&g
23.1230.1
4 400 410 24.1240.1
5 500 510 25.1250.1
>
> RBS
>
> -Original Message-
> From: Gerry Snyder [mailto:[EMAIL PROTECTED]
> Sent: 29 January 2007 23:52
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Limit statement
410 24.1240.1
5 500 510 25.1250.1
>
> RBS
>
> -Original Message-
> From: Gerry Snyder [mailto:[EMAIL PROTECTED]
> Sent: 29 January 2007 23:52
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Limit statement size?
>
> RB Smissaer
Thanks, that is how I understood it to be.
I must be overlooking something simple here.
RBS
-Original Message-
From: Gerry Snyder [mailto:[EMAIL PROTECTED]
Sent: 29 January 2007 23:52
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Limit statement size?
RB Smissaert wrote:
> Had a
RB Smissaert wrote:
Had a go at this, but sofar I haven't been able yet to get it to work.
I get no error, but A3Test115_J remains just at it is.
I couldn't find much information about INSERT OR REPLACE in the SQLite
documentation. What exactly should it do?
It will try to do an INSERT. If the
on [mailto:[EMAIL PROTECTED]
Sent: 28 January 2007 20:37
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Limit statement size?
I forgot to specify the unique key for the table to be updated
in the first attempt at INSERT OR REPLACE.
Please try this...
insert or replace into A3Test115_J(
I forgot to specify the unique key for the table to be updated
in the first attempt at INSERT OR REPLACE.
Please try this...
insert or replace into A3Test115_J(
PATIENT_ID, ---<---
ENTRY_ID_E2,
READ_CODE_E2,
TERM_TEXT_E2,
...
NUMERIC_VALUE_E15
)
select
t1.PATIENT_ID, ---<-
--- Joe Wilson <[EMAIL PROTECTED]> wrote:
> I think this technique might be more compact and efficient than the update:
I think my suggestion may result in duplicate rows.
If the INSERT or REPLACE doesn't work, you might try:
1. BEGIN
2. dump the joined select into a temp table
3. delete the
Thanks, will have a look at that.
It definitely looks better.
RBS
-Original Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED]
Sent: 28 January 2007 20:10
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Limit statement size?
I think this technique might be more compact and
I think this technique might be more compact and efficient than the update:
insert or replace into A3Test115_J(
ENTRY_ID_E2,
READ_CODE_E2,
TERM_TEXT_E2,
...
NUMERIC_VALUE_E15
)
select
g2.ENTRY_ID,
g2.READ_CODE,
g2.TERM_TEXT,
...
g15.NUMERIC_VALUE
from
A3Test115_J t1,
iginal Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED]
Sent: 28 January 2007 19:14
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Limit statement size?
--- Fred Williams <[EMAIL PROTECTED]> wrote:
> Wow! Talk about obfuscated code! I didn't even try to dig deeper than
&g
--- Fred Williams <[EMAIL PROTECTED]> wrote:
> Wow! Talk about obfuscated code! I didn't even try to dig deeper than
> a quick scan, but could this abomination be broken into multiple update
> queries? On the surface it looks like each "group" is unique. If so,
> wouldn't a transaction with mul
bject: Re: [sqlite] Limit statement size?
You have any way to normalize that original source table? It's full of
extents, which is the first sign of badness in a table design and
assured of complicating your life.
Clay
RB Smissaert wrote:
> Yes, I agree it looks messy, but I used to do
k from Igor Tandenik I lumped it all together and run it in one go,
> which is a lot faster.
>
> RBS
>
> -Original Message-
> From: Fred Williams [mailto:[EMAIL PROTECTED]
> Sent: 28 January 2007 18:49
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] Limit
@sqlite.org
Subject: RE: [sqlite] Limit statement size?
Wow! Talk about obfuscated code! I didn't even try to dig deeper than
a quick scan, but could this abomination be broken into multiple update
queries? On the surface it looks like each "group" is unique. If so,
wouldn'
nterested.
RBS
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 28 January 2007 18:20
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Limit statement size?
"RB Smissaert" <[EMAIL PROTECTED]> wrote:
> Is there any limit on the size of the SQL stat
Wow! Talk about obfuscated code! I didn't even try to dig deeper than
a quick scan, but could this abomination be broken into multiple update
queries? On the surface it looks like each "group" is unique. If so,
wouldn't a transaction with multiple update statements be much more
efficient and a
"RB Smissaert" <[EMAIL PROTECTED]> wrote:
> Is there any limit on the size of the SQL statements in SQLite?
32-bit integers are used to count things in various places. I
don't really consider that a limit, but some people do.
See http://www.sqlite.org/cvstrac/tktview?tn=2125
There may be other li
26 matches
Mail list logo
