Re: [sqlite] SQLite - how to protect the data

[Ulrich Telle]

Hi Marek,

> Thanks Ulrich, but I think that goes beyond the scope of my knowledge
> and tools I have available to me.
> 
> I wish somebody (who has C++ knowledge) has done it already and
> released version of SQLite with encrypt and decrypt functionality.

Well, there is a prebuilt DLL with encryption support for Windows bundled with 
wxSQLite3.

> You make it sound like it shouldn't be a problem for someone who knows
> C++. But I am expecting a catch somewhere, otherwise why would there be
> commercial versions of SQLite which has this functonality.

The catch is that for non-commercial solutions you don't have a guarantee *how* 
secure your encrypted database will be. The weak point of encryption is how the 
encryption key is generated and whether it's hard to crack or not.

I have no proof how secure my solution is but the encryption key is generated 
in much the same way as it is for Adobe PDF. So I guess what's good enough for 
PDF should be good enough for SQLite. But I won't give you a guarantee.

> If you don't mind one more off topic question. You seem to have
> experience with wxWidgets. In tandem with wxPython is that a better
> tool to use than just Python and Tkinter. Which route is the easier
> one for a beginner in this language?

Although I know wxWidgets quite well I can't give a qualified answer to your 
question since I'm using C++ almost exclusively. But I heard wxPython to be 
very usable.

Regards,

Ulrich

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[Nuno Lucas]

On 2/25/07, mxs <[EMAIL PROTECTED]> wrote:

I realize that, but this is about making it difficult for the average Joe not
to stop professional hackers who I assume can steal anything they want.


Look for SQLITE_FILE_HEADER in the code (it's in the btree.c file). By
redefining it, only your application will be able to open a sqlite
database created by it.

The database will not be encrypted, and you will not be able to open
sqlite databases made by other applications, but will be enough for
the average Joe.

You will have to check every time there is a file format change to not
destroy your databases, though.


Regards,
~Nuno Lucas

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Martin Jenkins]

RB Smissaert wrote:


Due to me not knowing C I hadn't realized that this structure had to be left
intact. 


It's not a C thing as such, it's the way Dr Hipp has designed it. It's 
an interface - the third entry in the list always does the same thing 
but the function that actually runs to do that thing can be changed, 
possibly at runtime. You can disable entries by setting them to 0 (if 
the infrastructure knows about it) but if you swap list entries around 
(or delete them) things will break. That's where the VB DLL instructions 
fell down.


Martin

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] (newbie) pictures in tables, what's the best way ?

[Roger Binns]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Stef Mientki wrote:
> Uptill now the dbase is small so no performance problems yet.

Wait until you have performance problems and then solve them :-)  It is
almost always the case that performance issues don't crop up where you
think they will.

> I can think of several solutions, but as my experience with databases is
> almost zero, I can't decide

One nice feature SQLite has is virtual tables.  You don't need to do
anything now, but if you have performance issues in the future, you can
use a virtual table for your data and behind the scenes do whatever you
want including storing the data as files.

Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF4PTYmOOfHg372QQRAtciAJ9QXbrq7/A/ksNjzg/EloiUlUBrZwCgumG/
veo4eqw9heMPlc1vuiGDBQw=
=j4my
-END PGP SIGNATURE-

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[mxs]

I realize that, but this is about making it difficult for the average Joe not
to stop professional hackers who I assume can steal anything they want.

Web based approach will not happen in my case and I am not sure you could
guarantee its safety there either. It might be safer with close monitoring,
but never 100% safe.

Thanks

Marek


Florian Weimer wrote:
> 
> * mxs:
> 
>> If anybody knows hot to ensure that the data is not readable without the
>> front end I would appreciate it.
> 
> You need to turn your application into some kind of web-based service
> which is actively monitored for misuse.  
> 
> Anybody who's got a copy of the application can reverse-engineer it
> and reimplement the decryption routines.  There is no way around that.
> 
> -
> To unsubscribe, send email to [EMAIL PROTECTED]
> -
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/SQLite---how-to-protect-the-data-tf3282484.html#a9140122
Sent from the SQLite mailing list archive at Nabble.com.


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[mxs]

Well, it might sound contradictory, but it's not. I don't know how well the
product will sell and I am not prepare to drop down my own cash to do it.
Not at least at the begining.

Regards

Marek



Roger Binns wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> mxs wrote:
>> One of the
>> application I work on contains data which have very high value. 
> [...]
>> I found a link talking about encryption, but this is not exactly
>> affordable
>> for my type of project.
>> http://www.hwaci.com/sw/sqlite/prosupport.html#crypto
> 
> Your statements are contradictory!  It has very high value, but you
> aren't prepared to spend a one time fee of $2,000 to protect that high
> value?
> 
> Roger
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.6 (GNU/Linux)
> 
> iD8DBQFF4O7YmOOfHg372QQRApofAJwORp2fWwlyG0ZJNenVFW0KSQNWEQCfUsYt
> 0+Y3UTKEWz3/xgv8XxNfqQc=
> =tLdz
> -END PGP SIGNATURE-
> 
> -
> To unsubscribe, send email to [EMAIL PROTECTED]
> -
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/SQLite---how-to-protect-the-data-tf3282484.html#a9140103
Sent from the SQLite mailing list archive at Nabble.com.


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[mxs]

Thanks Ulrich, but I think that goes beyond the scope of my knowledge and
tools I have available to me.

I wish somebody (who has C++ knowledge) has done it already and released
version of SQLite with encrypt and decrypt functionality. I cannot believe
that there is not more need for it between SQLite users. You make it sound
like it shouldn't be a problem for someone who knows C++. But I am expecting
a catch somewhere, otherwise why would there be commercial versions of
SQLite which has this functonality.

Thanks for your suggestion anyways.

If you don't mind one more off topic question. You seem to have experience
with wxWidgets. In tandem with wxPython is that a better tool to use than
just Python and Tkinter. Which route is the easier one for a beginner in
this language?

Thanks again

Marek



Ulrich Telle wrote:
> 
> Hi Marek,
> 
>> I'll be honest with you I had to google around to find out what is
>> wxWidgets (obviously I've seen it before, but never dipped in). Pls
>> understand I've been messing around for years with VB (not even the
>> .NET version) and it served me quite well. But I decided to move on
>> to something rather free of Microsoft.
> 
> Well, wxWidgets _is_ free of Microsoft and is available for many different
> platforms. But it wasn't my intent to point you in the direction of
> wxWidgets.
> 
> My encryption solution for SQLite is not bound to wxWidgets in any way.
> You may as well use it completely independent of wxWidgets (or my
> component wxSQLite3).
> 
> You may just take the source code of my encryption extension from the file
> release of wxSQLite3, combine it with the sources of SQLite itself,
> compile with just any C++ compiler to get a SQLite library or DLL
> supporting database encryption. Please read the readme file of wxSQLite3
> for further information.
> 
> My extension implements two functions of the SQLite API, namely
> sqlite3_key and sqlite3_rekey (see sqlite3.h header file of SQLite), which
> are not implemented in the normal SQLite distribution. To use encryption
> sqlite3_key has to be called immediately after the call to sqlite3_open.
> That's all.
> 
> Regards,
> 
> Ulrich
> 
> -
> To unsubscribe, send email to [EMAIL PROTECTED]
> -
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/SQLite---how-to-protect-the-data-tf3282484.html#a9140086
Sent from the SQLite mailing list archive at Nabble.com.


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[Roger Binns]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

mxs wrote:
> One of the
> application I work on contains data which have very high value. 
[...]
> I found a link talking about encryption, but this is not exactly affordable
> for my type of project.
> http://www.hwaci.com/sw/sqlite/prosupport.html#crypto

Your statements are contradictory!  It has very high value, but you
aren't prepared to spend a one time fee of $2,000 to protect that high
value?

Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF4O7YmOOfHg372QQRApofAJwORp2fWwlyG0ZJNenVFW0KSQNWEQCfUsYt
0+Y3UTKEWz3/xgv8XxNfqQc=
=tLdz
-END PGP SIGNATURE-

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] FTS1 dump/restore needs column names

[Adam Megacz]

It seems that when doing a dump/restore on databases with FTS1
enabled, the INSERT commands in the dump need column names.  That is,
if the dump looks like this:

  INSERT INTO "foo" VALUES (x,y,z)

You get the error

  SQL error: table foo has 4 columns but 3 values were supplied

Apparently if the dump looks like this, things work fine:

  INSERT INTO "foo" (a,b,c) VALUES (x,y,z)

So, question: is there a way to get the .dump command to emit dumps in
the latter form?

Thanks,

  - a

-- 
PGP/GPG: 5C9F F366 C9CF 2145 E770  B1B8 EFB1 462D A146 C380

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Martin Jenkins]

RB Smissaert wrote:

Will give that a try and see if it gives any less warnings.


OK, but as Dennis suggested and Dr Hipp has confirmed this isn't the way 
to go. I was assuming the VB thing was a bit of a hack and didn't really 
read enough of the C code.


Martin

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Martin Jenkins]

RB Smissaert wrote:

How would I do this:
compile with -DSQLITE_OMIT_LOAD_EXTENSION=1 to leave it out.


Remember that link tab I said about earlier?

There's a C/C++ tab next to  it with a Preprocessor definitions edit 
box. I think what you want is to put ",SQLITE_OMIT_LOAD_EXTENSION=1" at 
the end of the line and rebuild your DLL. I can't say for sure because I 
don't actually use VC6++ much - I bought a 2nd hand copy a couple of 
years ago so I could compile Python/wxPython but they've moved on now.


Martin

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

OK, when I do instead of commenting those lines out:

  0, //sqlite3_last_insert_rowid,

Etc. I get less warnings. Got 143 now instead 265 and no more
Warnings of the type C4028 and nil anymore in the .c file loadext.c
So, that looks much better.

Is it OK though to do this:

  0, //sqlite3_libversion,
  0, //sqlite3_libversion_number,

Or should I put something different than that zero, like an empty string?
If so how do I do that in C?

It looks then that although it compiled and worked those instructions from
Tod Tanner weren't quite right then.

RBS

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 20:06
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

"RB Smissaert" <[EMAIL PROTECTED]> wrote:
> All C4028 warnings originate from this code block:
> 
> const sqlite3_api_routines sqlite3_apis = {
[...]
>   sqlite3_busy_timeout,
>   //sqlite3_changes,
>   //sqlite3_close,
>   sqlite3_collation_needed,
>   sqlite3_collation_needed16,
> 
> Not sure it is relevant but some lines are commented out to do with making
> it VB compatible.
> 

Yes, it is relevant.  Commenting out those lines breaks the
code in a big way.

If that module is given you problems, why don't you compile
with -DSQLITE_OMIT_LOAD_EXTENSION=1 to leave it out.
--
D. Richard Hipp  <[EMAIL PROTECTED]>



-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Re: Re: how to get field names of empty tables ?

[Stef Mientki]

Scott Hess wrote:

I think only the dot commands are special (.help, etc).  Everything
else is fair game.  Best reference for what you can feed a prepare or
exec is http://www.sqlite.org/lang.html .

Scott,
thanks for this valuable information.
Now how beautiful it would be if it was all in 1 pdf file ;-)

cheers,
Stef


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[Joe Wilson]

--- RB Smissaert <[EMAIL PROTECTED]> wrote:
> Could try with MinGW and MSYS and it may give less warnings, but would it
> produce a dll that is any better? If possible I want to avoid installing
> more software when I already have VC6++.

It's completely up to you. How much time do you want to spend on learning 
VC6 when you have an alternative that is known to work?

No more VC++ for me, thanks. Good luck.



 

Need Mail bonding?
Go to the Yahoo! Mail Q for great tips from Yahoo! Answers users.
http://answers.yahoo.com/dir/?link=list=396546091

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Ok, thanks. I am not a C coder and was following some (faulty?)
instructions.

How would I do this:
compile with -DSQLITE_OMIT_LOAD_EXTENSION=1 to leave it out.

I mean where do I put it?

RBS


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 20:06
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

"RB Smissaert" <[EMAIL PROTECTED]> wrote:
> All C4028 warnings originate from this code block:
> 
> const sqlite3_api_routines sqlite3_apis = {
[...]
>   sqlite3_busy_timeout,
>   //sqlite3_changes,
>   //sqlite3_close,
>   sqlite3_collation_needed,
>   sqlite3_collation_needed16,
> 
> Not sure it is relevant but some lines are commented out to do with making
> it VB compatible.
> 

Yes, it is relevant.  Commenting out those lines breaks the
code in a big way.

If that module is given you problems, why don't you compile
with -DSQLITE_OMIT_LOAD_EXTENSION=1 to leave it out.
--
D. Richard Hipp  <[EMAIL PROTECTED]>



-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

> You're confusing me with someone else.

No, I know it wasn't you.

Could try with MinGW and MSYS and it may give less warnings, but would it
produce a dll that is any better? If possible I want to avoid installing
more software when I already have VC6++.

RBS


-Original Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 19:45
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] compiling with VC++

--- RB Smissaert <[EMAIL PROTECTED]> wrote:
> Downloaded it from the one you pointed to me:

You're confusing me with someone else.

Here's a way to build sqlite3.dll without Microsoft tools using the
official sources:

Grab and install MinGW and MSYS (google for it), 
download http://sqlite.org/sqlite-3.3.13.tar.gz, 
launch the bash shell and issue these commands:

 tar xzvf sqlite-3.3.13.tar.gz
 cd sqlite-3.3.13
 ./configure
 make sqlite3.dll

> 
> and a zip file - sqlite-source-3_3_13.zip - containing preprocessed source
> for Windows users at:
> 
> http://www.sqlite.org/download.html
> 
> Where else could I get it from?
> 
> RBS



 


Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index


-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Will give that a try and see if it gives any less warnings.

RBS


-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 19:21
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:
> Did you make the alterations to make the dll VB compatible?

I don't think Dennis was building the VB version. The lines that Todd 
says you have to comment out - did you comment them out or replace them 
with a 0?

I haven't analysed the code fully but I'm a bit suspicious about that // 
mod.

Firstly, comments in loadext.c says  new functions have to go at the end 
of the list to maintain backwards compatibility, so it sounds like the 
order is significant and 2) when sqlite3_global_recover was deprecated 
it was replaced with 0 rather than being removed completely, which also 
suggests that the order is significant.

On that basis I'd expect to see the line

  ...
  sqlite3_changes,
  ...

replaced with

  ...
  0, // sqlite3_changes,
  ...

and not

  ...
  // sqlite3_changes,
  ...

I can't comment on why Todd chose to remove those lines.

Martin


-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Thanks, that sounds it might be something.

How exactly do I do this:

Instead you should disable compiling the loadable module extension by
defining SQLITE_OMIT_LOAD_EXTENSION.

RBS


-Original Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 19:24
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] compiling with VC++

The suggested changes the web site recommends are incorrect:

 loadext.c

 Comment out the following lines is loadext.c by adding 2 back slashes
("//") to the start of the
line. This prevents errors due to our changes.

 sqlite3_changes,
 sqlite3_close,

 sqlite3_last_insert_rowid,
 sqlite3_libversion,
 sqlite3_libversion_number,

 sqlite3_open,
 sqlite3_open16, 

Instead you should disable compiling the loadable module extension by
defining SQLITE_OMIT_LOAD_EXTENSION.

--- RB Smissaert <[EMAIL PROTECTED]> wrote:

> Microsoft Visual C++ 6 Enterprise edition.
> I think it is the latest before .net came in.
> 
> I am compiling the latest 3.3.13 source as from the URL you mentioned to
me.
> Keep in mind I altered the source to make it VB compatible as in this URL:
> 
> http://www.tannertech.net/sqlite3vb/index.htm
> 
> RBS
> 
> 
> -Original Message-
> From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
> Sent: 24 February 2007 18:52
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] compiling with VC++
> 
> RB Smissaert wrote:
> > Thanks, that is very helpful and reassuring as well.
> > Will see if I can figure out then what is causing this one:
> > warning C4028, as you say that could be a typo.
> 
> I've just built 3.3.12 source with VC6 and didn't see that error. I 
> changed the warning level to 4 and got 500 warnings (signed/unsigned 
> mismatch, oddities in M$ headers, unreferenced parameter NotUsed ;)) but 
> not a C4028 in sight. VC6 is pretty old now - what version are you 
> using? And which sqlite source are you building?
> 
> Martin



 


Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
http://videogames.yahoo.com/platform?platform=120121


-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[drh]

"RB Smissaert" <[EMAIL PROTECTED]> wrote:
> All C4028 warnings originate from this code block:
> 
> const sqlite3_api_routines sqlite3_apis = {
[...]
>   sqlite3_busy_timeout,
>   //sqlite3_changes,
>   //sqlite3_close,
>   sqlite3_collation_needed,
>   sqlite3_collation_needed16,
> 
> Not sure it is relevant but some lines are commented out to do with making
> it VB compatible.
> 

Yes, it is relevant.  Commenting out those lines breaks the
code in a big way.

If that module is given you problems, why don't you compile
with -DSQLITE_OMIT_LOAD_EXTENSION=1 to leave it out.
--
D. Richard Hipp  <[EMAIL PROTECTED]>


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[Joe Wilson]

--- RB Smissaert <[EMAIL PROTECTED]> wrote:
> Downloaded it from the one you pointed to me:

You're confusing me with someone else.

Here's a way to build sqlite3.dll without Microsoft tools using the
official sources:

Grab and install MinGW and MSYS (google for it), 
download http://sqlite.org/sqlite-3.3.13.tar.gz, 
launch the bash shell and issue these commands:

 tar xzvf sqlite-3.3.13.tar.gz
 cd sqlite-3.3.13
 ./configure
 make sqlite3.dll

> 
> and a zip file - sqlite-source-3_3_13.zip - containing preprocessed source
> for Windows users at:
> 
> http://www.sqlite.org/download.html
> 
> Where else could I get it from?
> 
> RBS



 

Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[Ulrich Telle]

Hi Marek,

> I'll be honest with you I had to google around to find out what is
> wxWidgets (obviously I've seen it before, but never dipped in). Pls
> understand I've been messing around for years with VB (not even the
> .NET version) and it served me quite well. But I decided to move on
> to something rather free of Microsoft.

Well, wxWidgets _is_ free of Microsoft and is available for many different 
platforms. But it wasn't my intent to point you in the direction of wxWidgets.

My encryption solution for SQLite is not bound to wxWidgets in any way. You may 
as well use it completely independent of wxWidgets (or my component wxSQLite3).

You may just take the source code of my encryption extension from the file 
release of wxSQLite3, combine it with the sources of SQLite itself, compile 
with just any C++ compiler to get a SQLite library or DLL supporting database 
encryption. Please read the readme file of wxSQLite3 for further information.

My extension implements two functions of the SQLite API, namely sqlite3_key and 
sqlite3_rekey (see sqlite3.h header file of SQLite), which are not implemented 
in the normal SQLite distribution. To use encryption sqlite3_key has to be 
called immediately after the call to sqlite3_open. That's all.

Regards,

Ulrich

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Martin Jenkins]

RB Smissaert wrote:

Microsoft Visual C++ 6 Enterprise edition.


Hmm. I'm using VC6++ Pro. I wonder if it's safe to assume the compilers 
are the same and the difference is that I don't have the Enterprisey 
middleware gubbins.



I think it is the latest before .net came in.


Dunno. I kind of lost interest in M$ around then . ;)

I'll grab the 3.3.13 code and see what happens with that. Given that 
nobody's rung me up to go for a pint yet I'll have a look at the 
TannerTech mods too, but I won't be adding to his "Sole Donation" 
because he says he lifted most of it from another site. ;)


Martin

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[Joe Wilson]

The suggested changes the web site recommends are incorrect:

 loadext.c

 Comment out the following lines is loadext.c by adding 2 back slashes ("//") 
to the start of the
line. This prevents errors due to our changes.

 sqlite3_changes,
 sqlite3_close,

 sqlite3_last_insert_rowid,
 sqlite3_libversion,
 sqlite3_libversion_number,

 sqlite3_open,
 sqlite3_open16, 

Instead you should disable compiling the loadable module extension by
defining SQLITE_OMIT_LOAD_EXTENSION.

--- RB Smissaert <[EMAIL PROTECTED]> wrote:

> Microsoft Visual C++ 6 Enterprise edition.
> I think it is the latest before .net came in.
> 
> I am compiling the latest 3.3.13 source as from the URL you mentioned to me.
> Keep in mind I altered the source to make it VB compatible as in this URL:
> 
> http://www.tannertech.net/sqlite3vb/index.htm
> 
> RBS
> 
> 
> -Original Message-
> From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
> Sent: 24 February 2007 18:52
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] compiling with VC++
> 
> RB Smissaert wrote:
> > Thanks, that is very helpful and reassuring as well.
> > Will see if I can figure out then what is causing this one:
> > warning C4028, as you say that could be a typo.
> 
> I've just built 3.3.12 source with VC6 and didn't see that error. I 
> changed the warning level to 4 and got 500 warnings (signed/unsigned 
> mismatch, oddities in M$ headers, unreferenced parameter NotUsed ;)) but 
> not a C4028 in sight. VC6 is pretty old now - what version are you 
> using? And which sqlite source are you building?
> 
> Martin



 

Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
http://videogames.yahoo.com/platform?platform=120121

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Martin Jenkins]

RB Smissaert wrote:

Thanks, that is very helpful and reassuring as well.
Will see if I can figure out then what is causing this one:
warning C4028, as you say that could be a typo.


I've just built 3.3.12 source with VC6 and didn't see that error. I 
changed the warning level to 4 and got 500 warnings (signed/unsigned 
mismatch, oddities in M$ headers, unreferenced parameter NotUsed ;)) but 
not a C4028 in sight. VC6 is pretty old now - what version are you 
using? And which sqlite source are you building?


Martin

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Martin Jenkins]

RB Smissaert wrote:

Did you make the alterations to make the dll VB compatible?


I don't think Dennis was building the VB version. The lines that Todd 
says you have to comment out - did you comment them out or replace them 
with a 0?


I haven't analysed the code fully but I'm a bit suspicious about that // 
mod.


Firstly, comments in loadext.c says  new functions have to go at the end 
of the list to maintain backwards compatibility, so it sounds like the 
order is significant and 2) when sqlite3_global_recover was deprecated 
it was replaced with 0 rather than being removed completely, which also 
suggests that the order is significant.


On that basis I'd expect to see the line

 ...
 sqlite3_changes,
 ...

replaced with

 ...
 0, // sqlite3_changes,
 ...

and not

 ...
 // sqlite3_changes,
 ...

I can't comment on why Todd chose to remove those lines.

Martin

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[Florian Weimer]

* mxs:

> If anybody knows hot to ensure that the data is not readable without the
> front end I would appreciate it.

You need to turn your application into some kind of web-based service
which is actively monitored for misuse.  

Anybody who's got a copy of the application can reverse-engineer it
and reimplement the decryption routines.  There is no way around that.

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Downloaded it from the one you pointed to me:

and a zip file - sqlite-source-3_3_13.zip - containing preprocessed source
for Windows users at:

http://www.sqlite.org/download.html

Where else could I get it from?

RBS

-Original Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 19:06
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] compiling with VC++

The function signatures at the lines in question look wrong to me.
Do you have the correct version of sqlite3ext.h?

--- RB Smissaert <[EMAIL PROTECTED]> wrote:
> Here examples of all 3, all from the same source file and the same code
> block:
> 
> C:\SQLite\SourceWin\loadext.c(138) : warning C4047: 'initializing' : 'int
> (__cdecl *)(struct sqlite3_stmt *,int )' differs in levels of indirection
> from 'const char *(__cdecl *)(struct sqlite3_stmt *,int )'
> 
> const sqlite3_api_routines sqlite3_apis = {
>   sqlite3_column_double,
> 
> 
> C:\SQLite\SourceWin\loadext.c(125) : warning C4113: 'int (__cdecl
*)(struct
> sqlite3 *,void *,void (__cdecl *)(void *,struct sqlite3 *,int ,const char
> *))' differs in parameter lists from 'int (__cdecl *)(struct sqlite3 *)'
> 
> const sqlite3_api_routines sqlite3_apis = {
>   sqlite3_collation_needed,
> 
> 
> C:\SQLite\SourceWin\loadext.c(208) : warning C4133: 'initializing' :
> incompatible types - from 'void *(__cdecl *)(struct sqlite3 *,void
(__cdecl
> *)(void *,int ,const char *,const char *,__int64 ),void *)' to 'char
> *(__cdecl *)(int ,char *,const char
>  *,... )'
> 
> 
> const sqlite3_api_routines sqlite3_apis = {
>   sqlite3_update_hook,
> 
> 
> This codeblock ends like this:
> 
>   /*
>   ** The original API set ends here.  All extensions can call any
>   ** of the APIs above provided that the pointer is not NULL.  But
>   ** before calling APIs that follow, extension should check the
>   ** sqlite3_libversion_number() to make sure they are dealing with
>   ** a library that is new enough to support that API.
>
*
>   */
>   sqlite3_overload_function,
> };
> 
> 
> RBS
> 
> 
> -Original Message-
> From: Joe Wilson [mailto:[EMAIL PROTECTED] 
> Sent: 24 February 2007 17:29
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] compiling with VC++
> 
> They're probably harmless.
> 
> Even so, can you post the file name/line of one example of each of the 
> following 3 warnings as they seem odd:
> 
> warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)'
differs
> in levels of indirection from 'char *(__cdecl *)(const char *,char *)'
> 
> warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
> lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int
> ,const char *,const char *,__int64 ),void *)'
> 
> warning C4133: 'initializing' : incompatible types - from '__int64
(__cdecl
> *)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt
> *,int )'
> 
> --- RB Smissaert <[EMAIL PROTECTED]> wrote:
> > When compiling this source code I get 265 warning, which doesn't really
> > worry me that much as it all seems to be working fine, but in general
what
> > kind of warning should be taken seriously?
> > 
> > I only have 8 different types of warnings:
> > 
> > warning C4018: '!=' : signed/unsigned mismatch
> > warning C4028: formal parameter 1 different from declaration
> > warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)'
> differs
> > in levels of indirection from 'char *(__cdecl *)(const char *,char *)'
> > warning C4090: 'function' : different 'const' qualifiers
> > warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
> > lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void
*,int
> > ,const char *,const char *,__int64 ),void *)'
> > warning C4133: 'initializing' : incompatible types - from '__int64
> (__cdecl
> > *)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct
sqlite3_stmt
> > *,int )'
> > warning C4244: '+=' : conversion from '__int64 ' to 'int ', possible
loss
> of
> > data
> > warning C4761: integral size mismatch in argument; conversion supplied




 


Need Mail bonding?
Go to the Yahoo! Mail Q for great tips from Yahoo! Answers users.
http://answers.yahoo.com/dir/?link=list=396546091


-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Microsoft Visual C++ 6 Enterprise edition.
I think it is the latest before .net came in.

I am compiling the latest 3.3.13 source as from the URL you mentioned to me.
Keep in mind I altered the source to make it VB compatible as in this URL:

http://www.tannertech.net/sqlite3vb/index.htm

RBS


-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 18:52
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:
> Thanks, that is very helpful and reassuring as well.
> Will see if I can figure out then what is causing this one:
> warning C4028, as you say that could be a typo.

I've just built 3.3.12 source with VC6 and didn't see that error. I 
changed the warning level to 4 and got 500 warnings (signed/unsigned 
mismatch, oddities in M$ headers, unreferenced parameter NotUsed ;)) but 
not a C4028 in sight. VC6 is pretty old now - what version are you 
using? And which sqlite source are you building?

Martin


-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[Joe Wilson]

The function signatures at the lines in question look wrong to me.
Do you have the correct version of sqlite3ext.h?

--- RB Smissaert <[EMAIL PROTECTED]> wrote:
> Here examples of all 3, all from the same source file and the same code
> block:
> 
> C:\SQLite\SourceWin\loadext.c(138) : warning C4047: 'initializing' : 'int
> (__cdecl *)(struct sqlite3_stmt *,int )' differs in levels of indirection
> from 'const char *(__cdecl *)(struct sqlite3_stmt *,int )'
> 
> const sqlite3_api_routines sqlite3_apis = {
>   sqlite3_column_double,
> 
> 
> C:\SQLite\SourceWin\loadext.c(125) : warning C4113: 'int (__cdecl *)(struct
> sqlite3 *,void *,void (__cdecl *)(void *,struct sqlite3 *,int ,const char
> *))' differs in parameter lists from 'int (__cdecl *)(struct sqlite3 *)'
> 
> const sqlite3_api_routines sqlite3_apis = {
>   sqlite3_collation_needed,
> 
> 
> C:\SQLite\SourceWin\loadext.c(208) : warning C4133: 'initializing' :
> incompatible types - from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl
> *)(void *,int ,const char *,const char *,__int64 ),void *)' to 'char
> *(__cdecl *)(int ,char *,const char
>  *,... )'
> 
> 
> const sqlite3_api_routines sqlite3_apis = {
>   sqlite3_update_hook,
> 
> 
> This codeblock ends like this:
> 
>   /*
>   ** The original API set ends here.  All extensions can call any
>   ** of the APIs above provided that the pointer is not NULL.  But
>   ** before calling APIs that follow, extension should check the
>   ** sqlite3_libversion_number() to make sure they are dealing with
>   ** a library that is new enough to support that API.
>   *
>   */
>   sqlite3_overload_function,
> };
> 
> 
> RBS
> 
> 
> -Original Message-
> From: Joe Wilson [mailto:[EMAIL PROTECTED] 
> Sent: 24 February 2007 17:29
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] compiling with VC++
> 
> They're probably harmless.
> 
> Even so, can you post the file name/line of one example of each of the 
> following 3 warnings as they seem odd:
> 
> warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)' differs
> in levels of indirection from 'char *(__cdecl *)(const char *,char *)'
> 
> warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
> lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int
> ,const char *,const char *,__int64 ),void *)'
> 
> warning C4133: 'initializing' : incompatible types - from '__int64 (__cdecl
> *)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt
> *,int )'
> 
> --- RB Smissaert <[EMAIL PROTECTED]> wrote:
> > When compiling this source code I get 265 warning, which doesn't really
> > worry me that much as it all seems to be working fine, but in general what
> > kind of warning should be taken seriously?
> > 
> > I only have 8 different types of warnings:
> > 
> > warning C4018: '!=' : signed/unsigned mismatch
> > warning C4028: formal parameter 1 different from declaration
> > warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)'
> differs
> > in levels of indirection from 'char *(__cdecl *)(const char *,char *)'
> > warning C4090: 'function' : different 'const' qualifiers
> > warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
> > lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int
> > ,const char *,const char *,__int64 ),void *)'
> > warning C4133: 'initializing' : incompatible types - from '__int64
> (__cdecl
> > *)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt
> > *,int )'
> > warning C4244: '+=' : conversion from '__int64 ' to 'int ', possible loss
> of
> > data
> > warning C4761: integral size mismatch in argument; conversion supplied




 

Need Mail bonding?
Go to the Yahoo! Mail Q for great tips from Yahoo! Answers users.
http://answers.yahoo.com/dir/?link=list=396546091

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Did you make the alterations to make the dll VB compatible?

RBS

-Original Message-
From: Dennis Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 18:39
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:
> Thanks, will have a look at that.
> Do you know from experience that it will compile OK with VC6++?
>
>   

I use VC 6.0 and it compiles just fine.  I did not follow the 
instructions on the web site.  I didn't even read them.  I just put all 
of the C files into a single directory (except for the tcl one and 
shell.c - leave those out) and build a static library project using the 
source files.  I did use the pre-processed C/H files from the windows 
zip file though (so I used sqlite.h, not sqlite.h.in).



-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[Rich Shepard]

On Sat, 24 Feb 2007, Martin Jenkins wrote:


mxs wrote:

I decided I'd like to try Python and SQLite

Check out wxPython too.


  Python->wxPython->pysqlite2->sqlite3

  Works for me.

Rich

--
Richard B. Shepard, Ph.D.   |The Environmental Permitting
Applied Ecosystem Services, Inc.|  Accelerator(TM)
 Voice: 503-667-4517  Fax: 503-667-8863

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Dennis Jenkins]

RB Smissaert wrote:

Thanks, will have a look at that.
Do you know from experience that it will compile OK with VC6++?

  


I use VC 6.0 and it compiles just fine.  I did not follow the 
instructions on the web site.  I didn't even read them.  I just put all 
of the C files into a single directory (except for the tcl one and 
shell.c - leave those out) and build a static library project using the 
source files.  I did use the pre-processed C/H files from the windows 
zip file though (so I used sqlite.h, not sqlite.h.in).



-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[mxs]

Adriano,

this one looks good and the price is not out of the world although not cheap
either.

So this is basically a modified sqlite database which has an additional
function .encrypt and .decrypt. I haven't used many open source products
before so I am not sure how it works as far taking basically a free product
add two (could be more than that I know) functions and charge 150 bucks for
it. If it's not based on the free SQLite and is totally different database
engine then be it, but to me it looks like it rather is (but I haven't
looked too deep).

Obviously this looks like the easiest solution by far. At least to me for
now. Disadvantage is that it is not open source so if the company goes and
there's a bug, there goes your investment 

Regards

Marek



Adriano-8 wrote:
> 
> I'm in the same boat too.
> I've just found http://www.sqlcrypt.com/
> not tryed yet
> 
> i need something that can works either on pc or on windoes mobile devices
> thanks
> Adriano
> 
> -
> To unsubscribe, send email to [EMAIL PROTECTED]
> -
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/SQLite---how-to-protect-the-data-tf3282484.html#a9136419
Sent from the SQLite mailing list archive at Nabble.com.


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Thanks, that is very helpful and reassuring as well.
Will see if I can figure out then what is causing this one:
warning C4028, as you say that could be a typo.

RBS

-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 18:11
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:
> When compiling this source code I get 265 warning, which doesn't really
> worry me that much as it all seems to be working fine, but in general what
> kind of warning should be taken seriously?

This has come up the list before. Dr Hipp assigns a lot more weight to 
his tests passing than the complete absence of compiler warnings. This 
may sound cavalier but many of these warnings are in fact pretty benign. 
If you have a comprehensive test suite (as SQLite does) you can assume 
that these warnings *are* benign. One widely accepted reason for not 
"fixing" them is that most of the fixes (usually casts to similar type) 
just clutter up your source code and mask the intentions of the author.

> I only have 8 different types of warnings:

I won't go through them in huge detail because it's hard to say what the 
problem is without seeing the specific source lines, but generally 
compilers play safe and it's up to the author to know what he's doing. 
It can be a bit scary when you compile someone else's code for the first 
time - you see a load of warnings and think what a load of [EMAIL PROTECTED] 
but most 
of the time it's just the compiler being picky. As I said above, if you 
have a decent test suite you can relax a lot.

> warning C4018: '!=' : signed/unsigned mismatch

This is usually benign. Say you have an variable in which you store the 
unsigned return value from a library function. You know the value is 
always +ve so you make the variable unsigned. The compiler doesn't know 
the number will always be +ve but it knows signed/unsigned mismatch is a 
common source of bugs so it reports a warning. A cast would fix the 
warning but might suggest to the reader that the author wanted to force 
some kind of conversion. Or it might not.

> warning C4028: formal parameter 1 different from declaration

Without seeing the code, it's hard to say, but I'd expect this to be an 
error or a typo. Whether it matters is something else - it could be the 
signed/unsigned issue above.

> warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)'
differs
> in levels of indirection from 'char *(__cdecl *)(const char *,char *)'

Hard to say without seeing the code. Indirection in C can be quite 
tricky and is a common source of bugs, but I'd be surprised to see 
anything like that in SQLite.

> warning C4090: 'function' : different 'const' qualifiers

This is common when using string library functions. They're declared 
const because, say, strlen won't alter your data and your pointers are 
not declared const because they do. Sometimes an error but usually ok.

> warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
> lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int
> ,const char *,const char *,__int64 ),void *)'
> warning C4133: 'initializing' : incompatible types - from '__int64
(__cdecl
> *)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt
> *,int )'

Hard to say without seeing the code, but it looks related to the 
indirection warning above.

> warning C4244: '+=' : conversion from '__int64 ' to 'int ', possible loss
of
> data
> warning C4761: integral size mismatch in argument; conversion supplied

Common warnings where the compiler has converted between say 16/32 bit 
ints and 32/64 bit longs. It's OK in one direction but it may not be OK 
in the other, so the compiler warns and it's up to you to check. If the 
int/long variable only holds small numbers it's not significant but the 
compiler can't tell what numbers will be stored and so it's back to you.

This explanation is brief and fairly rushed so may it not be completely 
rigorous in places but I hope it helps a bit.

Martin



-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[Martin Jenkins]

mxs wrote:

I had to google around to find out what is wxWidgets
...
I decided I'd like to try Python and SQLite


Check out wxPython too.

Martin

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] sqlite ebuild - my problem, i have half year ago, is still here.

[Martin Jenkins]

Jakub Ladman wrote:

Hi Friends
Please help me
I need crosscompile sqlite for my sh4 cpu based linux system, but configure 
script (any version of sqlite i have tryed, even the actual one from sqlite 
homepage) fails if crosscompilation is selected.

Crosscompiler works good in other cases.
Thank you very much.


The autoconf stuff is unsupported and from recent comments hereabouts is 
likely to stay that way. I started to look at it last year but didn't 
get too far and didn't get anywhere near looking at cross-compilation. 
There are some autoconf tools which might help - autoreconf comes to 
mind but if they don't help I think you're going to be on your own 
unless you can find someone who knows autoconf reasonably well and 
persuade them to fix it up a bit.


There's a Linux Makefile in the source tree - I believe that it's used 
to build the binaries on the website - have you tried hacking that to 
see if it will work on your system?


Martin

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[mxs]

Hi Olaf,

so I took a quick look and it looks interesting, certainly very affordable.
One caveat could be that it doesn't seem to work under OS X which will be
important to me. Also all I coud find was how to encrypt stuff through their
GUI, but nothing about available API. When I distribute the app the database
must be already in encrypted mode and my frontend will take care of decrypt
through the API. At least that's what I kind of envision. But maybe I missed
something.

Thanks

Marek



Olaf Beckman Lapré wrote:
> 
> Hi,
> 
> Why not just encrypt the file system or part of the disk where the
> database 
> is situated? I use TrueCrypt, a free open-source program, for this and it 
> works great and it's very fast. Unless you're doing hundreds of
> transactions 
> per second, you'll hardly notice the performance loss (with
> AES/Whirlpool). 
> You can then also encrypt USB memory sticks when you take the database
> with 
> you.
> 
> Regards, Olaf
> 
> - Original Message - 
> From: "mxs" <[EMAIL PROTECTED]>
> To: 
> Sent: Saturday, February 24, 2007 04:14
> Subject: [sqlite] SQLite - how to protect the data
> 
> 
>>
>> Hi guys,
>>
>> I am quite new here and quite new to SQLite. I am shocked how small and 
>> fast
>> this database is. So far I've been using MS Access for my little projects
>> and I cannot wait to replace it with SQLite.
>>
>> Now, I have a question which I will have to deal with. One of the
>> application I work on contains data which have very high value. In
>> another
>> words the whole value of the app is the database, rather than the front 
>> end.
>> If somebody makes a clone of the front end I don't care, but if somebody
>> copies the database and uses the data for his own front end that would be 
>> a
>> disaster. It is not a privacy issue, but rather the amount of effort put
>> into filling the database up. I used to use a kind of crypto ActiveX when
>> Access was used. It worked although slowed already not fastest database 
>> down
>> which showed during search and filter operations.
>>
>> If anybody knows hot to ensure that the data is not readable without the
>> front end I would appreciate it.
>>
>> I found a link talking about encryption, but this is not exactly 
>> affordable
>> for my type of project.
>> http://www.hwaci.com/sw/sqlite/prosupport.html#crypto
>>
>>
>> Thanks for any suggestions.
>>
>> Cheers
>>
>> Marek
>> -- 
>> View this message in context: 
>> http://www.nabble.com/SQLite---how-to-protect-the-data-tf3282484.html#a9130596
>> Sent from the SQLite mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, send email to [EMAIL PROTECTED]
>> -
>>
>> 
> 
> 
> 
> -
> To unsubscribe, send email to [EMAIL PROTECTED]
> -
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/SQLite---how-to-protect-the-data-tf3282484.html#a9136345
Sent from the SQLite mailing list archive at Nabble.com.


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Here examples of all 3, all from the same source file and the same code
block:

C:\SQLite\SourceWin\loadext.c(138) : warning C4047: 'initializing' : 'int
(__cdecl *)(struct sqlite3_stmt *,int )' differs in levels of indirection
from 'const char *(__cdecl *)(struct sqlite3_stmt *,int )'

const sqlite3_api_routines sqlite3_apis = {
  sqlite3_column_double,


C:\SQLite\SourceWin\loadext.c(125) : warning C4113: 'int (__cdecl *)(struct
sqlite3 *,void *,void (__cdecl *)(void *,struct sqlite3 *,int ,const char
*))' differs in parameter lists from 'int (__cdecl *)(struct sqlite3 *)'

const sqlite3_api_routines sqlite3_apis = {
  sqlite3_collation_needed,


C:\SQLite\SourceWin\loadext.c(208) : warning C4133: 'initializing' :
incompatible types - from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl
*)(void *,int ,const char *,const char *,__int64 ),void *)' to 'char
*(__cdecl *)(int ,char *,const char
 *,... )'


const sqlite3_api_routines sqlite3_apis = {
  sqlite3_update_hook,


This codeblock ends like this:

  /*
  ** The original API set ends here.  All extensions can call any
  ** of the APIs above provided that the pointer is not NULL.  But
  ** before calling APIs that follow, extension should check the
  ** sqlite3_libversion_number() to make sure they are dealing with
  ** a library that is new enough to support that API.
  *
  */
  sqlite3_overload_function,
};


RBS


-Original Message-
From: Joe Wilson [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 17:29
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] compiling with VC++

They're probably harmless.

Even so, can you post the file name/line of one example of each of the 
following 3 warnings as they seem odd:

warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)' differs
in levels of indirection from 'char *(__cdecl *)(const char *,char *)'

warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int
,const char *,const char *,__int64 ),void *)'

warning C4133: 'initializing' : incompatible types - from '__int64 (__cdecl
*)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt
*,int )'

--- RB Smissaert <[EMAIL PROTECTED]> wrote:
> When compiling this source code I get 265 warning, which doesn't really
> worry me that much as it all seems to be working fine, but in general what
> kind of warning should be taken seriously?
> 
> I only have 8 different types of warnings:
> 
> warning C4018: '!=' : signed/unsigned mismatch
> warning C4028: formal parameter 1 different from declaration
> warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)'
differs
> in levels of indirection from 'char *(__cdecl *)(const char *,char *)'
> warning C4090: 'function' : different 'const' qualifiers
> warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
> lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int
> ,const char *,const char *,__int64 ),void *)'
> warning C4133: 'initializing' : incompatible types - from '__int64
(__cdecl
> *)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt
> *,int )'
> warning C4244: '+=' : conversion from '__int64 ' to 'int ', possible loss
of
> data
> warning C4761: integral size mismatch in argument; conversion supplied



 


Looking for earth-friendly autos? 
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
http://autos.yahoo.com/green_center/


-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Martin Jenkins]

RB Smissaert wrote:

When compiling this source code I get 265 warning, which doesn't really
worry me that much as it all seems to be working fine, but in general what
kind of warning should be taken seriously?


This has come up the list before. Dr Hipp assigns a lot more weight to 
his tests passing than the complete absence of compiler warnings. This 
may sound cavalier but many of these warnings are in fact pretty benign. 
If you have a comprehensive test suite (as SQLite does) you can assume 
that these warnings *are* benign. One widely accepted reason for not 
"fixing" them is that most of the fixes (usually casts to similar type) 
just clutter up your source code and mask the intentions of the author.



I only have 8 different types of warnings:


I won't go through them in huge detail because it's hard to say what the 
problem is without seeing the specific source lines, but generally 
compilers play safe and it's up to the author to know what he's doing. 
It can be a bit scary when you compile someone else's code for the first 
time - you see a load of warnings and think what a load of [EMAIL PROTECTED] but most 
of the time it's just the compiler being picky. As I said above, if you 
have a decent test suite you can relax a lot.



warning C4018: '!=' : signed/unsigned mismatch


This is usually benign. Say you have an variable in which you store the 
unsigned return value from a library function. You know the value is 
always +ve so you make the variable unsigned. The compiler doesn't know 
the number will always be +ve but it knows signed/unsigned mismatch is a 
common source of bugs so it reports a warning. A cast would fix the 
warning but might suggest to the reader that the author wanted to force 
some kind of conversion. Or it might not.



warning C4028: formal parameter 1 different from declaration


Without seeing the code, it's hard to say, but I'd expect this to be an 
error or a typo. Whether it matters is something else - it could be the 
signed/unsigned issue above.



warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)' differs
in levels of indirection from 'char *(__cdecl *)(const char *,char *)'


Hard to say without seeing the code. Indirection in C can be quite 
tricky and is a common source of bugs, but I'd be surprised to see 
anything like that in SQLite.



warning C4090: 'function' : different 'const' qualifiers


This is common when using string library functions. They're declared 
const because, say, strlen won't alter your data and your pointers are 
not declared const because they do. Sometimes an error but usually ok.



warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int
,const char *,const char *,__int64 ),void *)'
warning C4133: 'initializing' : incompatible types - from '__int64 (__cdecl
*)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt
*,int )'


Hard to say without seeing the code, but it looks related to the 
indirection warning above.



warning C4244: '+=' : conversion from '__int64 ' to 'int ', possible loss of
data
warning C4761: integral size mismatch in argument; conversion supplied


Common warnings where the compiler has converted between say 16/32 bit 
ints and 32/64 bit longs. It's OK in one direction but it may not be OK 
in the other, so the compiler warns and it's up to you to check. If the 
int/long variable only holds small numbers it's not significant but the 
compiler can't tell what numbers will be stored and so it's back to you.


This explanation is brief and fairly rushed so may it not be completely 
rigorous in places but I hope it helps a bit.


Martin


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[mxs]

Hi Ulrich,

I'll be honest with you I had to google around to find out what is wxWidgets
(obviously I've seen it before, but never dipped in). Pls understand I've
been messing around for years with VB (not even the .NET version) and it
served me quite well. But I decided to move on to something rather free of
Microsoft. So I decided I'd like to try Python and SQLite and convert one of
my projects. This would also let me make my product available to other OS
platforms which was one of the original reasons I decided to look elsewhere.

So it sounds like I have a lot of work (interisting one though) ahead of me
and your solution sounds very much ready and usable as soon as I am
confident of my steps in Python etc.

Thanks for your tip.


Regards

Marek
-- 
View this message in context: 
http://www.nabble.com/SQLite---how-to-protect-the-data-tf3282484.html#a9136243
Sent from the SQLite mailing list archive at Nabble.com.


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[mxs]

Hi John,

thanks for  the suggestion, but that is rather more than I can swallow right
now. I will have to keep looking for more complete solution which I can just
benefit from.

Regards

Marek
-- 
View this message in context: 
http://www.nabble.com/SQLite---how-to-protect-the-data-tf3282484.html#a9136154
Sent from the SQLite mailing list archive at Nabble.com.


-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] Problem with crosscompiler and sqlite - was subject mismatch Re: [sqlite] sqlite ebuild - my problem, i have half year ago, is still here.

[Jakub Ladman]

Dne sobota 24 únor 2007 18:33 Jakub Ladman napsal(a):
> Hi Friends
> Please help me
> I need crosscompile sqlite for my sh4 cpu based linux system, but configure
> script (any version of sqlite i have tryed, even the actual one from sqlite
> homepage) fails if crosscompilation is selected.
> Crosscompiler works good in other cases.
> Thank you very much.
>
> Jakub Ladman
>
> ./configure --build=i686-pc-linux-gnu --host=sh4-pc-linux-uclibc
> --disable-tcl checking build system type... i686-pc-linux-gnu
> checking host system type... sh4-pc-linux-uclibc
> checking for sh4-pc-linux-uclibc-gcc... sh4-pc-linux-uclibc-gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... yes
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether sh4-pc-linux-uclibc-gcc accepts -g... yes
> checking for sh4-pc-linux-uclibc-gcc option to accept ANSI C... none needed
> checking for a sed that does not truncate output... /bin/sed
> checking for egrep... grep -E
> checking for ld used by sh4-pc-linux-uclibc-gcc... sh4-pc-linux-uclibc-ld
> checking if the linker (sh4-pc-linux-uclibc-ld) is GNU ld... yes
> checking for sh4-pc-linux-uclibc-ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/sh4-pc-linux-uclibc-nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... sh4-pc-linux-uclibc-gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking for sh4-pc-linux-uclibc-g++... sh4-pc-linux-uclibc-g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether sh4-pc-linux-uclibc-g++ accepts -g... yes
> checking how to run the C++ preprocessor... sh4-pc-linux-uclibc-g++ -E
> checking for sh4-pc-linux-uclibc-g77... sh4-pc-linux-uclibc-g77
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether sh4-pc-linux-uclibc-g77 accepts -g... yes
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/bin/sh4-pc-linux-uclibc-nm -B output from
> sh4-pc-linux-uclibc-gcc object... ok
> checking for objdir... .libs
> checking for sh4-pc-linux-uclibc-ar... sh4-pc-linux-uclibc-ar
> checking for sh4-pc-linux-uclibc-ranlib... sh4-pc-linux-uclibc-ranlib
> checking for sh4-pc-linux-uclibc-strip... sh4-pc-linux-uclibc-strip
> checking if sh4-pc-linux-uclibc-gcc static flag  works... yes
> checking if sh4-pc-linux-uclibc-gcc supports -fno-rtti -fno-exceptions...
> no checking for sh4-pc-linux-uclibc-gcc option to produce PIC... -fPIC
> checking if sh4-pc-linux-uclibc-gcc PIC flag -fPIC works... yes
> checking if sh4-pc-linux-uclibc-gcc supports -c -o file.o... yes
> checking whether the sh4-pc-linux-uclibc-gcc linker
> (sh4-pc-linux-uclibc-ld) supports shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by sh4-pc-linux-uclibc-g++... sh4-pc-linux-uclibc-ld
> checking if the linker (sh4-pc-linux-uclibc-ld) is GNU ld... yes
> checking whether the sh4-pc-linux-uclibc-g++ linker
> (sh4-pc-linux-uclibc-ld) supports shared libraries... yes
> checking for sh4-pc-linux-uclibc-g++ option to produce PIC... -fPIC
> checking if sh4-pc-linux-uclibc-g++ PIC flag -fPIC works... yes
> checking if sh4-pc-linux-uclibc-g++ supports -c -o file.o... yes
> checking whether the sh4-pc-linux-uclibc-g++ linker
> (sh4-pc-linux-uclibc-ld) supports shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> appending configuration tag "F77" to libtool
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> checking for sh4-pc-linux-uclibc-g77 option to produce PIC... -fPIC
> checking if sh4-pc-linux-uclibc-g77 PIC flag -fPIC works... yes
> checking if sh4-pc-linux-uclibc-g77 

[sqlite] sqlite ebuild - my problem, i have half year ago, is still here.

[Jakub Ladman]

Hi Friends
Please help me
I need crosscompile sqlite for my sh4 cpu based linux system, but configure 
script (any version of sqlite i have tryed, even the actual one from sqlite 
homepage) fails if crosscompilation is selected.
Crosscompiler works good in other cases.
Thank you very much.

Jakub Ladman

./configure --build=i686-pc-linux-gnu --host=sh4-pc-linux-uclibc --disable-tcl
checking build system type... i686-pc-linux-gnu
checking host system type... sh4-pc-linux-uclibc
checking for sh4-pc-linux-uclibc-gcc... sh4-pc-linux-uclibc-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether sh4-pc-linux-uclibc-gcc accepts -g... yes
checking for sh4-pc-linux-uclibc-gcc option to accept ANSI C... none needed
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by sh4-pc-linux-uclibc-gcc... sh4-pc-linux-uclibc-ld
checking if the linker (sh4-pc-linux-uclibc-ld) is GNU ld... yes
checking for sh4-pc-linux-uclibc-ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/sh4-pc-linux-uclibc-nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... sh4-pc-linux-uclibc-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for sh4-pc-linux-uclibc-g++... sh4-pc-linux-uclibc-g++
checking whether we are using the GNU C++ compiler... yes
checking whether sh4-pc-linux-uclibc-g++ accepts -g... yes
checking how to run the C++ preprocessor... sh4-pc-linux-uclibc-g++ -E
checking for sh4-pc-linux-uclibc-g77... sh4-pc-linux-uclibc-g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether sh4-pc-linux-uclibc-g77 accepts -g... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/sh4-pc-linux-uclibc-nm -B output from 
sh4-pc-linux-uclibc-gcc object... ok
checking for objdir... .libs
checking for sh4-pc-linux-uclibc-ar... sh4-pc-linux-uclibc-ar
checking for sh4-pc-linux-uclibc-ranlib... sh4-pc-linux-uclibc-ranlib
checking for sh4-pc-linux-uclibc-strip... sh4-pc-linux-uclibc-strip
checking if sh4-pc-linux-uclibc-gcc static flag  works... yes
checking if sh4-pc-linux-uclibc-gcc supports -fno-rtti -fno-exceptions... no
checking for sh4-pc-linux-uclibc-gcc option to produce PIC... -fPIC
checking if sh4-pc-linux-uclibc-gcc PIC flag -fPIC works... yes
checking if sh4-pc-linux-uclibc-gcc supports -c -o file.o... yes
checking whether the sh4-pc-linux-uclibc-gcc linker (sh4-pc-linux-uclibc-ld) 
supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by sh4-pc-linux-uclibc-g++... sh4-pc-linux-uclibc-ld
checking if the linker (sh4-pc-linux-uclibc-ld) is GNU ld... yes
checking whether the sh4-pc-linux-uclibc-g++ linker (sh4-pc-linux-uclibc-ld) 
supports shared libraries... yes
checking for sh4-pc-linux-uclibc-g++ option to produce PIC... -fPIC
checking if sh4-pc-linux-uclibc-g++ PIC flag -fPIC works... yes
checking if sh4-pc-linux-uclibc-g++ supports -c -o file.o... yes
checking whether the sh4-pc-linux-uclibc-g++ linker (sh4-pc-linux-uclibc-ld) 
supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for sh4-pc-linux-uclibc-g77 option to produce PIC... -fPIC
checking if sh4-pc-linux-uclibc-g77 PIC flag -fPIC works... yes
checking if sh4-pc-linux-uclibc-g77 supports -c -o file.o... yes
checking whether the sh4-pc-linux-uclibc-g77 linker (sh4-pc-linux-uclibc-ld) 
supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library 

RE: [sqlite] compiling with VC++

[Joe Wilson]

They're probably harmless.

Even so, can you post the file name/line of one example of each of the 
following 3 warnings as they seem odd:

warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)' differs
in levels of indirection from 'char *(__cdecl *)(const char *,char *)'

warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int
,const char *,const char *,__int64 ),void *)'

warning C4133: 'initializing' : incompatible types - from '__int64 (__cdecl
*)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt
*,int )'

--- RB Smissaert <[EMAIL PROTECTED]> wrote:
> When compiling this source code I get 265 warning, which doesn't really
> worry me that much as it all seems to be working fine, but in general what
> kind of warning should be taken seriously?
> 
> I only have 8 different types of warnings:
> 
> warning C4018: '!=' : signed/unsigned mismatch
> warning C4028: formal parameter 1 different from declaration
> warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)' differs
> in levels of indirection from 'char *(__cdecl *)(const char *,char *)'
> warning C4090: 'function' : different 'const' qualifiers
> warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
> lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int
> ,const char *,const char *,__int64 ),void *)'
> warning C4133: 'initializing' : incompatible types - from '__int64 (__cdecl
> *)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt
> *,int )'
> warning C4244: '+=' : conversion from '__int64 ' to 'int ', possible loss of
> data
> warning C4761: integral size mismatch in argument; conversion supplied



 

Looking for earth-friendly autos? 
Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.
http://autos.yahoo.com/green_center/

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

When compiling this source code I get 265 warning, which doesn't really
worry me that much as it all seems to be working fine, but in general what
kind of warning should be taken seriously?

I only have 8 different types of warnings:

warning C4018: '!=' : signed/unsigned mismatch
warning C4028: formal parameter 1 different from declaration
warning C4047: 'initializing' : '__int64 (__cdecl *)(struct Mem *)' differs
in levels of indirection from 'char *(__cdecl *)(const char *,char *)'
warning C4090: 'function' : different 'const' qualifiers
warning C4113: '__int64 (__cdecl *)(struct Mem *)' differs in parameter
lists from 'void *(__cdecl *)(struct sqlite3 *,void (__cdecl *)(void *,int
,const char *,const char *,__int64 ),void *)'
warning C4133: 'initializing' : incompatible types - from '__int64 (__cdecl
*)(struct sqlite3_stmt *,int )' to 'double (__cdecl *)(struct sqlite3_stmt
*,int )'
warning C4244: '+=' : conversion from '__int64 ' to 'int ', possible loss of
data
warning C4761: integral size mismatch in argument; conversion supplied

RBS

-Original Message-
From: RB Smissaert [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 16:18
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] compiling with VC++

Thanks, that is it, nice and simple.

RBS

-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 15:40
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:

> Now what do I do make it compile a dll called SQLite3VB.dll?

I think it defaults to the project name, but have a look at the Link tab 
in the Project|Settings dialog (Alt-F7) - there's an edit box titled 
"Output file name" which might do what you want.

Martin


-
To unsubscribe, send email to [EMAIL PROTECTED]

-





-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Thanks, that is it, nice and simple.

RBS

-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 15:40
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:

> Now what do I do make it compile a dll called SQLite3VB.dll?

I think it defaults to the project name, but have a look at the Link tab 
in the Project|Settings dialog (Alt-F7) - there's an edit box titled 
"Output file name" which might do what you want.

Martin


-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Martin Jenkins]

RB Smissaert wrote:


Now what do I do make it compile a dll called SQLite3VB.dll?


I think it defaults to the project name, but have a look at the Link tab 
in the Project|Settings dialog (Alt-F7) - there's an edit box titled 
"Output file name" which might do what you want.


Martin

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Just one simple question:
I have a VC6++ project now that compiles a dll called SQLiteVB.dll
Now what do I do make it compile a dll called SQLite3VB.dll?
I can see no simple configuration setting for this. I could of course start
a new project, but that seems silly.
Thanks for any advice.

RBS


-Original Message-
From: RB Smissaert [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 14:31
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] compiling with VC++

Think I got this fixed now.
It simply was something I had overlooked to change:

//const char *sqlite3_libversion(void);
BSTR __stdcall sqlite3_libversion(void);

Lots of warnings (265) but no errors and a dll is produced, which I will try
now.

RBS

-Original Message-
From: RB Smissaert [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 13:47
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] compiling with VC++

OK, thanks a lot.

I think I have made a lot of progress, probably because of the different
source files you pointed me to.

I get one error though and that has to do with this bit of code:

/*
** The version of the library
*/
const char sqlite3_version[] = SQLITE_VERSION;
BSTR __stdcall sqlite3_libversion(void){ return SysAllocStringByteLen(
sqlite3_version,strlen( sqlite3_version) ); }
BSTR __stdcall sqlite3_libversion_number(void){ return
SQLITE_VERSION_NUMBER; }

The error originates from the second line of code and shows like this in the
build window:

c:\sqlite\sourcewin\main.c(33) : error C2373: 'sqlite3_libversion' :
redefinition; different type modifiers

No idea what to do about this.


RBS


-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 13:29
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:
> Thanks, will have a look at that.
> Do you know from experience that it will compile OK with VC6++?

I'm pretty sure I've compiled it with VC6++. I've been compiling on 
Debian and Solaris machines recently and have sort of lost track of 
building stuff on Windows. I tried upgrading to the current MS compilers 
but there seemed to be so many things that I didn't know I wanted that I 
think I gave up.

I'm having the same problems with installing the software for my phone. 
Been at it a couple of hours and so far it's changed my default email 
application, my default image viewer and my MP3 player and I still can't 
access the information I wanted off my phone. First and last Windows 
Smartphone I'll buy. It's "Smart" as in "Sting" rather than "Clever".

I'm going for a cup of tea and then I'll have a look and see if I can 
find some  VC6 project files for you. If I do I'll mail them straight to 
you rather than clutter up the list. If they work I suppose they could 
be uploaded somewhere.

Martin


-
To unsubscribe, send email to [EMAIL PROTECTED]

-





-
To unsubscribe, send email to [EMAIL PROTECTED]

-





-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

> which I will try now

And it works fine.

So the instructions at:
http://www.tannertech.net/sqlite3vb/index.htm
are fine to compile with VC6++ if you pick the right source files:
http://www.sqlite.org/download.html

and just ignore this bit:

We need to set our Module Definition File.

* Right click your project in the Solution Explorer and select
Properties.
* Select "All Configurations" from the Configuration drop down box.
(Important!)
* Select Configuration Properties -> Linker -> Input.
* Under "Module Definition File" enter "$(InputDir)sqlite3.def" without
the quotes. It should be located in the same folder in your project as your
SQLite source files.

Quite impressive to compile a real dll (as compared to a VB ActiveX dll).

Now will need to figure out if I can get some more function available in VB
than the ones I got now:

Private Declare Sub sqlite3_open Lib "SQLiteVB.dll" _
 (ByVal FileName As String, _
ByRef handle As Long)
Private Declare Sub sqlite3_close Lib "SQLiteVB.dll" _
 (ByVal DB_Handle As Long)
Private Declare Function sqlite3_last_insert_rowid _
Lib "SQLiteVB.dll" _
 (ByVal DB_Handle As Long) As Long
Private Declare Function sqlite3_changes _
Lib "SQLiteVB.dll" _
   (ByVal DB_Handle As Long) As Long
Private Declare Function sqlite_get_table _
Lib "SQLiteVB.dll" _
 (ByVal DB_Handle As Long, _
   ByVal SQLString As String, _
 ByRef ErrStr As String) As Variant()
Private Declare Function sqlite_libversion _
 Lib "SQLiteVB.dll" () As String
Private Declare Function number_of_rows_from_last_call _
  Lib "SQLiteVB.dll" () As Long


RBS

-Original Message-
From: RB Smissaert [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 14:31
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] compiling with VC++

Think I got this fixed now.
It simply was something I had overlooked to change:

//const char *sqlite3_libversion(void);
BSTR __stdcall sqlite3_libversion(void);

Lots of warnings (265) but no errors and a dll is produced, which I will try
now.

RBS

-Original Message-
From: RB Smissaert [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 13:47
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] compiling with VC++

OK, thanks a lot.

I think I have made a lot of progress, probably because of the different
source files you pointed me to.

I get one error though and that has to do with this bit of code:

/*
** The version of the library
*/
const char sqlite3_version[] = SQLITE_VERSION;
BSTR __stdcall sqlite3_libversion(void){ return SysAllocStringByteLen(
sqlite3_version,strlen( sqlite3_version) ); }
BSTR __stdcall sqlite3_libversion_number(void){ return
SQLITE_VERSION_NUMBER; }

The error originates from the second line of code and shows like this in the
build window:

c:\sqlite\sourcewin\main.c(33) : error C2373: 'sqlite3_libversion' :
redefinition; different type modifiers

No idea what to do about this.


RBS


-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 13:29
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:
> Thanks, will have a look at that.
> Do you know from experience that it will compile OK with VC6++?

I'm pretty sure I've compiled it with VC6++. I've been compiling on 
Debian and Solaris machines recently and have sort of lost track of 
building stuff on Windows. I tried upgrading to the current MS compilers 
but there seemed to be so many things that I didn't know I wanted that I 
think I gave up.

I'm having the same problems with installing the software for my phone. 
Been at it a couple of hours and so far it's changed my default email 
application, my default image viewer and my MP3 player and I still can't 
access the information I wanted off my phone. First and last Windows 
Smartphone I'll buy. It's "Smart" as in "Sting" rather than "Clever".

I'm going for a cup of tea and then I'll have a look and see if I can 
find some  VC6 project files for you. If I do I'll mail them straight to 
you rather than clutter up the list. If they work I suppose they could 
be uploaded somewhere.

Martin


-
To unsubscribe, send email to [EMAIL PROTECTED]

-





-
To unsubscribe, send email to [EMAIL PROTECTED]

-





-
To unsubscribe, send email to 

Re: [sqlite] SQLite - how to protect the data

[John Stanton]

You could use encryption like DES etc in your application.  Since sqlite 
is open source you could build encryption into the DB.  Since an Sqlite 
database is one file you can encrypt that file in the file system.


If those are too difficult, make a deal with Dr Hipp for his encrypted 
Sqlite.


mxs wrote:

Hi guys,

I am quite new here and quite new to SQLite. I am shocked how small and fast
this database is. So far I've been using MS Access for my little projects
and I cannot wait to replace it with SQLite.

Now, I have a question which I will have to deal with. One of the
application I work on contains data which have very high value. In another
words the whole value of the app is the database, rather than the front end.
If somebody makes a clone of the front end I don't care, but if somebody
copies the database and uses the data for his own front end that would be a
disaster. It is not a privacy issue, but rather the amount of effort put
into filling the database up. I used to use a kind of crypto ActiveX when
Access was used. It worked although slowed already not fastest database down
which showed during search and filter operations.

If anybody knows hot to ensure that the data is not readable without the
front end I would appreciate it.

I found a link talking about encryption, but this is not exactly affordable
for my type of project.
http://www.hwaci.com/sw/sqlite/prosupport.html#crypto


Thanks for any suggestions.

Cheers

Marek



-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Think I got this fixed now.
It simply was something I had overlooked to change:

//const char *sqlite3_libversion(void);
BSTR __stdcall sqlite3_libversion(void);

Lots of warnings (265) but no errors and a dll is produced, which I will try
now.

RBS

-Original Message-
From: RB Smissaert [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 13:47
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] compiling with VC++

OK, thanks a lot.

I think I have made a lot of progress, probably because of the different
source files you pointed me to.

I get one error though and that has to do with this bit of code:

/*
** The version of the library
*/
const char sqlite3_version[] = SQLITE_VERSION;
BSTR __stdcall sqlite3_libversion(void){ return SysAllocStringByteLen(
sqlite3_version,strlen( sqlite3_version) ); }
BSTR __stdcall sqlite3_libversion_number(void){ return
SQLITE_VERSION_NUMBER; }

The error originates from the second line of code and shows like this in the
build window:

c:\sqlite\sourcewin\main.c(33) : error C2373: 'sqlite3_libversion' :
redefinition; different type modifiers

No idea what to do about this.


RBS


-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 13:29
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:
> Thanks, will have a look at that.
> Do you know from experience that it will compile OK with VC6++?

I'm pretty sure I've compiled it with VC6++. I've been compiling on 
Debian and Solaris machines recently and have sort of lost track of 
building stuff on Windows. I tried upgrading to the current MS compilers 
but there seemed to be so many things that I didn't know I wanted that I 
think I gave up.

I'm having the same problems with installing the software for my phone. 
Been at it a couple of hours and so far it's changed my default email 
application, my default image viewer and my MP3 player and I still can't 
access the information I wanted off my phone. First and last Windows 
Smartphone I'll buy. It's "Smart" as in "Sting" rather than "Clever".

I'm going for a cup of tea and then I'll have a look and see if I can 
find some  VC6 project files for you. If I do I'll mail them straight to 
you rather than clutter up the list. If they work I suppose they could 
be uploaded somewhere.

Martin


-
To unsubscribe, send email to [EMAIL PROTECTED]

-





-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

OK, thanks a lot.

I think I have made a lot of progress, probably because of the different
source files you pointed me to.

I get one error though and that has to do with this bit of code:

/*
** The version of the library
*/
const char sqlite3_version[] = SQLITE_VERSION;
BSTR __stdcall sqlite3_libversion(void){ return SysAllocStringByteLen(
sqlite3_version,strlen( sqlite3_version) ); }
BSTR __stdcall sqlite3_libversion_number(void){ return
SQLITE_VERSION_NUMBER; }

The error originates from the second line of code and shows like this in the
build window:

c:\sqlite\sourcewin\main.c(33) : error C2373: 'sqlite3_libversion' :
redefinition; different type modifiers

No idea what to do about this.


RBS


-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 13:29
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:
> Thanks, will have a look at that.
> Do you know from experience that it will compile OK with VC6++?

I'm pretty sure I've compiled it with VC6++. I've been compiling on 
Debian and Solaris machines recently and have sort of lost track of 
building stuff on Windows. I tried upgrading to the current MS compilers 
but there seemed to be so many things that I didn't know I wanted that I 
think I gave up.

I'm having the same problems with installing the software for my phone. 
Been at it a couple of hours and so far it's changed my default email 
application, my default image viewer and my MP3 player and I still can't 
access the information I wanted off my phone. First and last Windows 
Smartphone I'll buy. It's "Smart" as in "Sting" rather than "Clever".

I'm going for a cup of tea and then I'll have a look and see if I can 
find some  VC6 project files for you. If I do I'll mail them straight to 
you rather than clutter up the list. If they work I suppose they could 
be uploaded somewhere.

Martin


-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Martin Jenkins]

RB Smissaert wrote:

Thanks, will have a look at that.
Do you know from experience that it will compile OK with VC6++?


I'm pretty sure I've compiled it with VC6++. I've been compiling on 
Debian and Solaris machines recently and have sort of lost track of 
building stuff on Windows. I tried upgrading to the current MS compilers 
but there seemed to be so many things that I didn't know I wanted that I 
think I gave up.


I'm having the same problems with installing the software for my phone. 
Been at it a couple of hours and so far it's changed my default email 
application, my default image viewer and my MP3 player and I still can't 
access the information I wanted off my phone. First and last Windows 
Smartphone I'll buy. It's "Smart" as in "Sting" rather than "Clever".


I'm going for a cup of tea and then I'll have a look and see if I can 
find some  VC6 project files for you. If I do I'll mail them straight to 
you rather than clutter up the list. If they work I suppose they could 
be uploaded somewhere.


Martin

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] Re: SQLite - how to protect the data

[Ulrich Telle]

Adriano schrieb:

> I'm in the same boat too.
> I've just found http://www.sqlcrypt.com/
> not tryed yet
> 
> i need something that can works either on pc or on windoes mobile
> devices

Since I was in need of encrypting my SQLite database, too, and could not 
afford a commercial solution I created my own SQLite encryption 
extension, based on experiences I gained developing encryption support 
for my wxWidgets component wxPdfDocument.

My SQLite encryption extension is written in C++ and should be 
compilable on any platform for which SQLite is available. The API is 
compatible with the commercial encryption solution offered by D.R. Hipp, 
(but not the encrypted database files, since I do not know the 
encryption algorithm used by D.R. Hipp). My algorithm is based on 
128-Bit-AES. The source code of the extension is distributed with the 
latest release (1.7.2) of wxSQLite3, my SQLite wrapper for wxWidgets:

http://sourceforge.net/project/showfiles.php?group_id=51305_id=45182_id=343361

Regards,

Ulrich

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

RE: [sqlite] compiling with VC++

[RB Smissaert]

Thanks, will have a look at that.
Do you know from experience that it will compile OK with VC6++?

RBS

-Original Message-
From: Martin Jenkins [mailto:[EMAIL PROTECTED] 
Sent: 24 February 2007 12:02
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] compiling with VC++

RB Smissaert wrote:
> Could anybody pass me step by step instructions to compile the source with
> MS VC++ ? I don't code or compile in C at all and only code in VB/VBA.

There a some instructions at:

http://www.sqlite.org/cvstrac/wiki?p=HowToCompile


and a zip file - sqlite-source-3_3_13.zip - containing preprocessed 
source for Windows users at:

http://www.sqlite.org/download.html

I don't know if that latter file contains the headers you want as I 
mostly work on Linux.

This is a bit of an FAQ so you might want to take a look through the 
mailing list archives. There's one at news.gmane.org.

Shout again if this didn't help. ;)

Martin




-
To unsubscribe, send email to [EMAIL PROTECTED]

-




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] compiling with VC++

[Martin Jenkins]

RB Smissaert wrote:

Could anybody pass me step by step instructions to compile the source with
MS VC++ ? I don't code or compile in C at all and only code in VB/VBA.


There a some instructions at:

http://www.sqlite.org/cvstrac/wiki?p=HowToCompile


and a zip file - sqlite-source-3_3_13.zip - containing preprocessed 
source for Windows users at:


http://www.sqlite.org/download.html

I don't know if that latter file contains the headers you want as I 
mostly work on Linux.


This is a bit of an FAQ so you might want to take a look through the 
mailing list archives. There's one at news.gmane.org.


Shout again if this didn't help. ;)

Martin



-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] compiling with VC++

[RB Smissaert]

Could anybody pass me step by step instructions to compile the source with
MS VC++ ? I don't code or compile in C at all and only code in VB/VBA.

I am following the tutorial by Todd Tanner:
http://www.tannertech.net/sqlite3vb/index.htm

But this is with Visual Studio Net and I am running in some problems.

For now I can see 2 trouble spots:
The tutorial talks about sqlite.h, but in the download I don't have that
file, although I have sqlite.h.in, which seems to have the code as described
in the tutorial.

Secondy at the end of the tutorial there is a change in the configuration
settings:

We need to set our Module Definition File.

* Right click your project in the Solution Explorer and select
Properties.
* Select "All Configurations" from the Configuration drop down box.
(Important!)
* Select Configuration Properties -> Linker -> Input.
* Under "Module Definition File" enter "$(InputDir)sqlite3.def" without
the quotes. It should be located in the same folder in your project as your
SQLite source files.


Not sure how to do the same in VC++

I have tried compiling after altering the extension from sqlite.h.in to
sqlite.h and obviously this is completely wrong.
When I compile I get this error the most:

fatal error C1083: Cannot open include file: 'sqliteInt.h': No such file or
directory


Thanks for any advice.



RBS




-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] SQLite - how to protect the data

[Adriano]

I'm in the same boat too.
I've just found http://www.sqlcrypt.com/
not tryed yet

i need something that can works either on pc or on windoes mobile devices
thanks
Adriano

-
To unsubscribe, send email to [EMAIL PROTECTED]
-