[sqlite] SqliteDog released

[Sqlite Dog]

Hi,

we are happy to announce a final release of SqliteDog: a modern SQLite
database manager.

http://sqlitedog.com



-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] SqliteDog released

[Sqlite Dog]

Thank you. We'll improve that.


2013/10/23 Donald Griggs <dfgri...@gmail.com>

> Congratulations to the team!
>
> Just a note in the spirit of helpfulness:
>  Note that one of the major headings on the website is misspelled
> "Purhase."There are numerous grammar errors in the website text.  I
> suggest you may want to have a native English speaker proof it.
>
>
> On Wed, Oct 23, 2013 at 12:21 PM, Sqlite Dog <sqlite...@gmail.com> wrote:
>
> > Hi,
> >
> > we are happy to announce a final release of SqliteDog: a modern SQLite
> > database manager.
> >
> > http://sqlitedog.com
> >
> >
> >
> > --
> > Regards,
> > SqliteDog support team
> > ___
> > sqlite-users mailing list
> > sqlite-users@sqlite.org
> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> >
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] How to fix sqlite issue

[Sqlite Dog]

Hi,

perhaps, this can help:

1) download zip with latest SQLite DLL from http://sqlite.org/download.html;
2) unzip it to c:\temp;
3) copy c:\temp\sqlite3.dll to Windows\System32 folder;
4) if there is already sqlite3.dll in Windows\System32 and it's locked,
overwrite it with InUse.exe (http://support.microsoft.com/kb/228930);
5) reboot;
6) if some software is still complaining, delete sqlite3.dll from app's
folder.

Since SQLite is (mostly :) backwards compatible these steps will force
wrongful app to use latest sqlite3.dll in system32 instead of the one it
was installed with.

I'm not sure if this would definitely work, but I would give it a try. The
problem can arise if app uses some specifically built DLL that's not
compatible in some way with the default one.

And it's not clear how to perform step 6 - find complaining app's folder.



2013/11/12 Norma Richey 

> Hello,
>
>
>
> I am having problem with an error that is appearing whenever I startup my
> computer.  This happened when I downloaded the latest update of iTunes.
>
>
>
> The issue is as follows:
>
> The procedure entry point sqlite3-wal-checkpoint could not be located in
> the
> dynamic library SQLite3.dll.
>
>
>
> I previously had an issue with the AppleSyncNotifier.exe Entry Point Not
> Found but it was a little different and I was able to fix it.  I tried the
> same fix but it did not work.  I am not real tech savvy so if you can
> direct
> me that would be great.
>
>
>
> Any assistance would be most appreciated.  Thanks in advance.
>
>
>
> Norma Richey
>
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Is there available sample "featured" SQLite database file?

[Sqlite Dog]

Hi,

we are developing (yet another :) SQLite manager.

I'm wondering is there available sample "feature-tight" "limit-striking"
SQLite database (or SQL script)  for GUI manager testing purposes?

Like:
- identifier names contains spaces, UNICODE chars, are surrounded by [], by
"" or not surrounded;
- some tables contains really lots of columns, some have only one;
- columns have all meaninful data types, all resonable default values, etc;
- some tables have lots of triggers and indices;
- all kinds of foreign key constraints;
- a pack of views;
- tables are filled with some testing data, some contains lots of rows,
some are empty, etc;

It would be great to have one.

-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Is there available sample "featured" SQLite database file?

[Sqlite Dog]

> Here is your starter schema (and perfectly valid):

>  create table ""("" "");


Thanks for this snippet! Actually found a bug :)




> For performance testing this could be helpful with the --dump-sql arg:
>  https://code.google.com/p/apsw/source/browse/tools/speedtest.py


Well, performance is not an issue... What I'm looking for is a database
with all sorts of database objects available.

Perhaps, SQLite developers already have one for their own purporse and
would be able to share it.


-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] A few questions about SQLite Encryption Extension

[Sqlite Dog]

Hi,

documentation on SEE (http://www.hwaci.com/sw/sqlite/see.html) states that

"You can ship as many compiled, binary copies of SQLite with your
commercial product as long as each copy is attached to your product in such
a way that it cannot be separated from your product. Normally this means
that you should statically link SEE with your product, thought exceptions
to this rule can be made as circumstances require."

Our database manager is developed using Delphi (Pascal). Thus it is not
possible to statically link SQLite library, SQLite.dll is used. Is there
some other way to support SEE in our project?

SEE supports several various encryption algorithms. If a database is
already encrypted does it automatically choose needed algorithm? How to
specify algorithm for a new database if a version of SEE is used which
supports all of them? Or is it always using most "powerful" one (AES-256)?

Thank you.

--
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] A few questions about SQLite Encryption Extension

[Sqlite Dog]

That's interesting. What about pas file with function declarations to
SQLite API? Should it be modified somehow?


2013/7/19 kyan <alfasud...@gmail.com>

> On Fri, Jul 19, 2013 at 10:21 AM, Sqlite Dog <sqlite...@gmail.com> wrote:
>
> >
> > Our database manager is developed using Delphi (Pascal). Thus it is not
> > possible to statically link SQLite library, SQLite.dll is used. Is there
> > some other way to support SEE in our project?
> >
>
> It is possible to compile the SQLite amalgamation with Embarcadero CBuilder
> and statically link the object file in a Delphi program using the $L
> directive; I have
> successfully
> done this
> with Delphi XE
> . So
> -although I haven't tried it-
> I suppose it is possible to do the same with SEE since it is open-source.
>
> --
> Constantine Yannakopoulos
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] A few questions about SQLite Encryption Extension

[Sqlite Dog]

2013/7/19 Richard Hipp <d...@sqlite.org>

> On Fri, Jul 19, 2013 at 3:21 AM, Sqlite Dog <sqlite...@gmail.com> wrote:
>
> >
> > Our database manager is developed using Delphi (Pascal). Thus it is not
> > possible to statically link SQLite library, SQLite.dll is used. Is there
> > some other way to support SEE in our project?
> >
>
> Yes.  You can ship it as a DLL and use a special pragma to enable the
> encryption feature.  We ask that you rename the DLL to something that does
> not contain the words "SQLite" or "SEE" or anything similar, to disguise
> its purpose.
>
>
OK


>
>
> >
> > SEE supports several various encryption algorithms. If a database is
> > already encrypted does it automatically choose needed algorithm? How to
> > specify algorithm for a new database if a version of SEE is used which
> > supports all of them? Or is it always using most "powerful" one
> (AES-256)?
> >
>
> There is no way to detect which encryption algorithm is used.  Indeed, the
> encryption is so thorough that there is no way to tell whether or not the
> file you are trying to open is an encrypted database file or just a file of
> white noise.
>


> The default algorithm is the fastest algorithm (AES-128).  I suggest you
> stick to that one algorithm unless you have a compelling reason to use
> another.  That way, you never need to worry which algorithm is being used.
>


Suppose there are two databases, one is RC-4 encrypted and the other is
AES-256 encrypted.
What happens on open? SEE will use default algorithm and fail? Or it will
try all algorithms in cycle?





> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] A few questions about SQLite Encryption Extension

[Sqlite Dog]

2013/7/19 Ralf Junker <ralfjun...@gmx.de>

> On 19.07.2013 09:21, Sqlite Dog wrote:
>
> > Our database manager is developed using Delphi (Pascal). Thus it is
> > not possible to statically link SQLite library, SQLite.dll is used.
> > Is there some other way to support SEE in our project?
>
> You have two options:
>
> * Create your own sqlite.dll and compile SEE into it.
>

The question was - is it against the rules or not.


>
> * Statically link SQLite to your Delphi application. My DISQLite3
>   enables you to do just that and has numerous extensions: One is a
>   custom encryption algorithm. This is not compatible with SEE,
>   but if you like I can replace it with your original SEE code for you.
>
>   http://www.yunqa.de/delphi/doku.php/products/sqlite3/index


Is it a pascal wrapper around SQLite or something bigger?



>
>
> Ralf
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] A few questions about SQLite Encryption Extension

[Sqlite Dog]

2013/7/19 RSmith <rsm...@rsweb.co.za>

> Being a Delphi Developer (mostly) and using SQLite quite often, I can tell
> you some things about it:
>
> You can easily wrap an SQLite DLL in Delphi, there are many free
> implementations of this, if you dont have one, send me a mail and I will
> supply one. SEE will work as easily and I don't know of any restriction
> about it being used as a DLL, excepting to disguise it for obvious reasons.
> (not least among which, the security of your own system).
>

We already have a wrapper on SQLite.dll (otherwise we won't be able to
develop a SQLite database manager :) It's a .pas file with function calls
declared like:

...
function sqlite3_open_v2(const Filename: PAnsiChar; var Base: PSQLite3;
Flags: Integer; const Vfs: PAnsiChar = nil): Integer; cdecl; external
'sqlite3.dll';
...

It just wasn't clear how can we use SEE in this case.


>
> Further to this, DISQLite works really well as a native implementation in
> specifically Delphi, and will work very well for your purpose. It is
> however commercial so there is a cost consideration. (Yes it has a
> free-for-personal-use option, but any form of commercial application needs
> the commercial version). The only possible disadvantage I can level at it
> is that to use new adaptations of the SQLite system requires a recompile
> and update as opposed to just shipping another dll - but then if the dll
> supports new API calls, much the same is true. If security is a concern and
> it is a wholly Delphi-integrated product, I would suggest going with
> DISQLite if feasible.
>

I'm unsure about advantages of using DISQLite vs calling directly
SQLite.dll.

The main advantage is statically linking but we'll try to manage it via
compiling amalgamation to .obj and linking.

As for performance. There can't be a significant difference between these
solutions, in my opinion. 99% of the time will be spent inside SQLite.

Thanks, anyway. We'll give it a try.



>
> Lastly, it seems that either you wish to use different forms of
> encryptions to further subterfuge or obscure database content, or that you
> expect to be needing to open datasets with hitherto unknown encryptions. if
> it is the former, I can honestly say it is not needed, just use whatever
> you like, most of the supported encryptions have ratings way above military
> specification when using proper keys etc. If it is the latter case, you
> can't open Databases of which you don't know exactly the encryption and
> keys... there is no way to do this, else the whole encryption racket would
> be rather useless.


I guess you're right.



>
>
>
>
> On 2013/07/19 15:52, Ralf Junker wrote:
>
>> On 19.07.2013 15:27, Sqlite Dog wrote:
>>
>>  * Statically link SQLite to your Delphi application. My DISQLite3
>>>>enables you to do just that and has numerous extensions: One is a
>>>>custom encryption algorithm. This is not compatible with SEE,
>>>>but if you like I can replace it with your original SEE code for you.
>>>>
>>>>
>>>> http://www.yunqa.de/delphi/**doku.php/products/sqlite3/**index<http://www.yunqa.de/delphi/doku.php/products/sqlite3/index>
>>>>
>>> Is it a pascal wrapper around SQLite or something bigger?
>>>
>> DISQLite3 is the only Delphi product which includes the _complete_
>> SQLite API, AFAIK. Using register calling conventions and the Delphi
>> memory manager, DISQLite3 surprised many users to perform noticeably
>> faster than other implementations. Features include:
>>
> etc...
>
>
>
>
> __**_
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users>
>



-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] A few questions about SQLite Encryption Extension

[Sqlite Dog]

OK. Thank you.


2013/7/19 Richard Hipp <d...@sqlite.org>

> On Fri, Jul 19, 2013 at 9:20 AM, Sqlite Dog <sqlite...@gmail.com> wrote:
>
> > >
> > > There is no way to detect which encryption algorithm is used.  Indeed,
> > the
> > > encryption is so thorough that there is no way to tell whether or not
> the
> > > file you are trying to open is an encrypted database file or just a
> file
> > of
> > > white noise.
> > >
> >
> >
> > > The default algorithm is the fastest algorithm (AES-128).  I suggest
> you
> > > stick to that one algorithm unless you have a compelling reason to use
> > > another.  That way, you never need to worry which algorithm is being
> > used.
> > >
> >
> >
> > Suppose there are two databases, one is RC-4 encrypted and the other is
> > AES-256 encrypted.
> > What happens on open? SEE will use default algorithm and fail? Or it will
> > try all algorithms in cycle?
> >
>
> It will use the default algorithm and succeed.  But then later when you try
> to query the database you'll get back an SQLITE_CORRUPT error.
>
> --
> D. Richard Hipp
> d...@sqlite.org
> ___
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] How to detect full table scan?

[Sqlite Dog]

What is a best way to detect that query does full table scan? Considering
this (from http://www.sqlite.org/eqp.html ):

"Warning: The data returned by the EXPLAIN QUERY PLAN command is intended
for interactive debugging only. It may change dramatically between SQLite
releases. Applications should not depend on the results of an EXPLAIN QUERY
PLAN command."

Is it enough (and reliable) to search detail column of EXPLAIN QUERY PLAN
for "SCAN TABLE%" and (if found) presume that query does full scan?

The problem. We have a very large table with a lot of quering. So we came
along with 4 complex covering indices and want to prohibit queries that
does not supply enough values to avoid full scanning.


--
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] How to detect full table scan?

[Sqlite Dog]

We are using SQLite 3.7.17



2013/8/13 Sqlite Dog <sqlite...@gmail.com>

> What is a best way to detect that query does full table scan? Considering
> this (from http://www.sqlite.org/eqp.html ):
>
> "Warning: The data returned by the EXPLAIN QUERY PLAN command is intended
> for interactive debugging only. It may change dramatically between SQLite
> releases. Applications should not depend on the results of an EXPLAIN QUERY
> PLAN command."
>
> Is it enough (and reliable) to search detail column of EXPLAIN QUERY PLAN
> for "SCAN TABLE%" and (if found) presume that query does full scan?
>
> The problem. We have a very large table with a lot of quering. So we came
> along with 4 complex covering indices and want to prohibit queries that
> does not supply enough values to avoid full scanning.
>
>
> --
> Regards,
> SqliteDog support team
>



-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Trigger SQL and database schema

[Sqlite Dog]

Hi,

seems like SQLite is not checking trigger SQL for invalid column names
until execution? Is there a way to force this check?

The problem: trying to find out which indices, triggers and views depend on
particular column. We can recreate table without this column and recompile
indices, triggers and views. The ones that don't recompile, perhaps, depend
on this column.

This works for indices and views but not for triggers that ignores schema
until executed.

-- 
Regards,
SqliteDog support team
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users