Hi Kervin
> 1. Try these extra gcc flags in your build...
> "-Wall -Wconversion -Wshadow". Also try
> renaming your database handle to something
>more unique.
I renamed my database handle to something more unique but this did not have
any affect. I also tried the extra flags you
Jeffrey Becker wrote:
> All you need to do is pass the string ":memory:" to sqlite3_openxxx
> and it will open a memory-backed database. That said I think your
> first order of business should be to try and define a good abstraction
> around the whole thing. While my C++ is a little rusty heres
All you need to do is pass the string ":memory:" to sqlite3_openxxx
and it will open a memory-backed database. That said I think your
first order of business should be to try and define a good abstraction
around the whole thing. While my C++ is a little rusty heres some C#
pseudo code to get you
Jeffrey Becker wrote:
> As a solution I suggest you come up
> with two slightly different schemas one with change-tracking and one
> without. The disk file will be saved without change-tracking. When
> you load a file, first create a connection to a :memory: database, set
> up your schema with
Darren Landrum wrote:
> D. Richard Hipp wrote:
>
>> Why do you want to load the database into memory? Why not just open
>> it and use it off of disk?
>>
>
> Software synthesis applications, particularly disk-streaming samplers,
> are very high-performance programs, so I'd like to keep
Personally I'd skip the 'auto-saving' feature. Lots of users are used
to being able to mess around with whatever safe in the knowledge that
when they quit their changes will go away. More over, unless
cross-session undo is a stated goal it provides little value while
potentially balooning
D. Richard Hipp wrote:
> Have you actually run experiments to see if this is the case, or are
> you just guessing? My guess would be the combination of the OS disk
> cache and SQLite's internal page cache will make actual disk I/O
> relatively rare, even for an on-disk database.
Okay, I'm
On Aug 18, 2008, at 4:38 PM, Darren Landrum wrote:
> Every touch of a GUI widget will result in a query
> run on the database, so it's best that that be in memory, I think.
Have you actually run experiments to see if this is the case, or are
you just guessing? My guess would be the
Dennis, thank you VERY VERY MUCH. It's exactly what I wanted. I worked on
that for 3 days! I am going to examine your work more carefully to see
exactly what you did (all I did was test it at this point, I didn't read the
query yet).
Thanks again SO MUCH!
--MALON
--
View this message in
MALON wrote:
> I've never posted any questions about SQLite before, so I don't know what
> information I need to give you about it, so I'll just link you to a copy of
> my SQL database: http://www.fileden.com/files/2007/3/10/869420/climb.sq3
>
D. Richard Hipp wrote:
> Why do you want to load the database into memory? Why not just open
> it and use it off of disk?
Software synthesis applications, particularly disk-streaming samplers,
are very high-performance programs, so I'd like to keep disk I/O as
clear as possible. Every touch
On Tue, 19 Aug 2008 01:14:43 +0530, Mrinal wrote:
>pragma table_info(dbname.tablename) syntax is not allowed. Is there
>some other way to get the table_info for tables in attached db which
>bear the same name as another table in either the main, temp or a
>previously attached db?
>F.e.
>I
pragma table_info(dbname.tablename) syntax is not allowed. Is there
some other way to get the table_info for tables in attached db which
bear the same name as another table in either the main, temp or a
previously attached db?
F.e.
I connect to db1.sqlite which contains a table called t1.
Then I
Thomas Sailer wrote:
>
> Interestingly, the original query is extremely compute-bound, there is
> almost no disk activity!
>
> Looking at the output opcodes from the queries, I can't see any
> significant difference. Though I have to admit I'm by far no expert in
> vmdb opcodes...
>
You can
Petite Abeille <[EMAIL PROTECTED]>
wrote:
> Given a set of ids, what would be the proper way to find the records
> containing all those ids?
>
> Specifically, given a 'document_token' table containing a document_id
> mapping to multiple token_id, how would one find the document_id which
> contains
I've never posted any questions about SQLite before, so I don't know what
information I need to give you about it, so I'll just link you to a copy of
my SQL database: http://www.fileden.com/files/2007/3/10/869420/climb.sq3
http://www.fileden.com/files/2007/3/10/869420/climb.sq3
I have taken
Although most of the online documentation for SQLite is OK, I had to
go all the way and buy "The Definitive Guide to SQLite" by Michael
Owens to answer most of my "nuts and bolts" inquiries on the matter.
Most of what you describe seems to be doable without too much hassle.
On Mon, Aug 18, 2008
Hello,
Not specific to sqlite, but a rather generic SQL question...
Given a set of ids, what would be the proper way to find the records
containing all those ids?
Specifically, given a 'document_token' table containing a document_id
mapping to multiple token_id, how would one find the
On Mon, 2008-08-18 at 11:16 -0600, Dennis Cote wrote:
> Does this query run faster?
>
> select * from mapelements
> where ID in
> (
> select ID from mapelements_rtree
> where mapelements_rtree.NELAT>=7900
> and mapelements_rtree.SWLAT<=8000
> and
On Aug 18, 2008, at 2:17 PM, Darren Landrum wrote:
> An object of the class Preset will have the functions to load a
> database into memory
Why do you want to load the database into memory? Why not just open
it and use it off of disk?
D. Richard Hipp
[EMAIL PROTECTED]
I realize that there is a lot written on this subject, and that it's a
popular way of using SQLite, but I'm having trouble finding any
documentation or tutorials that really explain the nuts and bolts. It
doesn't help that I'm still fairly new to C++ programming.
What I want to do is create a
Thomas Sailer wrote:
>
> The following query is very quick, it returns 20 rows within a small fraction
> of a second:
> select * from mapelements_rtree where NELAT>=7900 and SWLAT<=8000 and
> NELON>=7900 and SWLON<=8000;
>
> The following query, however, takes a long time
Hello!
В сообщении от Monday 18 August 2008 20:21:04 Thomas Sailer написал(а):
> The following query is very quick, it returns 20 rows within a small
> fraction of a second: select * from mapelements_rtree where NELAT>=7900
> and SWLAT<=8000 and NELON>=7900 and SWLON<=8000;
>
>
On Mon, 2008-08-18 at 12:28 -0400, D. Richard Hipp wrote:
> Please try changing the last term as shown below (add a "+" before the
> r-tree ID column):
>
> mapelements.ID = +mapelements_rtree.ID
Thanks a lot for your quick answer! Unfortunately, it didn't help.
What's interesting is
On Aug 18, 2008, at 12:32 PM, Brown, Daniel wrote:
> Ah excellent, if I am wanting to build the analyzer from source code
> which C files are required?
>
You need to build on Unix using the canonical source files (not the
pre-processed source files or the amalgamation) and you need to have a
Ah excellent, if I am wanting to build the analyzer from source code
which C files are required?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of D. Richard Hipp
Sent: Friday, August 15, 2008 3:38 PM
To: General Discussion of SQLite Database
Subject: Re:
On Aug 18, 2008, at 12:21 PM, Thomas Sailer wrote:
>
> The following query, however, takes a long time (almost half a
> minute):
> select * from mapelements,mapelements_rtree where
> mapelements_rtree.NELAT>=7900 and
> mapelements_rtree.SWLAT<=8000 and
>
Greetings,
> Lemon does not have any feature that will provide the application with
> access to the follow-set. You could perhaps tease that informatino
> out of the "*.out" output file using a script, though.
Capital idea! That does indeed do the trick. It's straightforward to
extract the
I have a database with the following schema:
CREATE TABLE mapelements (ID INTEGER PRIMARY KEY NOT NULL, TYPECODE
INTEGER,NAME TEXT,LAT INTEGER,LON INTEGER,SWLAT INTEGER,SWLON INTEGER,NELAT
INTEGER,NELON INTEGER,POLY BLOB,TILE INTEGER);
CREATE VIRTUAL TABLE mapelements_rtree USING
On Aug 17, 2008, at 1:48 PM, Markus Thiele wrote:
> Greetings,
>
> I've been using Lemon for a small custom compiler project. I've used
> Bison before, and I very much prefer the way Lemon does things,
> there's
> just one feature I'm missing and haven't been able to find.
>
> Bison generates
>
> 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, context
> FROM poems a JOIN (
> SELECT
> rowid,
>
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, context
> FROM poems a JOIN (
> SELECT
> rowid,
>
> Change cache sizes using separate cache_size
> pragmas for each attached database.
Thank you! (It would be nice if there is a hint for this behaviour in
http://www.sqlite.org/lang_attach.html.)
Is this correct? (At least it does not return an error)
PRAGMA job01.cache_size=200
PRAGMA
Hello Chris,
It looks like you've been dealing with this
for a while now.
1. Try these extra gcc flags in your build...
"-Wall -Wconversion -Wshadow". Also try
renaming your database handle to something
more unique.
2. Have you tried 'strace' like someone else
suggested?
3.
On Aug 18, 2008, at 8:34 AM, [EMAIL PROTECTED] wrote:
> The example with just one main database does not consume more than
> ~300KB
> which seems to be pretty close to the specified 'cache_size'. The
> second example with three attached database consumes
> around 500KB per query and it looks
On Mon, 18 Aug 2008 13:57:16 +0200, Richard wrote:
>Hi,
>
>What is the right time to do a vacuum?
>Is it useful to do it every time you start or stop your application?
Not necessarily. Depends on the dynamics of the application.
>Or can you take a look at the pages that have been used?
That
> Depending on what you are storing in fs_textid and what your LIKE
> pattern is, you might get much better performance (and lower memory
> usage) if you use GLOB instead of LIKE and if you explicitly code the
> pattern rather than using the wildcard "?", and if you create a new
> index:
>
Hi,
What is the right time to do a vacuum?
Is it useful to do it every time you start or stop your application?
Or can you take a look at the pages that have been used? If so how do
you do that exactly?
Thanks,
Richard
___
sqlite-users mailing
I have tried to trace the problem further through the Sqlite source by
checking at which point I could no-longer successfully call the system
function. I got as far as xOpen through sqlite3_open > opendatabase >
sqlite3Btreefactory > sqlite3Btreeopen > sqlite3PagerOpen > Sqlite3OsOpen >
xOpen.
39 matches
Mail list logo
