Hello this Testing for cuenta
Gerard
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I understand that the SQLite database resides in memory.
Not usually, no. There's an in-memory cache of recently accessed pages,
but most of the database (especially a large database) remains on disk.
> Now lets say a database is
I understand that the SQLite database resides in memory. I understand that
the information in memory gets written to disk, ie saving parts that have
been updated/whole database.
I have read that SQLite has been known to support up 100,000 concurrent
read connections and can support several
Hello My Name is gerardo Cabero from Argetina..
im Aministrator for Sqlite - Latino [1]
Saludos Gerardo Cabero
[1] = sqlite-latino.blogspot.com
___
sqlite-users mailing list
sqlite-users@sqlite.org
On Wed, Aug 27, 2008 at 03:50:56PM +0100, Hardy, Andrew wrote:
> Is there any way to log conversions to highlite any issues that would
> have been hilighted by failure with strict typing?
If the conversions are nicely isolated into functions (static and
otherwise) could use the DTrace 'pid'
The Sqlite manifest typing integrates nicely with scripting languages
which use similar strategies. Where such integration is not required
and there is a well defined application such as an embedded system,
particularly with a slower processor, a static typing model would be
advantageous in
When I modified Sqlite to block type conversions my memory of it is that
the changes were quite simple and easy to implement. You could log
the change events with a handful of patches to Sqlite. It would be an
interesting exercise to analyze the impact of the conversions.
On an aside I
I made some changes to Sqlite to stop the automatic type conversions.
The performance improvement was not significant. My reason was not to
avoid the performance overhead but to prevent the use of floating point
where it would raise precision problems.
My suggestion would be not to worry
Brown, Daniel wrote:
> Thanks for the clarification Roger, I guess it looks like I will need to
> modify the compiler settings locally then.
If you can modify the amalgamation source code, I would try updating
sqlite3IsNan() to use the standard C isnan() macro. DRH commented in
one of the
On Wed, Aug 27, 2008 at 06:05:46PM +0100, Dave Toll scratched on the wall:
> I'm currently using an 8000 page cache, and as far as I know my DB
> should have been fully-cached before I created the indices (it was built
> from scratch and queried several times).
Ahh... that does change things a
Thanks Jay
I'm currently using an 8000 page cache, and as far as I know my DB
should have been fully-cached before I created the indices (it was built
from scratch and queried several times). Disk usage is pretty much as I
expected. Does creating an index use extra pages on top of the
D. Richard Hipp wrote:>
> I was going to guess the opposite - that manifest typing reduces
> overhead. (But as Dan pointed out - nobody will know until somebody
> generates a version of SQLite that uses static typing and compares the
> performance.)
>
I agree with Dan on this point.
>
On Aug 27, 2008, at 4:52 AM, Alexandre Courbot wrote:
> I know there is a patch at
> http://www.sqlite.org/cvstrac/tktview?tn=3140,38 that is supposed to
> improve Unicode support in FTS3. I suspect it to turn any Unicode
> character into a token - however maybe you can use it as a basis to
>
Hello,
On Aug 26, 2008, at 11:34 PM, Dennis Cote wrote:
> Petite Abeille wrote:
>>
>> Is it possible to use 'if not exists' in conjunction with the
>> creation
>> DDL for a virtual table?
>>
>
> No, its not possible.
>
> The syntax of a "create table" statement is shown here
>
Thanks for the clarification Roger, I guess it looks like I will need to
modify the compiler settings locally then.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Roger Binns
Sent: Tuesday, August 26, 2008 5:00 PM
To: General Discussion of SQLite
On 8/27/08, Dennis Cote <[EMAIL PROTECTED]> wrote:
> P Kishor wrote:
>
> >
> > only badly written Perl, or Perl specifically written to be obfuscated
> > such as in Perl golf, is inscrutable. Well written Perl (I practice as
> > close to literal programming in Perl as possible) is quite pleasant
>
Is there any way to log conversions to highlite any issues that would
have been hilighted by failure with strict typing?
It is my plan to match the column type & data stored type, but clearly
if any conversions are occurring I will be unaware.
Kind Regards
-Original Message-
From:
On Aug 27, 2008, at 10:45 AM, Dennis Cote wrote:
> Hardy, Andrew wrote:
>>
>> Is there a performance hit assosiated with manifest typing?
>>
>
> I'm sure there is since sqlite must track the type of each data item
> as
> well as its value. But in reality this overhead is quite small.
>>
I was
Hardy, Andrew wrote:
> Is there any way to log conversions to highlite any issues that would
> have been hilighted by failure with strict typing?
>
Not that I am aware of.
Dennis Cote
___
sqlite-users mailing list
sqlite-users@sqlite.org
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it
Hardy, Andrew wrote:
>
> Is there a performance hit assosiated with manifest typing?
>
I'm sure there is since sqlite must track the type of each data item as
well as its value. But in reality this overhead is quite small.
> Is it right that although info on the sqlite site suggests there
On Aug 27, 2008, at 4:03 PM, Hardy, Andrew wrote:
> Is there a performance hit assosiated with manifest typing?
Yes. No. Possibly. Difficult to tell unless somebody creates
and optimizes a version of sqlite that does not do manifest
typing.
> Is it right that although info on the sqlite site
On 8/27/08, Andreas Ntaflos <[EMAIL PROTECTED]> wrote:
> On Wednesday 27 August 2008 16:11:28 P Kishor wrote:
> > See my notes at
> >
> > http://www.punkish.org/?p=Why_File_When_You_Can_Full-Text_Search
> >
> > I should get down to write a new and more detailed version and then
> > putting
lovely discourse, but although I feel bad disagreeing (on a tiny
point) with the otherwise very agreeable Mr. Cote...
On 8/27/08, Dennis Cote <[EMAIL PROTECTED]> wrote:
> Derek Developer wrote:
> > Thanks for the link. Unfortunatly its a little expensive and probably
> > 50% slower than my
On Wednesday 27 August 2008 16:11:28 P Kishor wrote:
> See my notes at
>
> http://www.punkish.org/?p=Why_File_When_You_Can_Full-Text_Search
>
> I should get down to write a new and more detailed version and then
> putting it on the SQLite wiki. FTS documentation is woefully
> dismembered and
Derek Developer wrote:
> Thanks for the link. Unfortunatly its a little expensive and probably
> 50% slower than my implementation.
>
On what basis do you make that claim?
> No offense, but C is a language that a lot of us tolerate and is not
> the panacea that some C developers like to believe
On 8/18/08, Dennis Cote <[EMAIL PROTECTED]> wrote:
> P Kishor wrote:
>
> >
> > I would like to generate Snippets from MATCHes in two columns,
> > however, I get the following error: "unable to use function MATCH in
> > the requested context" with the following query --
> >
> > SELECT poem_id,
On 8/27/08, Andreas Ntaflos <[EMAIL PROTECTED]> wrote:
> Hi list,
>
> this is my first post to this list and the first time I am using SQLite
> (3.6.1
> from source on Debian and Ubuntu) in a program of mine so I obviously don't
> have much experience with it. I am glad for the documentation
On Aug 26, 2008, at 1:13 PM, Dave Toll wrote:
> Hello all
>
>
>
> I'm running some general performance tests on SQLite 3.5.9 (embedded C
> platform), and I noticed that creating an index seems to use a lot
> more
> memory than I expected.
>
>
>
> An index on an integer column (30495 rows) uses
On Tue, Aug 26, 2008 at 06:13:29PM +0100, Dave Toll scratched on the wall:
> I'm running some general performance tests on SQLite 3.5.9 (embedded C
> platform), and I noticed that creating an index seems to use a lot more
> memory than I expected.
Creating an index requires reading and sorting
Hi list,
this is my first post to this list and the first time I am using SQLite (3.6.1
from source on Debian and Ubuntu) in a program of mine so I obviously don't
have much experience with it. I am glad for the documentation (otherwise I
would have missed that FOREIGN KEY constraints are
Is there a performance hit assosiated with manifest typing?
Is it right that although info on the sqlite site suggests there is an
avilable mode that supports strict typring, this is not infact the case?
If there is a performance hit, what are the best ways to minimise this?
And is there any
Alexey Pechnikov wrote:
>
> Is it included to 3.6.1 or 3.6.2 version?
>
No, it is not included in either version. The patch was submitted by the
mozilla group, but it has not been checked in to SQLite.
You can of course apply the patch to your own customized version of SQLite.
HTH
Dennis
Note this has been sent to the SQLITE Users digest, as well as the
comp.lang.tcl newsgroup.
I'm getting a core dump at the end of execution of a script which opens an
SQLite database, and performs a query. The gdb stacktrace is as follows:
#0 0x284099c0 in ?? ()
#1 0x2804f918 in dlopen ()
Hello all
I'm running some general performance tests on SQLite 3.5.9 (embedded C
platform), and I noticed that creating an index seems to use a lot more
memory than I expected.
An index on an integer column (30495 rows) uses 1,011,560 bytes.
DB file size increases by 311,296 bytes.
An
Brown, Daniel wrote:
>Unfortunately our build system is automated and not particularly agile, it can
>be done but it would be preferred not to have to do that and to replace the
>offending function instead but I've never had to write a IsNaN test.
>
>
>
I had a look at the sourcecode for
Does anyone know what the course of action is for recovering from a table
locked error?
I dropped a table and I got the error code 6 (Table Locked Error). After two
weeks of pulling my hair I guessed that the error was not for my table being
dropped. It was for the sqlite_master table being
Hello!
В сообщении от Wednesday 27 August 2008 06:52:09 Alexandre Courbot написал(а):
> I know there is a patch at
> http://www.sqlite.org/cvstrac/tktview?tn=3140,38 that is supposed to
> improve Unicode support in FTS3. I suspect it to turn any Unicode
> character into a token - however maybe
Is there a performance hit assosiated with manifest typing?
Is it right that although info on the sqlite site suggests there is an
avilable mode that supports strict typring, this is not infact the case?
If there is a performance hit, what are the best ways to minimise this?
And is there any
40 matches
Mail list logo