Hello!
With the attached patch I am able to obtain declared column types from
CAST() expressions.
The diff was made from v3.7.0 amalgamation code; original source file is
select.c, near beginning of function columnType().
Best wishes,
alex.
--- sqlite3.c.orig 2010-07-31 12:17:29.906250
I found the following text:
recommended that applications still make the distinction between between
protected and
At the following location:
http://www.sqlite.org/c3ref/value.html
I believe the first or second "between" should not be there.
Steve
__
Dan Kennedy writes:
> On Aug 25, 2010, at 10:40 PM, Pavel Ivanov wrote:
>
>> Nikolaus,
>>
>> I've traced your application a bit (with SQLite 3.6.18 sources) and
>> it looks like SQLite does some nasty thing nobody in this thread
>> expected. For some reason while doing first delete SQLite actuall
On Fri, Aug 27, 2010 at 18:27, Paweł Hajdan, Jr. wrote:
>
>
>> At start-time, simply call sqlite3_vfs_register() to register your
>> customized VFS with SQLite.
>>
>
> That's what our implementation effectively does, see
> http://trac.webkit.org/browser/trunk/WebCore/platform/sql/chromium/SQLiteFi
Hello,
I'm using sqlite in a speed critical application. Data integrity after
crashes is not very important as the database can be recreated from
scratch in that case.
In my tests, the writing of data with insert commands seemed very slow,
despite being wrapped in a transaction.
I have tried
> And we can't have the entire implementation on the
> WebKit/Chrome side either, because then we can't compile against vanilla
> SQLite (and Linux distributions don't like it).
Could you explain in detail where this "can't" comes from and what's
the problem with Richard's suggestion to copy neces
On Tue, Aug 31, 2010 at 1:19 PM, Paweł Hajdan, Jr.
wrote:
> On Fri, Aug 27, 2010 at 18:27, Paweł Hajdan, Jr. >wrote:
>
> >
> >
> >> At start-time, simply call sqlite3_vfs_register() to register your
> >> customized VFS with SQLite.
> >>
> >
> > That's what our implementation effectively does, see
On Tue, Aug 31, 2010 at 10:51, Richard Hipp wrote:
> My suggestion is that you make a copy of the os_unix.c source file (call it
> chromium_vfs.c or anything else that you like) and apply your edits to that
> copy. Since you started with an exact copy of the original os_unix.c
> source
> file, y
> Is this intended behaviour? How does the pragma/async io module fit in,
> then?
I believe you've got something wrong in your tests. Because with
asynchronous module (if you indeed used its VFS when created your
connections) no actual disk I/O happens in the same thread as insert
command. With PR
On Tue, Aug 31, 2010 at 1:56 PM, Paweł Hajdan, Jr.
wrote:
> On Tue, Aug 31, 2010 at 10:51, Richard Hipp wrote:
>
> > My suggestion is that you make a copy of the os_unix.c source file (call
> it
> > chromium_vfs.c or anything else that you like) and apply your edits to
> that
> > copy. Since you
Scott Frankel wrote:
> Hi all,
>
> How does one find the next value of a serial item? Given a simple
> table with a serial primary key, I'd like to get the next available
> integer key value. eg:
>
> CREATE TABLE foo (
> foo_id SERIAL PRIMARY KEY,
> name
Hi Pavel,
thanks for helping me out!
>> Is this intended behaviour? How does the pragma/async io module fit in,
>> then?
>>
> I believe you've got something wrong in your tests. Because with
> asynchronous module (if you indeed used its VFS when created your
> connections) no actual disk I/
On Aug 30, 2010, at 10:07 PM, Eric Smith wrote:
> Scott Frankel wrote:
>
>> Hi all,
>>
>> How does one find the next value of a serial item? Given a simple
>> table with a serial primary key, I'd like to get the next available
>> integer key value. eg:
>>
>> CREATE TABLE foo (
>> foo_id
On Tue, Aug 31, 2010 at 9:07 AM, Eric Smith wrote:
>
> You probably don't want 'SELECT max(foo_id)+1' because I think that does
> a full table scan.
>
>
you're right, but slightly modified version SELECT (SELECT max(foo_id) FROM
MxVft_FTIndex)+1 does not
Max
_
Pavel,
I have set up a test program without QtSql and could not reproduce any
of the performance degradations. So the problem has nothing to do with
sqlite. Sorry for the noise.
Cheers,
Benjamin
___
sqlite-users mailing list
sqlite-users@sqlite.org
15 matches
Mail list logo