[sqlite] [ANN] DragonDB - MVB Edition 1.1 Released

[John Oliva]

Danic Systems releases DragonDB - MVB Edition 1.1 for AppForge MobileVB.
 
EAST BRUNSWICK, NJ, USA (December 16, 2005) -- Danic Systems, LLC announced
today availability of an updated version of its DragonDB - MVB Edition
product.
 
Release 1.1 is a free update for those with an existing DragonDB - MVB
Edition license.
 
*** Whats New ***
 
* Support for SQLite 3.2.7
  - many new SQL language features
  - improved transaction control
  - improved performance of indexed queries
  - ability to modify structure of existing tables
  - minor bug fixes
 
* New licensing options & support policy
  - Commercial license
  - Non-commercial license
  - Standard support is free for licensed products.
  - High priority support is offered through fee based support packages.
 
*** About DragonDB - MVB Edition ***
 
DragonDB - MVB Edition is an SQL database engine and software development
toolkit for creating Microsoft Pocket PC and Smartphone database
applications using AppForge MobileVB (version 3.2 or later).  DragonDB is
built upon SQLite3 so its databases are portable to all platforms and
applications which support the SQLite3 database format.
 
*** Pricing & Availability ***
 
DragonDB - MVB Edition 1.1 is available now from the Danic Systems website
at   http://www.danicsystems.com.
 
The commercial version is $179 per development license without any royalties
for your deployed applications. The non-commercial version is $20 and is
strictly for non-commercial use. Volume discounts are available. A 30 day
free trial version is also available.
 
Priority support packages may be purchased starting from $45.
 
*** About Danic Systems, LLC ***
 
Danic Systems, LLC is a privately held software company providing
applications and tools for the Microsoft Windows desktop and mobile
operating systems.  Our specialty is in providing applications and tools
which bridge the power of the desktop computer with the flexibility offered
by mobile devices.
 
*** Contact Information ***
 
Company:  Danic Systems, LLC
E-mail: [EMAIL PROTECTED]
Website:    http://www.danicsystems.com

RE: [sqlite] equivalent of linked tables in sqlite ?

[John Oliva]

You might want to look at using AppForge (www.appforge.com) which takes a
slightly restricted version of VB6, VB.NET and C# and can produce output for
many handheld devices (including PPC).  Also, you can program in .NET for
the desktop and .NET compact framework for the Pocket PC.

Regards,
John Oliva
www.danicsystems.com

> I hope to use the same (type) language for desktop and ppc 
> programmation. The most likely candidate seems evc++ & vc++. 
> (I still have to learn it) even more so because the intended 
> tool calls for lowlevel access to the serial port on the 
> pocketpc (Dallas Ibutton interfacing).
> 
> I'm however concerned about the database connectivity. On a 
> previous attempt, I bought Sybase PocketBuilder on sybase's 
> reputation of being proficient at different db formats. Only 
> to find out dbase, foxpro support and such was scrapped from 
> pocketbuilder.
> 
> glenn

[sqlite] ANN: DragonDB - MVB Edition 1.0 for AppForge MobileVB

[John Oliva]

Danic Systems Releases DragonDB - MVB Edition 1.0 for AppForge MobileVB.
 
East Brunswick, NJ, USA (August 12, 2005) -- Danic Systems, LLC
announced today that it is shipping DragonDB - MVB Edition 1.0 for
AppForge MobileVB.  DragonDB - MVB Edition is an SQL database engine and
software development toolkit for creating Microsoft Pocket PC and
Smartphone database applications using AppForge MobileVB.
 
DragonDB - MVB Edition works with AppForge MobileVB (version 3.2 or
later) for producing database applications which run on Microsoft Pocket
PC and Smartphone devices running Windows Mobile 2003 (or later
version).
 

Major Benefits
 
* Affordable - No royalty fees when deploying your applications.
* Rapid Development - Easy to use API with a full featured SQL
relational database engine. 
* Trivial deployment - Simply include a couple of shared libraries with
your application.
* Trivial management - Zero-configuration. No setup or administration
needed.
* Small footprint - Approximately 300KB for either Pocket PC or
Smartphone platforms.
* High performance - Efficient/optimized design yields extremely fast
queries and other database operations.
* Portable - A database may simply be copied from one platform to
another (binary compatibility). 
* Lifetime updates - Updates are free for your licensed major version
number.
 
Major Features
 
* Powerful SQL relational database management engine embedded in
AppForge MobileVB compliant fuser.
* Complete and well documented API.
* VB6 project template for creating DragonDB powered AppForge MobileVB
applications.
* Royalty-free MobileVB compliant fusers for MS Pocket PC and Smartphone
target devices.
* Design time Win32 fuser for developing your DragonDB applications.
* Example programs
* Bundled with useful third-party tools to accelerate your development.
 
 
About DragonDB - MVB Edition
 
DragonDB - MVB Edition provides an SQL database engine for AppForge
MobileVB which is affordable, powerful and portable.  DragonDB is built
upon SQLite3 which is a popular database engine included as a core
component in Apple's Mac OS X and as the native DB for the PHP scripting
language. 
 

Availability
 
DragonDB - MVB Edition 1.0 is available now from the Danic Systems
website at http://www.danicsystems.com.
 
The full version is available at an introductory price of $299 per
development license without any royalties for your deployed
applications. Volume discounts are available. A 30 day free trial
version is also available.
 

About Danic Systems, LLC
 
Danic Systems, LLC is a privately held software company providing
applications and tools for the Microsoft Windows desktop and mobile
operating systems.  Our specialty is in providing applications and tools
which bridge the power of the desktop computer with the flexibility
offered by mobile devices.
 
Contact Information
 
Company Name: Danic Systems, LLC
E-mail: [EMAIL PROTECTED]
Website: http://www.danicsystems.com
 
 

Re: [sqlite] database replication

[John Oliva]

I am interested.

John Oliva

> I just finished a c++ program to replicate a database while it's in use.
> I have tested it on a version 3 database under windows.
>
> It creates a duplicate database with the same schema as the source
> database, then in a loop it locks the database, copies a table,
> and unlocks the database.
>
> The database will be write locked for however long
> it takes for each table to be copied. If you're interested
> in the source code I will be happy to release it.
>
>
>
>
>
> __
> Do you Yahoo!?
> Yahoo! Small Business - Try our new resources site!
> http://smallbusiness.yahoo.com/resources/

Re: [sqlite] SQLite for Windows CE

[John Oliva]

I am also interested in synchronizing SQLite databases.  As far as I am
aware, there is no support in the SQLite code for the tasks required to
synchronize multiple databases.  You would need meta-data indicating
whether data has been added/deleted/modified along with either timestamps
or update numbering in order to reconcile the changes and possibly
conflicts between multiple databases.

You might want to google for the techniques employed in synchronizing
PalmOS PDB files between the PDA and host. It provides table based
synchronization, and seems to be a robust and efficient solution between a
pair of databases.

John Oliva

> Does anyone know how to synchronize the data on the WinCE device with a
> database on a server computer?  I'm just testing the feasibility of using
> SQLite for our projects that run under wireless  WinCE 3.0 device.  The
> primary database is a Sybase database server running on Sun workstations.
> The WinCE SQLite would be a subset of the Sybase database.  My conceptual
> problem is if we do that, how could we keep the two databases
> synchronized?
> The wireless computers will not always be within radio frequency (RF) of
> the
> database, so a large part of its work is off-line from the main Sybase
> server.
>
> Thanks for any hints or links you may be able to provide.
>
> Mel Stober
>

Re: [sqlite] WinCE port

[John Oliva]

Nuno,

Is this port freely available?  I presume you can use it to build the
textfixture for running on the PPC target.

Thanks,
John Oliva

> Stober, Mel, dando pulos de alegria, escreveu :
>> I created an MFC for WinCE version of shell.c to make it easier to enter
>> text and see error messages.  The problem I have is that insert SQL
>> statement doesn't seem to work. Using the examples from here:
>> http://bs2000.fujitsu-siemens.com/download/Goodies/SMAWPlus/SMAWPsqli/html/s
>> qlite.1.html  it doesn't like the exalamation point inside quoted
>> strings.
>
> I advise you to check your code as the example is pretty common.
>
> As an aside, Paul Sokolovsky succeeded in porting TCL 8.4.6 into an iPaq
> 4150, using an arm-wince-gcc port.
>
> With that it achieved running the full test suite on sqlite 2.8.13 and
> all relevant single-threaded tests passed.
>
> I'm very grateful to him as I'm more confident now on the status of the
> port :)
>
> This unfortunely doesn't apply to 3.0.x, but I think it's a good sign :)
>
> Best regards,
> ~Nuno Lucas
>
>
>

Re: [sqlite] SQLite DB synchronization

[John Oliva]

I haven't worked out a synchronization scheme yet. One possibility is to
model it on how the Palm PDB databases are synchronized.  They keep
meta-data for each row indicating whether the data is dirty, new, has been
deleted, etc. This is optimized for a one-to-one pairing between two
databases.  A more complex process would be required to support
synchronization between members of a set of databases which all may be
synced.

Do you support uni-directional and bi-directional synchronization?

You mentioned that you create a hash on the contents of the row to produce
a GUID.  I presume this is only done when you first create the row,
otherwise any changes to the row data would change the GUID.  Correct?

John

> John Oliva wrote:
>
>>Are any of you performing synchronization between multiple SQLite DBs?
>>What tools or techniques are you using?
>>
>>Thanks,
>>John Oliva
>>
>>
> That's something I'd be interested in as well.  At the moment, we are
> using a system where each table to be synchronized has at least the
> following fields:
>
> guid (a global unique identifier, composed of a md5 hash of all the
> contained data in the row plus a couple other random bits)
> date_added
> date_modified
>
> Using these, we can sync updates and inserts across database instances.
> Unfortunately, there doesn't seem to be a simple method of deleting a
> record and then syncing.
> This is obviously a pretty simplistic way to do this, so any other
> suggestions I would find helpful.
>
> John LeSueur
>

[sqlite] SQLite DB synchronization

[John Oliva]

Are any of you performing synchronization between multiple SQLite DBs? 
What tools or techniques are you using?

Thanks,
John Oliva

Re: [sqlite] SQLite versions in CVS

[John Oliva]

To answer my own question for other's reference, you can view the SQLite
CVStrac timeline and look at the release milestones.  They have the date
and time for each release.

John

> Thanks.  What file should I reference to get the data/time for past
> releases?
>
> John
>

Re: [sqlite] SQLite versions in CVS

[John Oliva]

Thanks.  What file should I reference to get the data/time for past
releases?
 
John