http://www.sqlmaestro.com
May do what you want...
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
From: sqlite-users-boun...@sqlite.org
Can you try doing table copies using select with offset and limit?
See where limit crashes the system and then offset past it perhaps?
Just a guess on my part as one possibility.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop
Hmmm...looking at that strace sequencing is there some reason those 24-byte and
1024-byte writes can't be combined? The 1024-byte write is occurring at the
end boundary of the 24-byte.
That would cut the i/o ops in half and might be a noticeable improvement. A
memory copy would be a lot
Run this program (change the diff threshold if you want) on the strace log file.
This will only show the calls that take too long and the time involved.
#include stdio.h
#include stdlib.h
main(int argc, char *argv[])
{
char buf[65535];
double t1=0,t2;
FILE *fp=fopen(argv[1],r);
-users@sqlite.org
Subject: EXT :Re: [sqlite] Tracing latencies
On 12/05/2012 09:03 PM, Black, Michael (IS) wrote:
Hmmm...looking at that strace sequencing is there some reason those 24-byte
and 1024-byte writes can't be combined? The 1024-byte write is occurring at
the end boundary of the 24
Could it be waitiing on the prior transaction though?
Since disk I/O lies it might be syncing the last transaction causing the new
one to wait longer.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
Can you re-run your strace as strace -tt and look at the timings to help
pinpoint it?
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
From:
One of my considerations would be whether or not the fields are 1-to-1 to the
user or are non-related.
In your list for example favorite politician is something non-related to the
user and you might want to implement either as a search function or a pulldown
list or a tabulated page. So
Could this be your problem?
http://mattgadient.com/2011/02/18/mac-os-x-slow-for-10-15-minutes-after-boot-the-fix/
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
on that platform...
-David
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Black, Michael (IS) [michael.bla...@ngc.com]
Sent: Friday, November 30, 2012 9:46 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite
And if you want to improve latency you can use fifo's on Unix or anonymous
pipes on Windows and run a thread to send your data while it's writing since
those methods are synchronous.
man popen (you open write in one thread and open a read in another)
to char array
On Thu, Nov 29, 2012 at 02:05:02PM +, Black, Michael (IS) scratched on the
wall:
And if you want to improve latency you can use fifo's on Unix or
anonymous pipes on Windows and run a thread to send your data
while it's writing since those methods are synchronous.
I would
The Linux kernel used to default to writeback for a while until 2.6.36 where it
then defaulted to ordered.
So you're seeing the ordered behavior now which is the safest mode.
http://forum.linode.com/viewtopic.php?t=7815
How to convert to writeback if that's what you want...it is a more dangerous
Does this make it weirder or what? If you do the replace after the insert you
get the expected result.
But if you do the replace, followed by 2 more inserts you get this:
SQLite version 3.7.14.1 2012-10-04 19:37:12
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite
Hmmm...is this a disk head seeking problem?
You've got several TEXT entries which are either NULL or default to '';
I did a small experiment: on 3.7.13
CREATE TABLE container_stat (
account TEXT,
container TEXT,
created_at TEXT,
[O'Toole, Eamonn] This definitely sounds like it could be an issue. There is
just one container_stat entry confirmed by sqlite3_analyzer output which I'll
post later). So you're saying that the single container_stat table :entry is
potentially being relocated very frequently the closer the
...@sqlite.org] On Behalf Of Black, Michael (IS)
Sent: 09 November 2012 14:26
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Anomalously slow performance on updates to
earlyentries in a DB
[O'Toole, Eamonn] This definitely sounds like it could be an issue.
There is just one
4, 2012 at 5:59 AM, Black, Michael (IS)
michael.bla...@ngc.com wrote:
Hmmm...interesting...I'm using VS 2010 Express 32-bit and I would've assumed
the warnings would match. I also enabled SQLITE_64BIT_STATS to try and force
the first warning but that didn't cause it.
Microsoft (R) 32-bit C/C
...@mail.ru]
Sent: Sunday, November 04, 2012 1:34 AM
To: General Discussion of SQLite Database
Subject: EXT :Re: [sqlite]SUGGESTION: now as alias for strftime('%s','now')
Fri, 2 Nov 2012 14:11:26 + от Black, Michael (IS)
michael.bla...@ngc.com:
CREATE TABLE t(id,time);
INSERT INTO t VALUES(1
succeeded, 0 failed, 0 skipped ==
*Jonas Malaco Filho*
2012/11/3 Black, Michael (IS) michael.bla...@ngc.com
You probably have the warning level turned up high.
Up to level 3 it compiles without warnings. Level 4 starts complaining
loudly.
Michael D. Black
Senior Scientist
You probably have the warning level turned up high.
Up to level 3 it compiles without warnings. Level 4 starts complaining loudly.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
CREATE TABLE t(id,time);
INSERT INTO t VALUES(1,CURRENT_DATE);
INSERT INTO t VALUES(2,CURRENT_TIMESTAMP);
INSERT INTO t VALUES(3,datetime('now'));
INSERT INTO t VALUES(4,date('now'));
SELECT * FROM t;
1|2012-11-02
2|2012-11-02 14:10:15
3|2012-11-02 14:10:15
4|2012-11-02
Perhaps the documentation
Sounds ilke you're using a 64-bit JDK.
Use the 32-bit JDK.
That's what the error is telling you64-bit can't load 32-bit DLL.
As long as all your code is 32-bit it will run on 32-bit.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Here it is with your desire to use system().
The table output you get probably is not going to be formatted the way you like.
You can extend the logic here to put special sequences in the string to then
replace with formatting.
It would really be easier oveall to do this yourself by using the
Hmmm...looks a lot like 32-bit overflow into a 64-bit number.
2^64
18446744073709551616
Your read offset
18446744071873782392
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
You appear to be programming in C so that's what this is...
Here's a complete example where you can control the table formatting yourself.
This is using sqlite3 calls and I made it produce a simple, complete HTML page.
This is, of course, tied to your database due to the specific column names.
If Windows get FART (find and replace text) from here:
http://blog.secaserver.com/2011/07/windows-find-and-replace-text-command-line-utility/
If Unix learn sed:
http://www.thegeekstuff.com/2009/09/unix-sed-tutorial-replace-text-inside-a-file-using-substitute-command/
Then
sqlite3 test.db
create
I assume you have some program doing the sqlite_exec?
Care to show us your code?
I just ran a test doing what you describe with SQLite Database Browser Version
2.0b1 and the following program compiled against 3.7.13;
After the 2nd run of this program there are 2 records in test.db which the
to update the coloum value of table and using update
command with where clause ..here every time sqlite_exec command failing and
rc returns in sqlite3_prepare such as SQLITE_NOTADB
CHEERS
KRITESH
On Oct 24, 2012 2:10 AM, Black, Michael (IS) michael.bla...@ngc.com
wrote:
I assume you have some
Have you tried making your own DLL from each source and comparing them when
they are compiled the same?
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
From:
How's about you store your interpolated value during insert?
You can use a binary mask of say, 16384, to indicate the value is interpolated
in case you need to know that. In the original data you sent only one value
can be interpolated at record 3. You probably want the interpolation to be
Does a view help you out? Are you just trying to make it easier for somebody
to create a query for that answer without typing so much?
create table v(a integer primary key,b,c,d,e,f);
insert into v values(0,NULL,NULL,2,null,9);
insert into v values(1,1,null,3,null,8);
insert into v
I used 3.7.14.1
Compiled thusly with Visual Studio Express 2008
cl /O2 sqlite3.c shell.c
CREATE INDEX idx_namen_name ON Namen(name);
Took 26.6 seconds and one CPU was pegged the whole time.
I'm on a 3Ghz 8-core machine.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced
And using Dan's downloads
3.7.14.1 took 30.4 seconds
3.6.22 took 40.94 (there was a lot of idle time towards the end here...disk I/O
I assume)
Re-did my compilation again...
3.7.14.1 took 26.8
Recompiled under Visual Studio Express 2010 cl /O2 sqlite3.c shell.c
3.7.14.1 took 26.2 seconds
I'm
[sqlite-users-boun...@sqlite.org] on
behalf of Black, Michael (IS) [michael.bla...@ngc.com]
Sent: Thursday, October 18, 2012 10:16 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] EXT :Re: CREATE INDEX is 13 times slower with 3.7.14.1
than with 3.6.22
And using Dan's downloads
Are you maybe using WAL mode?
Do you have any other files alongside your database like *.db-shm or *.db-wal?
If so, you can just cat all the files together and pipe through md5sum or such.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Maybe I'm missing something (wouldn't surprise me) but I can think of O(n)
traversal of the array for doing this. Not in SQL of course but you should be
able to write a user function for it.
Pseudo-code:
lastchar='';
For (char c in array)
if (lastchar = '' || c = lastchar+1)
subsequence using an UDF
Black, Michael (IS) michael.bla...@ngc.com wrote:
Pseudo-code:
lastchar='';
For (char c in array)
if (lastchar = '' || c = lastchar+1)
curseq.push(c);
else
curseq.clear();
curseq..push(c);
end
The longest increasing subsequence doesn't need to be contiguous
Do this work for you?
CREATE TABLE Test(ID,Value,Group_Marker);
INSERT INTO Test VALUES(1,'D',0);
INSERT INTO Test VALUES(2,'X',0);
INSERT INTO Test VALUES(3,'X',0);
INSERT INTO Test VALUES(4,'X',0);
INSERT INTO Test VALUES(5,'A',0);
INSERT INTO Test VALUES(6,'B',0);
SELECT * FROM Test;
CREATE
Ok...how about with triggers then?
This will give a unique number to each sequence as you insert them.
CREATE TABLE Test(ID,Value,Group_Marker);
CREATE TRIGGER insert_trigger1 after insert on Test
WHEN new.id=1
BEGIN
UPDATE Test set Group_Marker=1;
END;
CREATE TRIGGER insert_trigger2 after
And if you don't quote the 2nd select it comes out OK. This is 3.6.13:
sqlite SELECT id FROM TESTVIEW; -- Observe the results here.
id
--
test
sqlite SELECT id FROM TESTVIEW; -- Observe the results here.
id
--
Presumably a simple bug for the powers-to-be to fix.
Michael D. Black
There isn't Somebody sure wasted their time on this article then...
http://www.linux-magazine.com/w3/issue/78/Write_Barriers.pdf
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
Can you check the difference in stack size between the emulator and the real
device?
The emulator could well have a larger default stack size and you're getting
stack overflow on the real device.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions
You haven't provided enough info for anybody to tell what's going on.
What data are you substracting? Can you provide an sql dump of the data that
gets different answers and your code?
You can' even get fractional seconds from those statements as the time format
only supports hr/min/sec
...@gmail.com]
Sent: Sunday, October 07, 2012 8:18 AM
To: General Discussion of SQLite Database
Subject: EXT :Re: [sqlite] Subtract times hh:mm:ss
There are no different answers and I think all the information is in the
first post.
RBS
On Oct 7, 2012 1:21 PM, Black, Michael (IS) michael.bla
previous post confused/misled you. These are execution
times, not values produced by SQL.
RBS
On Sunday, October 7, 2012, Black, Michael (IS) wrote:
You expect the readers on this list to go find your old post and then look
at what you're NOT doing now? You asked how to compute time, we showed
It would seem to me that if GC.Collect fixes the problem than all you've done
is move the problem to someplace else that isn't fatal (at the moment) and
could rear its ugly head at most any time.
The reason your emulator doesn't throw the error would be for the same
reason...different memory
I took a wee bit of a look at your project -- don't have Win 8 so can't debug
it.
And you didn't include the sqlite assembly anyways.
But...if I read your comments correctly it appears that the primary difference
between what works and what doesn't is the size of the SQL string.
So...this
You don't show any code but it sounds like you're using volatile variables.
Are you using SQLITE_STATIC instead of SQLITE_TRANSIENT?
http://www.sqlite.org/c3ref/bind_blob.html
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop
Try the -cmd switch. Probably the easiest solution.
set xxx to do shell script sqlite3 -cmd \.timeout 2\databasePath
\select * from table1 ;\
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
SQLite3 .timeout command in Command-Line Mode
Thank you Michael. I can't find anything in the documentation about the
-cmd switch. Will you point me in the right direction? Also, a 2 second
timeout would be .timeout 2000 , right?
John
On Thu, Sep 27, 2012 at 8:36 AM, Black, Michael (IS) michael.bla
\databasePath
\select * from table1 ;\
or can I simply use ?
set xxx to do shell script sqlite3 -cmd .timeout 2 databasePath
\select * from table1 ;\
Thanks again for revealing the (apparent) -cmd switch secret.
On Thu, Sep 27, 2012 at 9:44 AM, Black, Michael (IS) michael.bla...@ngc.com
, Black, Michael (IS)
michael.bla...@ngc.com wrote:
The command does need to be in quotes if it's more than one word. sqilte3
expects 1 argument for the command.
I'm not familiar with applescript but I assume you have to escape quotes
to make them actually appear in the output.
Michael D
From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Black, Michael (IS) [michael.bla...@ngc.com]
Sent: Thursday, September 27, 2012 9:26 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] EXT :Re: Sending SQLite3 .timeout command
The other thing you should do is check the exit status of sqlite3. if not 0
then an error occurred.
Plus parse the output to see if you get any errors -- in specific handle the
errors you know about and show errors that need a handler. So for BUSY and
LOCKED you may loop for a while retrying
You said you need to keep something like 30 days, right? Why convert at all?
What's wrong with this:
delete from mytable where mytime max(mytime)-30
If you want to round it off to whole days:
delete from mytable where mytime round(max(mytime)-.5)-30
Or is there something else you need to
You may just want to split the amalgamation code...a wee bit easier...see the
split utility in this dicussion.
http://sqlite.1065341.n5.nabble.com/SQLite-Amalgamation-td11315.html
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop
You don't say how much speed difference you see
But a separate connection will have separate caches. So you could just be
seeing a difference in caching behavior.
One connection uses one cache so will be in L1/L2/L3 cache more often than
multiple threads thrashing the cache.
-users-boun...@sqlite.org] on
behalf of Black, Michael (IS) [michael.bla...@ngc.com]
Sent: Thursday, September 20, 2012 8:37 AM
To: General Discussion of SQLite Database
Subject: EXT :Re: [sqlite] Store error messages in thread local memory
You don't say how much speed difference you see
* on this table from 100 concurrent threads where each
thread randomly selected 20,000 table entries.
The results are:
* using a single connection for all threads: 11 seconds
* using one connection per thread: 59,3 seconds
On Thursday, 20. September 2012 at 15:37, Black, Michael (IS) wrote:
You
:37, Black, Michael (IS) wrote:
You don't say how much speed difference you see
But a separate connection will have separate caches. So you could just be
seeing a difference in caching behavior.
One connection uses one cache so will be in L1/L2/L3 cache more often
than
2 things
#1 Create indexes on testTable.deTestRecordId, dataXyTable.deTestRecordid, and
testTable.testName.
#2 Do you really need the LIKE operator? That's going to scan the entire
table every time. If you can change that to = you'll likely run a lot faster
too.
This shouild speed up
You have a bad table structure which is helping to cause your problem.
It's pretty obvious that you don't want one column per year, you want want a
membership table that has member,year, and paid status (or whatever info you're
keeping for year).
The way you have you have to modify your
Or just fix the existing table:
update members set year2007=NULL where year2007='';
update members set year2008=NULL where year2008='';
update members set year2009=NULL where year2009='';
update members set year2010=NULL where year2010='';
update members set year2011=NULL where year2011='';
Clegg [john.cl...@nailsea.net]
Sent: Monday, September 17, 2012 10:05 AM
To: General Discussion of SQLite Database
Subject: EXT :Re: [sqlite] Count(*) help
Yes, that was the problem thanks. Even though sqlitebrowser declared them
as empty with '' !
On 17 September 2012 15:50, Black, Michael
If you use rowid correctly (always incrementing rowid by using AUTOINCREMENT)
you can always query records lastrowid. That's probably easier.
http://www.sqlite.org/autoinc.html
So something like:
startrowid = 0;
lastrowid = select max(rowid) from mytable;
select * from mytable where rowid =
Try using this method...you just need to ensure mystmt is set to NULL to start
with and reset to NULL in finalize().
const int mySQLite3::read_int(int pos)
throw(somexception) {
if (mystmt == NULL) { // Ensure mystmt is set to NULL in constructor
rc = sqlite3_prepare_v2(db,
A quick experiment shows that 3.7.14 rounds off the last 2 digits of a
double-precision.
As of 3.7.14 sqlite3 rounds to 15 significant digits when using the internal
formatting routines.
sqlite3 test.db
SQLite version 3.7.14 2012-09-03 15:42:36
Enter .help for instructions
Enter SQL statements
Slavin [slav...@bigfraud.org]
Sent: Tuesday, September 11, 2012 8:01 AM
To: General Discussion of SQLite Database
Subject: EXT :Re: [sqlite] selecting real values
On 11 Sep 2012, at 1:56pm, Black, Michael (IS) michael.bla...@ngc.com wrote:
A quick experiment shows that 3.7.14 rounds off the last 2
Have you looked at this?
http://timheuer.com/blog/archive/2012/08/07/updated-how-to-using-sqlite-from-windows-store-apps.aspx
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
_
Does this work for you?
SQLite version 3.7.13 2012-06-11 02:05:22
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite create table t(s);
sqlite insert into t values('Logging in user [aa] from
[10.165.69.247]');
sqlite insert into t values('194|2012-09-07|Logging
:
Nice one! Works here.
RBS
On 9/10/12, Black, Michael (IS) michael.bla...@ngc.com wrote:
Does this work for you?
SQLite version 3.7.13 2012-06-11 02:05:22
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite create table t(s);
sqlite insert into t values('Logging
You're example should work if you only prepare the statement once.
So assuming mystmt is set to NULL on your object creation.
if (mystmt == NULL) {
rc = sqlite_prepare_v2.
}
Then reset it to NULL again when you set apstr=finished. After
sqlite3_finalize(mystmt). That way you're next
And, when you have problems, you should always examine your SQL by running the
EXACT same string you generate in your program through the sqlite3 shell. This
will help you to figure out if your SQL is wrong or your C++ is wrong.
For example even just your SELECT portion generates the wrong
Yeah -- I should've been in a better teaching mode
Trying to keep things simple opens up these type of security problemsthough
there are lots of situations where this works just fine and is no problem at
all (e.g. when you don't have user input or it's completely under your own
control
'twould appear so...the shell even knows about a read-only database.
$ sqlite3 test.db
SQLite version 3.7.9 2011-11-01 00:52:41
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite create table test(a,b);
sqlite insert into table values(1,2);
Error: near table: syntax
You need to :
cout this-SQLStatement.c_str() endl;
Then put that SQL into the sqlite3 shell against your database and ensure you
actually get rows back.
You also need to be sure you're looking at the same database. Many times
people have multiple copies and the one the program uses is not
As for sprintf what they didn't tell you is that you don't want to use that due
to security considerations.
If you are getting ANY data from user input they can craft sql injection
attacks which sprintf is very susceptible to.
Binding the values helps to ensure they can't do that.
Michael D.
Tell us what kind of speed you're seeing. And what your insert looks like.
Then tell us what you expect.
Then we can tell you if your expectations are reasonable or if you're already
getting as much speed as one can expect.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
I think the first thing you'll hear is to NOT store the video data in the
database.
Just store a file path. That is much faster and should complete a lot faster
than your expectations.
Is there some specific reason why you want the blob data in your database?
How long does it take you just to
stored )
in SD card .
Total time to parsing and insert the 500 image =42 sec
Time to insert one image in table after parsing = .02 Sec
Time to parsing one images = .04 sec
Cheers
kritesh
On Tue, Aug 28, 2012 at 9:22 PM, Black, Michael (IS) michael.bla...@ngc.com
wrote:
I think the first
the values using sqlite_binding
will effect the performance .. Is performance due to hardware like SD card
speed or Filesystem ?
Cheers
kritesh
On Tue, Aug 28, 2012 at 9:55 PM, Black, Michael (IS) michael.bla...@ngc.com
wrote:
So you're already doing the smart thinggoodand I believe you
PM, Black, Michael (IS)
michael.bla...@ngc.com
wrote:
I think the first thing you'll hear is to NOT store the video data in the
database.
Just store a file path. That is much faster and should complete a lot
faster than your expectations.
Is there some specific reason why you want
Why should shared cached be serialized when all the threads are reading? I can
see it for writing, but not just for reading. There must be some logic that be
done to allow this I would think (he said without looking at the code).
Michael D. Black
Senior Scientist
Advanced Analytics
I'd vote for the date-range as that can be indexed and result in fast retrieval.
The separate column for accuracy would be a computed range and not indexable.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information
You can use sscanf to determine data type...I've done it before using a method
that's not obvious...
You parse from most restrictive to least restrictive format like this...this
will accept any valid float format including scientific notation.
#include stdio.h
enum {UNKNOWN, FLOAT, INT,
Fully qualified path names may still both load the same shared library.
I assume you have ldd available? Run that on the binaries and see which
library they'll load. Probably the same one unless they are statically linked.
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
You may be interested in this article:
http://www.drdobbs.com/parallel/multithreaded-file-io/220300055?pgno=2
Mutli-threaded reading of multiple files (which is basically what you're
talking about by splitting a file in half) is only faster if you have multiple
disks (in this article that's a
campaign against html e-mail
/\ www.asciiribbon.org
-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
boun...@sqlite.org] On Behalf Of Black, Michael (IS)
Sent: Sunday, 29 July, 2012 06:22
To: General Discussion of SQLite Database
Subject: Re: [sqlite] EXT
You probably have another shared library in your path that is getting loaded
first.
Since you said shared library and not DLL I assume you're using Unix of some
sort?
Run ldd on your GUI app and see what library it says it will use.
Also, you should have either strace or truss which can show
You familiar with the sqlite3 shell?
sqlite-shell here:
http://www.sqlite.org/sqlite-shell-linux-x86-3071300.zip
sqlite3 filename
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
Or since in C++ use an unordered_map. Add your statement pointers to that, and
delete them from the map when finalized. Then walk through that map on
destruction to finalize all you haven't cleaned up yourself.
Given the way he's developing I would make a function to do this that
pre-checks
In keeping with your example what you want to do is add a done flag to your
write class. So you tell it when your SQL can be executed.
Something like this:
void someClass::write2tblName() {
stmtName = INSERT INTO name (n_id, title, fname, mname, lname) VALUES
(?, ?, ?, ?, ?);
int
You're going to get questions like why do you want to do this so you may as
well tell us now.
The usual way to do his is to execute the sql yourself using statement prepares
and step. It gives you a lot more control over error messages. Why don't you
want to do it this way?
The 2nd way
Should be this:
on = true = !0 = 1 (other !=0 values also work typically)
off = false = 0
Michael D. Black
Senior Scientist
Advanced Analytics Directorate
Advanced GEOINT Solutions Operating Unit
Northrop Grumman Information Systems
From:
Hmmmyour data import works just fine in 3.7.9...but you're correct that
3.7.13 burps with that error message doing the same import.
So something changed
C:\sqlitesqlite3 data.db
SQLite version 3.7.9 2011-11-01 00:52:41
Enter .help for instructions
Enter SQL statements terminated with a ;
Nope -- that doesn't work. Seems to me if the import is going to assume the
field is text it should also recognize that if it doesn't start with a quote it
shouldn't assume that all quotes are delimiters.
Plus, it should recognize that any quotes that aren't at the beginning or
end-of-field
Just as a sanity check your code does work OK. I made it a standalone program.
#include iostream
#include sqlite3.h
using namespace std;
class mySQLite3Class {
private:
//SQLite3
sqlite3* db; //SQLite3
string dbName; // Database name
string apstr; // All Purpose String
string
I needed a quick excercise this morning. Never used table_info() before.
table_info() will be faster than doing select * I would think in most all
cases.
#include iostream
#include sstream
#include sstream
#include sqlite3.h
using namespace std;
bool dbExists(string dbName) {
sqlite3 *db;
AND table already exist?
Black, Michael (IS) michael.bla...@ngc.com wrote:
table_info() will be faster than doing select * I would think in most all
cases.
To check the existence of a table, you don't need to actually run the select
statement - just prepare it and check for errors.
--
Igor Tandetnik
1 - 100 of 843 matches
Mail list logo
