Hi guys,
I'm trying to use sqlite as the database for punbb. I've created the
database, and changed it's user and permissions (even to 777 for
testing purposes). Still, punbb can not write to it. Have any idea
what could be wrong?
thanks
Hi everybody,
I'm trying to compile SQLite for the PowerPC 8xx architecture using
Power PC cross compiler, i.e ppc_8xx-gcc, on a Pentium 4 machine running
ELDK. Considering ppc_8xx-gcc is in my PATH,
I've created a Makefile by ./configure command and edited it so as to
make all the gcc's in the
On Tue, 12 Apr 2005, Maksim Yevmenkin wrote:
Dear SQLite users,
consider this
[snip]
it only took 4+ seconds to read, parse, perform hash table lookup and
sum the data. note that for unique 1417 keys it had to do hash lookup
and hash insert.
so, just with plain ascii file i get four times
On Fri, 2005-04-08 at 11:53 -0700, Maksim Yevmenkin wrote:
CREATE INDEX data_by_a ON data (a);
time sqlite3 db 'select n2 from data where a = 18234721' /dev/null
25.95u 0.71s 0:27.02 98.6%
If you make the index look like this:
CREATE INDEX data_by_a ON data(a, n2);
Then SQLite only
well, it could be true, but not in the queries i have posted. i group
by column a and there is an index on column a, so sqlite does not
have to do anything to compute key. it does not even have to back to
Do not confuse the index key with the aggregator key. The two may be
the same in
I am running into a situation that does not make sense.
I have allocated a flat file under the Operating System as follows (notice
that autocommit is off):
$dbh = DBI-connect('dbi:SQLite:' . $dbms_file , , ,
{ RaiseError = 1,AutoCommit = 0 });
Then, I create
Follow up:
If I create multiple $dbh as in $dbh{$tables}, and point each to a
different Operating System (O.S.) flat file, then I am OK.
LOOP-for-tables:
$dbh{$tables} = DBI-connect('dbi:SQLite:' . $dbms_file . $table , ,
,
{ RaiseError = 1,AutoCommit = 0 });
It is
[EMAIL PROTECTED] wrote:
I am running into a situation that does not make sense.
I have allocated a flat file under the Operating System as follows (notice
that autocommit is off):
$dbh = DBI-connect('dbi:SQLite:' . $dbms_file , , ,
{ RaiseError = 1,AutoCommit = 0 });
On Wed, 2005-04-13 at 17:59 -0500, Eric Bohlman wrote:
[EMAIL PROTECTED] wrote:
I am running into a situation that does not make sense.
I have allocated a flat file under the Operating System as follows (notice
that autocommit is off):
$dbh = DBI-connect('dbi:SQLite:' . $dbms_file , ,
I have been experimenting with SQLITE for a little over a week now, and
I must say that I am fairly impressed with many of its capabilities. I
have been experimenting with performance from several aspects, and the
numbers are quite respectable. I have several years experience with
Sybase,
D. Richard Hipp wrote:
Not only CREATE statements, but also DROP and VACUUM statements
will also invalidate all previously prepared statements. Once a
prepared statement is invalidated, it must be prepared again.
And also ALTER TABLE.
Just wondering, is there any mechanism to help me achieve that
functionality or should I go the DROP, CREATE, SELECT and INSERT path?
Thanks,
Dennis
-Original Message-
From: Dennis Volodomanov
Sent: Wednesday, April 13, 2005 10:14 AM
To: sqlite-users@sqlite.org
Subject: [sqlite]
There's always CREATE TABLE ... AS ..., but not everybody is happy
with the column names and types it creates.
--- Dennis Volodomanov [EMAIL PROTECTED] wrote:
Just wondering, is there any mechanism to help me achieve that
functionality or should I go the DROP, CREATE, SELECT and INSERT path?
To cross-compile, you need to create the config.h file by hand. The
following excerpt is from main.mk:
# The config.h file will contain a single #define that tells us how
# many bytes are in a pointer. This only works if a pointer is the
# same size on the host as it is on the target. If you
SQLite needs write permission to the directory as well. It could be
that.
--- tom [EMAIL PROTECTED] wrote:
Hi guys,
I'm trying to use sqlite as the database for punbb. I've created the
database, and changed it's user and permissions (even to 777 for
testing purposes). Still, punbb can
I actually haven't seen that before :-(
So, CREATE TABLE AS will basically duplicate the table that I have (if
I say for example, CREATE TABLE AS myNewTable AS SELECT * FROM
myOldTable)? Sounds good if that's true :-)
Thanks,
Dennis
-Original Message-
From: Dan Kennedy
16 matches
Mail list logo