Dear Stephen,
Thanks for the reply. As you said we checked the EXPLAIN QUERY PLAN with our
query and it has shown that all the four tables we use in the query are
using their indexes and there is no ORDER BY class in our query. So
sqlite3_prepare compiles the query and sqlite3_step executes the
"Doug" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Thank you Igor. The GROUP BY was the secret (I was trying to do a
> GROUP BY on the outer select, but it wasn't quite cutting it).
>
> GROUP BY is very powerful, but I notice it has a performance cost.
> Is there a way to use an
Thank you Igor. The GROUP BY was the secret (I was trying to do a GROUP BY
on the outer select, but it wasn't quite cutting it).
GROUP BY is very powerful, but I notice it has a performance cost. Is there
a way to use an index with it? I have EventTime indexed and that index is
being used. I
>
>
> >
> > BTW, those PRAGMAs made little difference. I resorted to caching the
> remote
> > file to the local drive via a fast OS-level file copy then doing the SQL
> > R/W, then copying back to the remote in a bkgnd thread. A programming
> > headache to keep everything in sync, but very
I think I have found a solution
After the commit I have set up a loop with a 1 sec sleep that checks for the
existence of the file "ATTACHedDatabase-journal"
Once it no longer exists the script continues, DETACHing the database
without error.
I would have thought there would be a similar SQL
>
> The normal proper way to do what you said is to declare a table like this:
>
> CREATE TABLE person (
> person_id INT PRIMARY KEY,
> name TEXT,
> birthdate DATE
> )
>
> In my example, you are using only the normal data, which is the 3 columns
> specified, and you are not
Stephen Oberholtzer wrote:
> On Tue, May 27, 2008 at 3:59 PM, Richard Klein <[EMAIL PROTECTED]>
> wrote:
>
>>> On May 26, 2008, at 3:24 PM, A. H. Ongun wrote:
Now, when I change the compiler to ppc_82xx-g++ from ppc_82xx-gcc I
get hundreds of error messages.
I am puzzled to
Federico Granata wrote:
>> Your example doesn't counter my suggestion at all, which is to use the data
>> only and not a special rowid. So you put 2 identical rows in a table.
>> Since rows in a table are unordered, there isn't even an ordinal position
>> to distinguish the 2 occurrences of that
Stephen Oberholtzer
<[EMAIL PROTECTED]> wrote:
> On Tue, May 27, 2008 at 4:15 PM,
> [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> One of the fields takes few values (say, company website id), but new
> ids
>> are
>> added from time to time. I would prefer to dynamically create a set
>> of
>
> > > For windows the easiest thing to do would be setting up the ram disk
> and
> > > store database there.
> >
> > easier than using :memory: ???
>
> Not easier, but sometimes more useful. Using a RAM disk means going
> through the OSes file manager, which adds some overhead. On the
>
On Tue, May 27, 2008 at 3:59 PM, Richard Klein <[EMAIL PROTECTED]>
wrote:
> > On May 26, 2008, at 3:24 PM, A. H. Ongun wrote:
> >> Now, when I change the compiler to ppc_82xx-g++ from ppc_82xx-gcc I
> >> get hundreds of error messages.
> >>
> >> I am puzzled to see why this is so.
> >
> > My
On Tue, May 27, 2008 at 05:15:27PM -0300, [EMAIL PROTECTED] scratched on the
wall:
> I need to handle tables with several million records, on realtime, from RAM.
> for the improved locality of reference plus reduced
Do you mean a :memory: database? RAM doesn't really have locality of
>
> Your example doesn't counter my suggestion at all, which is to use the data
> only and not a special rowid. So you put 2 identical rows in a table.
> Since rows in a table are unordered, there isn't even an ordinal position
> to distinguish the 2 occurrences of that same row. Since they are
On Tue, May 27, 2008 at 4:15 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
> >De: [EMAIL PROTECTED]
> >Fecha: 27/05/2008 19:56
> >
> >It's not supposed to, according to
> >http://sqlite.org/lang_createtrigger.html . The syntax
> >only allows select, insert, update and delete statements.
> >
On Tue, May 27, 2008 at 10:41:18PM +0200, Federico Granata scratched on the
wall:
> >
> > For windows the easiest thing to do would be setting up the ram disk and
> > store database there.
>
> easier than using :memory: ???
Not easier, but sometimes more useful. Using a RAM disk means going
[EMAIL PROTECTED] wrote:
>> De: [EMAIL PROTECTED]
>> Fecha: 27/05/2008 19:56
>>
>> It's not supposed to, according to
>> http://sqlite.org/lang_createtrigger.html . The syntax
>> only allows select, insert, update and delete statements.
>>
>> What are you trying to achieve?
>
> I need to handle
>
> For windows the easiest thing to do would be setting up the ram disk and
> store database there.
easier than using :memory: ???
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>De: [EMAIL PROTECTED]
>Fecha: 27/05/2008 19:56
>
>It's not supposed to, according to
>http://sqlite.org/lang_createtrigger.html . The syntax
>only allows select, insert, update and delete statements.
>
>What are you trying to achieve?
I need to handle tables with several million records, on
Thanks for the clarification.
The error I am receiving must then be produced by the application rather
than just reporting an SQLite error.
Or
The application is taking control of the commit wait time, allowing my
script to continue.
Or more correct perhaps; the script commands are passed to the
> On May 26, 2008, at 3:24 PM, A. H. Ongun wrote:
>> Now, when I change the compiler to ppc_82xx-g++ from ppc_82xx-gcc I
>> get hundreds of error messages.
>>
>> I am puzzled to see why this is so.
>
> My guess would be because SQLite is written in C, not C++.
>
> D. Richard Hipp
> [EMAIL
[EMAIL PROTECTED] wrote:
> Does not work:
>
> CREATE TABLE ttt ( t INTEGER PRIMARY KEY );
>
> CREATE TRIGGER ttt_new_trigger AFTER INSERT ON ttt FOR EACH ROW
> BEGIN
>CREATE TABLE uuu ( u INTEGER PRIMARY KEY );
> END;
It's not supposed to, according to
Does not work:
CREATE TABLE ttt ( t INTEGER PRIMARY KEY );
CREATE TRIGGER ttt_new_trigger AFTER INSERT ON ttt FOR EACH ROW
BEGIN
CREATE TABLE uuu ( u INTEGER PRIMARY KEY );
END;
SQL error: near "CREATE": syntax error
If I try the CREATE TABLE outside the trigger, it succeds.
If I replace
On Wed, 28 May 2008 13:44:51 +1930, you wrote:
>My data Base will run on Linux, Is it possible that?
It works the same on all platforms.
Igor Tandetnik already pointed out:
If you use ":memory:" as a file name in the sqlite3_open()
call SQLite creates an in-memory database not backed by disk
On Tue, May 27, 2008 at 2:41 PM, Petite Abeille <[EMAIL PROTECTED]>
wrote:
> Hello,
>
> % sqlite3 -version
> 3.5.9
>
> I'm trying to figure out a frugal way to handle a unique key
> constrain...
>
> I tried using both 'insert or ignore' and a self join. The self join
> seems to be noticeably
Hello,
% sqlite3 -version
3.5.9
I'm trying to figure out a frugal way to handle a unique key
constrain...
I tried using both 'insert or ignore' and a self join. The self join
seems to be noticeably faster even though 'insert or ignore' would
empirically appear to be the better deal
My data Base will run on Linux, Is it possible that?
--
Ing. Hildemaro Carrasquel
Ingeniero de Proyectos
Cel.: 04164388917/04121832139
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Doug <[EMAIL PROTECTED]> wrote:
> SELECT ProcessID, count(1), sum(BytesProcessed)
> FROM FinishedWork
> WHERE EventTime > {20 minutes ago}
> GROUP BY ProcessID, FileName
>
> Unfortunately when a file is processed twice, it's counted twice (ie
> added into the sum twice) and I need to show only
On May 27, 2008, at 12:50 PM, Nicolas Williams wrote:
> On Mon, May 26, 2008 at 11:20:27AM -0400, D. Richard Hipp wrote:
>> SQLite already allows three different names for the rowid: "rowid",
>> "oid", "_rowid_". If all three names are taken, for example if the
>> user has a table like this:
Hi,
Hildemaro Carrasquel wrote:
> How do i do for running on RAM?
Unless I misunderstand your question, you've already asked:
http://sqlite.org:8080/cgi-bin/mailman/private/sqlite-users/2008-May/003023.html
Weren't the answers useful?
--
Dimitri
___
29 matches
Mail list logo
