• Welcome to SQLitening Support Forum.
 

News:

Welcome to the SQLitening support forums!

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Steve Pardoe

#1
Rolf,

Yes that is an option but not an elegant one I think. I am not a DB expert by any means but I know that NULL should be put where there is nothing (in an ideal world).

Naturally I can achieve this using the old fashioned insert statement syntax, so I may need to go that way.

Thanks again,

Steve.
#2
Rolf,

Thanks very much for that. Have never really been aware of the difference of those two before...

Any ideas about the appropriate approach for my insert of null values at all ?

Thanks in advance,

Steve.
#3
Hi,

I have been having some problems with slBuildInsertOrUpdate - with values getting into my DB as text with a leading space. Finally realised that the STR$ function inserts a leading space if the value is >= 0. I had no idea about this all this time, so that is here in case anyone else looks for it..

On to my second question - I want to perform an insert of a value if a condition is met but nothing if it is not met, so thebelow seemed logical:

IIF$(DOMASKSCOUNT >= 1, LTRIM$(STR$(PRICELEVEL)), $NUL) + $NUL

The above forms part of my value string for slBuildInsertOrUpdate. I take it that (as the routine parses based on $NUL), it is not specifiable as my 'negative' choice selection in the above. In this case, the alternative is "" ?

Am I overlooking something here or not ? The 'correct' value for the field should be NULL and not any 'actual' value as it were right ?

Thoughts and opinions most welcome..

Steve.
#4
Jim,

SQLite does not natively come with encryption - that is provided by SQLitening..

Steve.
#5
Rolf,

Thanks for the response but neither of those posts nor my searching on the forum (which I had already completed) gave me any insight as to the mode of encryption nor, therefore inferred, the need or not for a vector or not.
Likewise I did a search of the source and couldn't find anything mentioned...

If anyone knows more then by all means let me know. Thanks in advance,

Steve.
#6
Hi,

I am using the built in encryption in SQLitening and want a little high-level guidance on the encryption standard that is used. You see I have a Linux based site that has an MySql DB and I want to explore the possibility of having the server create an SQLite DB with the fields encrypted. On the face of it, this is entirely possible (there is an SQLite class out there), so my question becomes, what 'specification' of the encryption is needed to match that of my application which (would) use SQLitening for the desktop decryption ?

I know very little about encryption but from the below link:

http://www.coderelic.com/examples/AES_Encryption_Example.php

There are choices about which AES  encryption mode to use as many of them require an Initialization Vector.

Any pointers about which method matches what SQLitening is using would be appreciated and apologies in advance for my lack of crypt-comprehension !

Steve.
#7
Bern,

Yes, that's what I thought. I am using the 'longer and less elegant' route as we speak. It is a shame as 13,10 is such a common need.

Steve.
#8
Hi Guys,

A quick question about slSelStr - presumably I can only use this and separate records with 13,10 if I modify the SQLitening source code to parse out more than one sep characters. Is this correct ?

Thanks for the great product by the way !

Steve.