Igor Tandetnik wrote:
On 3/21/2012 9:33 PM, Yan Seiner wrote:
I need to write some C code to interface with sqlite API. I"ve been
through the docs, and I'm hoping someone can point me to some very basic
example code that I could build on.
http://www.sqlite.org/quickstart.html
Thanks! Perfec
On 3/21/2012 9:33 PM, Yan Seiner wrote:
I need to write some C code to interface with sqlite API. I"ve been
through the docs, and I'm hoping someone can point me to some very basic
example code that I could build on.
http://www.sqlite.org/quickstart.html
--
Igor Tandetnik
_
I just started playing around with sqlite3 in earnest. I have a fairly
large database (several hundred thousand records) on an embedded box and
sqlite does an incredible job of finding what i need very fast.
My database is as simple as it gets:
CREATE VIRTUAL TABLE latlong USING rtree( id, la
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/03/12 16:57, Udi Karni wrote:
> Frankly I don't know if a 64-bit version and Big RAM would make a
> difference and if so - up to what point.
A 64 bit Windows command shell won't wave a magic wand. In any event you
can compile one yourself and
Frankly I don't know if a 64-bit version and Big RAM would make a
difference and if so - up to what point. With SQLite being a single process
- assigned for the most part to a single CPU - even if everything was done
in RAM - there is a limit to what 1 CPU can do.
I am just noticing anecdotally th
Doh!
Know the feeling. Well!
On Wed, Mar 21, 2012 at 2:38 PM, Simon Slavin wrote:
>
> On 21 Mar 2012, at 7:35pm, Adam DeVita wrote:
>
> > Sorry for false alarm. Please disregard this thread:
> >
> > Solution: make sure you quit everything and isolate the code. There is a
> > subsequent writ
On 21 Mar 2012, at 7:35pm, Adam DeVita wrote:
> Sorry for false alarm. Please disregard this thread:
>
> Solution: make sure you quit everything and isolate the code. There is a
> subsequent write to the new record that made it appear as a problem, when
> it wasn't.
We've all done it. Glad
Sorry for false alarm. Please disregard this thread:
Solution: make sure you quit everything and isolate the code. There is a
subsequent write to the new record that made it appear as a problem, when
it wasn't.
Adam
On Wed, Mar 21, 2012 at 3:25 PM, Adam DeVita wrote:
> Good day,
>
> I'm just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/03/12 11:09, Black, Michael (IS) wrote:
> Cache is the primary (and obvious) thing I can think of.
With a 32 bit compilation you'll be able to bump it up to about 2GB.
However by that point you will long have passed diminishing returns and
can j
Good day,
I'm just exporting data to another db of known same structure, and setting
a flag. It seems that one row shows an incorrect result, but only so in my
c++ code.
I extracted the queries being run using my debugger, and tried them in the
command prompt.
When I run the following batch of q
Cache is the primary (and obvious) thing I can think of.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/03/12 05:28, Udi Karni wrote:
> Is there - or can we kindly request that a 64-bit version of the
> Command Shell be offered on the download page?
>
> A version that could run on Windows 7 64-bit and effectively use large
> RAM?
Which bit of the
Currently the MyJSQLView application uses the Xerial SQLiteJDBC
interface to interact with a SQLite database. Does anyone know
of a more native type of JDBC interface mechanism that Java may
use to access a SQLite database?
The project would really like to be able to create a local file
or memory
Hello,
Is there - or can we kindly request that a 64-bit version of the Command
Shell be offered on the download page?
A version that could run on Windows 7 64-bit and effectively use large RAM?
Thanks !
___
sqlite-users mailing list
sqlite-users@sqlit
On 21 Mar 2012, at 12:23pm, Conxita Marín wrote:
> Any command respond, no error, nothing
>
> conxita@mylinux$: sqlite3 backup.bd
> SQLite version 3.7.3
> Enter ".help" for instructions
> Enter SQL statements terminated with a ";"
> sqlite> .tables
> sqlite>
If you have made a new database wit
Conxita Marín wrote:
> I'm in my new Linux box, Linux Debian Squeeze, I installed the version
> 3.7.3.of sqlite3, that comes in the repositories that I use.
>
> Any command respond, no error, nothing
>
> conxita@mylinux$: sqlite3 backup.bd
> SQLite version 3.7.3
> Enter ".help" for instructions
Hi all,
I'm in my new Linux box, Linux Debian Squeeze, I installed the version
3.7.3.of sqlite3, that comes in the repositories that I use.
Any command respond, no error, nothing
conxita@mylinux$: sqlite3 backup.bd
SQLite version 3.7.3
Enter ".help" for instructions
Enter SQL statements ter
On 21 Mar 2012, at 3:08am, Udi Karni wrote:
> The 240GB SSD drives are pretty reasonably priced and would suffice for
> most tables. I'm just wondering how long before Flash Write Fatigue sets in
> and you need a replacement.
Nobody knows yet. We've done a ton of tests but so far the driv
When I did the index test I did not have the second table in the DB.
Just the complete large table (id, topics, definition). I also didn't have
order by random() limit 1
In the select statment. The data is alread in alphabetical order, but I'll try
that anyway.
I am going to be away from the
At 07:53 21/03/2012, Max Vlasov wrote:
On Wed, Mar 21, 2012 at 1:33 AM, Tim Morton wrote:
> So it seems the index is no help;
>
Are you sure you did as Simon explained?
Becausem my tests shows the trick works... (sqlite 3.7.10)
The trick works, but i think he didn't timed what he should tim
I want to get the virable char myresult[200]= select name where id>20 from
mytable
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
2012/3/21 Alexandr Němec
>
> Dear all,
>
> I've just read the 3.7.11 release notes. This version fixes the LEFT JOIN
> bug with OR in the WHERE clause introduced in 3.7.10. Since our software is
> currently based on 3.7.10 and it is not easy for us to upgrade to 3.7.11, I
> just want to be sure a
Dear all,
I've just read the 3.7.11 release notes. This version fixes the LEFT JOIN bug
with OR in the WHERE clause introduced in 3.7.10. Since our software is
currently based on 3.7.10 and it is not easy for us to upgrade to 3.7.11, I
just want to be sure about the bug impacts.
1. I have d
23 matches
Mail list logo