On Sep 24, 2008, at 1:13 AM, Alex Scotti wrote:
>
> On Sep 23, 2008, at 2:35 PM, Jay A. Kreibich wrote:
>
>
>>
>> It doesn't "blatantly" anything. Indexes are outside of the
>> Relational Model and have nothing to do with it. They're
>> orthogonal.
>> From that, anything having to do
On Tue, Sep 23, 2008 at 02:26:08PM -0500, Nicolas Williams scratched on the
wall:
> On Tue, Sep 23, 2008 at 01:35:44PM -0500, Jay A. Kreibich wrote:
> > IMHO, the jump from "you must manually create indexes" to "you may
> > control the *use* of an index" is a MUCH smaller jump than the very
"Bruno Moreira Guedes"
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I have a query where I want to reuse a subquery result. By example:
>
> SELECT
> CASE WHEN
> (SELECT "value1") != ''
> THEN
> (SELECT "value1")
> ELSE
>
Hello all,
I have a query where I want to reuse a subquery result. By example:
SELECT
CASE WHEN
(SELECT "value1") != ''
THEN
(SELECT "value1")
ELSE
(SELECT "value2")
END;
But I don't want to repeat all the subquery again in the
On Tue, Sep 23, 2008 at 01:35:44PM -0500, Jay A. Kreibich wrote:
> If there was a point I was trying to make, it was that something
> being "un-RDBMS like" in itself doesn't make it a bad thing. After
> all, the very concept of indexes themselves is (from a Relational
> Model theory
On Tue, 23 Sep 2008 14:37:11 -0400,
Enrique Ramirez wrote:
>On Tue, Sep 23, 2008 at 1:16 PM, Kees Nuyt <[EMAIL PROTECTED]> wrote:
>> Steps to take (you need all of them, except 1):
>>
>> 1) Use v6.2.3
>>
>
>Probably meant to say 1) Use v3.6.2?
Oops, yes. Or even better: v3.6.3
--
( Kees
On Mon, Sep 22, 2008 at 10:44:20PM -0400, Alex Scotti scratched on the wall:
>
> On Sep 22, 2008, at 11:18 AM, Jay A. Kreibich wrote:
>
>> On Mon, Sep 22, 2008 at 10:07:54AM -0400, D. Richard Hipp scratched on
>> the wall:
>>> I am reluctant to add to SQLite the ability to explicitly specify the
On Mon, 22 Sep 2008 13:48:42 -0700, Jason wrote:
>Hello everyone,
>
>Hoping that I could get some help with a performance problem.
>Using version 3.5.2
>
>Here are the tables:
>CREATE TABLE Objects (ObjectId INTEGER PRIMARY KEY, Name TEXT)
>CREATE TABLE Keywords4Objects (ObjectId INTEGER,
You have to follow
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users and set
it up in your options.
On Tue, Sep 23, 2008 at 12:39 PM, chris newgent <[EMAIL PROTECTED]> wrote:
> Could I be removed from the regular mailing list please. I am trying to sign
> up for the digest.
>
> Design
Could I be removed from the regular mailing list please. I am trying to sign up
for the digest.
Design simplicity eliminates engineering complexity.
___
sqlite-users mailing list
sqlite-users@sqlite.org
On Tue, Sep 23, 2008 at 11:24:04AM -0400, Timothy A. Sawyer scratched on the
wall:
> I'm trying to find out what the limit is with INTEGER PRIMARY KEY.
http://www.sqlite.org/autoinc.html
> But what is the theoretical limit for the integer,
9223372036854775807 in SQLite version 3.0.0 and
Hi there,
I would like to confirm the transaction flow for three SQL statements (2
INSERT's + 1 UPDATE):
sqlite3_open_v2() - open database
sqlite3_prepare_v2() - prepare a statement
sqlite3_step() - BEGIN TRANSACTION
if an error occured sqlite3_finalize()
sqlite3_reset() - reset
Hi there,
I would just like to confirm that this is the processing flow for a transaction
made of two SQL statements (INSERT + UPDATE):
sqlite3_open_v2() - open database
sqlite3_prepare_v2() - prepare statement
sqlite3_step() - BEGIN TRANSACTION using above prepared statement
sqlite3_reset()
On Sep 23, 2008, at 10:31 AM, Dennis Cote wrote:
> Shane Harrelson wrote:
>> This was my fault. http://www.sqlite.org/cvstrac/chngview?cn=5654
>> strcasecmp() isn't available on all platforms, and I naively assumed
>> sqlite3StrICmp() would be (it's not in this case do to the way you
>> are
Did you take a moment to read the documentation on the subject?
http://www.sqlite.org/faq.html#q5
On Mon, Sep 22, 2008 at 9:37 PM, Dave Dyer <[EMAIL PROTECTED]> wrote:
>
> In modern working environments, network shares are not an abnormality.
>
> Sqlite Network shares work by default for pcs.
>
He probably comes from the world of posgresql, where an
'autoincrement' variable is called a serial.
On Mon, Sep 22, 2008 at 1:06 PM, Seun Osewa <[EMAIL PROTECTED]> wrote:
> INTEGER PRIMARY KEY AUTOINCREMENT
>
> 2008/9/22 Victor Hugo Oliveira <[EMAIL PROTECTED]>
>
>> hi everybody,
>>
>> SQLite 3
Shane Harrelson wrote:
> This was my fault. http://www.sqlite.org/cvstrac/chngview?cn=5654
> strcasecmp() isn't available on all platforms, and I naively assumed
> sqlite3StrICmp() would be (it's not in this case do to the way you
> are compiling/linking). I'll review the issue and see what I
P Kishor wrote:
>
> Still, you have a point, and maybe DRH will expound and enlighten us
> on his reticence to enable locking style equal to one.
>
It seems he isn't so reticent after all. See checkin [5737] from this
morning at http://www.sqlite.org/cvstrac/chngview?cn=5737.
Dennis Cote
Hello Guys.
I have a problem with running SQLite.
I am running linux 2.6.5 on ARM and basicaly problem si that my application
is crushing on sqlite3_open() function while the sqlite3 command shell is
running without problems.. I have tried to copy all defines but probably
that is not enough to
On Sep 23, 2008, at 12:06 AM, Robert Simpson wrote:
>>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Gavin Kistner
>> Sent: Monday, September 22, 2008 9:45 PM
>> To: General Discussion of SQLite Database
>> Subject: [sqlite] Crazy performance
hi all,
> В сообщении от Thursday 31 July 2008 12:10:54 Petr Vanek
написал(а):
> > > I gave it a try, and it seems as if SQLiteman can´t handle extensions
> > > for databases, is this right?
> >
> > not yet unfortunately. But it's requested already.
it's done in current SVN. Sqliteman can handle
Hi,
I just ran the full test suite (all.test) in our Mac OS X build and
got a few failures, but I'm not quite sure what to make of them and
whether they're critical failures - they don't seem to be part of the
quick tests suite, so I figure they might be less important?
Anyway, here's the
On Sep 23, 2008, at 12:06 AM, Robert Simpson wrote:
>>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Gavin Kistner
>> Sent: Monday, September 22, 2008 9:45 PM
>> To: General Discussion of SQLite Database
>> Subject: [sqlite] Crazy performance
On Sep 22, 2008, at 11:03 PM, P Kishor wrote:
> I am assuming you have good reason to not just ATTACH the old db to
> the new db and INSERT INTO new_table SELECT * FROM old_db.old_table
Partially ignorance about that, and partially because I want to use
the ORMs involved with the DB to ensure
Looks to me like you've forgotten the biggest performance factor of all ...
starting a transaction before you begin the loop and committing it
afterwards.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gavin Kistner
Sent: Monday, September 22, 2008 9:45
25 matches
Mail list logo
