I'm planning to use SQLite in an application that has a lot of rows (1M+)
with a moderate number of columns (about 50) with the data being somewhat
sparsely populated - ie each row may only have data in a primary column and
5 other columns. Will I get a performance hit - in terms of the size of
This code example below should help you a little, it shows how we
install our own custom order by type. Hope this helps, feel free to ask
more questions here and I'll help if I can.
void QtopiaSqlPrivate::installSorting( QSqlDatabase &db)
{
int sqliteLocaleAwareCompare(void *, int ll, cons
On 6/29/07, Kees Nuyt <[EMAIL PROTECTED]> wrote:
On Wed, 27 Jun 2007 20:42:18 -0400, you wrote:
>1) Faster to do the timestamp in the sql statement, since it does not
>require activation of the trigger.
>2) Query looks 'cleaner', not having an explicit datetime() inside
>3) Can switch the timesta
On Wed, 27 Jun 2007 20:42:18 -0400, you wrote:
>Hello all:
>I was reading through a couple of sqlite tutorials and I noticed
>examples of timestamping database entries by using triggers. I wanted
>to ask people's opinion about using triggers to timestamp records in a
>database.
>
>Which is 'b
Thanks Andrew and everyone.
I'll see what I can get with it.
Thanks for your attention,
Bruno
On 6/28/07, Andrew Finkenstadt <[EMAIL PROTECTED]> wrote:
On 6/28/07, Bruno S. Oliveira <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> Now I see the what's happening.
> But what if I need to create a tab
On 6/28/07, Bruno S. Oliveira <[EMAIL PROTECTED]> wrote:
Hi all,
Now I see the what's happening.
But what if I need to create a table with two primary keys and one
auto incremented (and I DO need that!)? Isn't this possible?
If by primary key you mean alternate (unique) key, then yes.
crea
After reading some more it seems language and country tags alone
aren't enough. Inside the same country, the same language and even the
same culture, different orderings can be used depending on the
ordering objective. As an example, there can be a specific order used
in phone lists and other for
On 6/28/07, Trevor Talbot <[EMAIL PROTECTED]> wrote:
On 6/28/07, Stephane Bortzmeyer <[EMAIL PROTECTED]> wrote:
> > RFCs 4646 and 4647 cover this convention.
>
> No, "language tags" (specified in RFC 4646) use the dash as a
> separator, unlike the POSIX locales. So, it is pt-BR.
Whoops, good cat
Hi all,
Now I see the what's happening.
But what if I need to create a table with two primary keys and one
auto incremented (and I DO need that!)? Isn't this possible?
Thanks a lot Trevor and all. Thanks for the attention.
Best regards,
Bruno
On 6/28/07, Trevor Talbot <[EMAIL PROTECTED]> wrot
Hi all
Is the combination of SQLite and Java/Tomcat is good for an hosting
application ?
My project is http://www.ysalaya.org.
It is a chatbot hosting site.
All the chatbot have their own SQLite database for their knowledge.
That's mean when several users (visitor and botmaster) access
at the sa
To add the guarantee that automatically generated values will never be
reused, your only option is:
create table foo(id integer primary key autoincrement);
Got involved testing this and forgot what I originally went to look
for. You can add "not null" on the end of that, if you want. It's
Bruno S. Oliveira
<[EMAIL PROTECTED]> wrote:
The problem is that, with a table created like this:
sqlite> CREATE TABLE t1 (a INTEGER AUTO INCREMENT NOT NULL, b TEXT,
PRIMARY KEY (a));
Make it
CREATE TABLE t1 (a INTEGER PRIMARY KEY AUTOINCREMENT, b TEXT);
The autoincrement column must be spel
On 6/28/07, Bruno S. Oliveira <[EMAIL PROTECTED]> wrote:
CREATE TABLE te_representation (repres_id INTEGER AUTO_INCREMENT
NOT NULL ,layer_id INTEGER ,geom_type INTEGER ,geom_table TEXT
,description TEXT ,lower_x REAL ,lower_y REAL ,upper_x REAL
,upper_y REAL ,res_x REAL ,res_y REAL ,
Hi,
On 6/28/07, Trevor Talbot <[EMAIL PROTECTED]> wrote:
"integer primary key" is special, and the only column "autoincrement"
can be applied to. It's not a general-purpose sequence option, like
some other database engines.
Yep, I knew that.
The problem is that, with a table created like th
On 6/28/07, Bruno S. Oliveira <[EMAIL PROTECTED]> wrote:
Does the sqlite auto_increment work only with primary keys WITHOUT the
not null constraint? The same query on the same table worked on MySQL.
"integer primary key" is special, and the only column "autoincrement"
can be applied to. It's
Hi Griggs and everyone,
Nop, the problem isn't the underscore. The sqlite works with both
keywords: AUTOINCREMENT and AUTO_INCREMENT.
Thanks for the attention!
Regards,
Bruno
On 6/28/07, Griggs, Donald <[EMAIL PROTECTED]> wrote:
Regarding: "I'm aware of the create table syntax. And accordin
On 6/28/07, Stephane Bortzmeyer <[EMAIL PROTECTED]> wrote:
On Thu, Jun 28, 2007 at 08:45:23AM -0700,
Trevor Talbot <[EMAIL PROTECTED]> wrote
a message of 16 lines which said:
> >It seems more natural to use the standard C locale names to me (the
> >usual "pt_PT" and "pt_BR" for Portuguese/Port
Regarding: "I'm aware of the create table syntax. And according to it I
can declare a column as INTEGER AUTO_INCREMENT NOT NULL. So I wonder
why this doesn't work (in MySQL it does!)."
To underscore -- the difficulty:
Maybe it was just a typing mistake in your message, but according to
http
Hi Eugene and all,
On 6/28/07, Eugene Wee <[EMAIL PROTECTED]> wrote:
Why not declare repres_id as INTEGER PRIMARY KEY? You can refer to the
documentation on CREATE TABLE:
Well, I am declaring it as INTEGER PRIMARY KEY. Or do you mean without
the NOT NULL and AUTO_INCREMENT?
I'm aware of the c
On Thu, Jun 28, 2007 at 08:45:23AM -0700,
Trevor Talbot <[EMAIL PROTECTED]> wrote
a message of 16 lines which said:
> >It seems more natural to use the standard C locale names to me (the
> >usual "pt_PT" and "pt_BR" for Portuguese/Portugal culture and
> >Portuguese/Brazil culture) , but I'm ope
Hi Bruno,
Why not declare repres_id as INTEGER PRIMARY KEY? You can refer to the
documentation on CREATE TABLE:
http://www.sqlite.org/lang_createtable.html
Regards,
Eugene Wee
Bruno S. Oliveira wrote:
Hi all,
I'm having some trouble in inserting data into a table which its
primary key is se
Hi all,
I'm having some trouble in inserting data into a table which its
primary key is set as auto_increment and not null.
The table was created as follows:
CREATE TABLE te_representation (repres_id INTEGER AUTO_INCREMENT
NOT NULL ,layer_id INTEGER ,geom_type INTEGER ,geom_table TEXT
,desc
Hi,
We are trying to figure out how to use Qt Sqlite driver to use loadable
extension mechanism. We have a shared library, which needs to be loaded
after db is open. We are using Qt classes to make a connection to database,
so our code looks like this:
QSqlDatabase db= QSqlDatabase::addDatabas
On 6/28/07, Nuno Lucas <[EMAIL PROTECTED]> wrote:
It seems more natural to use the standard C locale names to me (the
usual "pt_PT" and "pt_BR" for Portuguese/Portugal culture and
Portuguese/Brazil culture) , but I'm open to suggestions when that
problem arise, and I'm sure there are already st
On 6/28/07, Trevor Talbot <[EMAIL PROTECTED]> wrote:
On 6/28/07, Nuno Lucas <[EMAIL PROTECTED]> wrote:
> One thing I noticed is that "collations" != "case change". This will
> not make it possible to use UPPER/LOWER with the same data on the
> table, but maybe we can work on something in that re
On 6/28/07, Jiri Hajek <[EMAIL PROTECTED]> wrote:
> My idea is to implement the UCA collation in SQLite (with the usual
> OMIT_* #ifdef's), using the DUCET table as base, and if people need
> the tailoring part for localized sorting, have it be optional by
> having a "sqlite_collation_data" table
On 6/28/07, Jiri Hajek <[EMAIL PROTECTED]> wrote:
Btw, even if this is implemented, there is still a need for a
standardization such new collation names. E.g. that new language
neutral collation could be called Unicode or DUCET? And how about
language specific collations? After some thoughts, I'
On 6/28/07, Nuno Lucas <[EMAIL PROTECTED]> wrote:
One thing I noticed is that "collations" != "case change". This will
not make it possible to use UPPER/LOWER with the same data on the
table, but maybe we can work on something in that respect, also.
If the intent is case-insensitive comparison
My idea is to implement the UCA collation in SQLite (with the usual
OMIT_* #ifdef's), using the DUCET table as base, and if people need
the tailoring part for localized sorting, have it be optional by
having a "sqlite_collation_data" table with the needed locale data
included on the database.
Th
I see that change 3948 implemented the max_page_count pragma, which is very,
very useful in my environment. I was surprised by the fact that its value
is per-connection and not per-database, as I had assumed that the maximum
file size was an attribute of the file and not of the running instance.
This is a typical symptom of timing issue which can be due to threading.
If u have purify try it.U can find the error soon.
regards
ragha
**
This email and its attachments contain confidential information fro
Just a follow-up for the group...
Richard was able to determine that my platform is having trouble with an
fstat() call to get the size of files on my file system. Specifically, the
call is returning a size of 0 when it should be 11K. I am investigating the
vxWorks platform and have found that f
On 6/27/07, Jiri Hajek <[EMAIL PROTECTED]> wrote:
> Trevor proposed method doesn't need that, because the collation data
> goes with the database (which is the big advantage to me). And if you
> want to use another collation, you only need to import the collation
> data needed for that locale.
You could achieve this with a trigger + custom function.
MSSQL 2005 now has this ability (though no SQL syntax applies, it's built
into the ADO.NET 2.0 provider) and it's a really nice feature.
HTH
Sam
---
We're Hiring! Seeking a passionate developer t
B V, Phanisekhar <[EMAIL PROTECTED]> wrote:
select * from tableName order by someField DESC
limit ROUND( (select count(*) from tableName) / 10);
"limit_opt ::=",
"limit_opt ::= LIMIT expr",
"limit_opt ::= LIMIT expr OFFSET expr",
"limit_opt ::= LIMIT expr COMMA expr",
Which one of the above fo
Joe Wilson wrote:
page_size must be the first statement.
PRAGMA page_size=4096;
PRAGMA default_cache_size=25;
Thanks Joein hindsight, that's something I should have checked, but
it never crossed my mind.
And thanks Andy for explaining the physical effect of default_cache_size
in a
36 matches
Mail list logo
