[AccessD] Basic Question (Probably) that I just don't know

Stuart McLachlan stuart at lexacorp.com.pg
Mon Sep 26 01:42:47 CDT 2016


Hi Doug,

"High concurrency"  here means multiple threads or processes on the same machine 
accessing the datafile.     

See the bits on that page that metion client/server for multi-user considerations.  Not optimal.

 So no, I've never developed a multi-user SQLite application and have no intention of ever 
doing so.' 

But if you really want or need to work with SQLite data files in client/server mode, you could 
check out SQLitening (developed by some very good PowerBASIC programmers)


SQLitening Database System

SQLitening is a client/server implementation of the very popular SQLite database.

SQLitening is a programmer's library in standard Win32 DLL form. It is installed as a 
standard Windows Service. In addition to client/server mode, the library allows the 
programmer to also access SQLite databases in local mode. In either mode (local or 
client/server), the database is extremely fast and robust.

Installation is a breeze - you simply copy a couple of DLL's to the folder where your 
application resides. If you work in client/server mode, you create a folder on your server and 
start the SQLitening Windows Service from the Administration program. You may need to 
modify the standard configuration text file to set permissions and port numbers/host names. 
Simple.

Download via the sqlitening support site. Check it out at:  http://www.sqlitening.com


On 25 Sep 2016 at 22:58, Doug Steele wrote:

> Hi Stuart:
> 
> I was under the impression that SQLite couldn't be used as the BE for
> multi-user applications, but that web page just says it shouldn't be
> used for 'high concurrency' applications.  None of my MS Access client
> usage could ever be considered high concurrency (one or two people
> entering orders while talking on the phone...). Have you any
> experience with SQLite multi-user BEs?
> 
> Doug
> 
> On Sun, Sep 25, 2016 at 10:39 PM, Stuart McLachlan
> <stuart at lexacorp.com.pg> wrote:
> 
> > That sums it up very well.   It does have a lot of uses.
> >
> > On 25 Sep 2016 at 22:10, Doug Steele wrote:
> >
> > > By coincidence, this just came up on HackerNews:
> > >
> > > https://sqlite.org/whentouse.html
> > >
> > > Doug
> > >
> > > On Sat, Sep 24, 2016 at 4:43 AM, Stuart McLachlan
> > > <stuart at lexacorp.com.pg> wrote:
> > >
> > > > Oh yes, I forgot to mention triggers and in-memory databases  :)
> > > >
> > > >
> > > > On 24 Sep 2016 at 21:38, Stuart McLachlan wrote:
> > > >
> > > > > I agree it's not a good alternative for multi user systems,
> > > > > but SQLite is an excellent solution for  single user
> > > > > applications. There are reasons why it is so ubiquitous.
> > > > >
> > > > > It's free.  :)
> > > > >
> > > > > The same database file is usable on many platforms including
> > > > > Windows, Linux,Android and iOS.
> > > > >
> > > > > It's fast, lightweight and versatile.
> > > > >
> > > > > For Windows, it's just one native 500KB DLL and no
> > > > > dependencies.
> > > > >
> > > > > While it doesn't have a huge range of dataypes, there's not
> > > > > much that you can't do with a 8 bytes integers and floats
> > > > > (twice the size that Access offers) and  a default maximum
> > > > > size for text  of 1 billion characters (try indexinga field of
> > > > >  more than 255 characters in Access), and the same size of
> > > > > BLOBs.  There are plenty of built in functions for Date
> > > > > manipulation that make the use of a dedicated Date/Time
> > > > > datatypes unnecessary  including UnixTime (which is a real
> > > > > PITA to handle in Access).
> > > > >
> > > > > You're right that many (including me) use it because we "don't
> > > > > know any better".  That's because in its niche, there is no
> > > > > better.
> > > > >
> > > > > :)
> > > > >
> > > > >
> > > > >
> > > > > On 24 Sep 2016 at 8:35, Gustav Brock wrote:
> > > > >
> > > > > > Hi Arthur
> > > > > >
> > > > > > I can't add much to the comments already posted, except for
> > > > > > one thing: SQLite is certainly not an alternative for an
> > > > > > accdb or any other decent database as SQLite is severely
> > > > > > limited regarding data types. In fact, I think why so many
> > > > > > use it, is only because they just don't know better.
> > > > > >
> > > > >
> > > > > --
> > > > > AccessD mailing list
> > > > > AccessD at databaseadvisors.com
> > > > > http://databaseadvisors.com/mailman/listinfo/accessd
> > > > > Website: http://www.databaseadvisors.com
> > > > >
> > > >
> > > >
> > > > --
> > > > AccessD mailing list
> > > > AccessD at databaseadvisors.com
> > > > http://databaseadvisors.com/mailman/listinfo/accessd
> > > > Website: http://www.databaseadvisors.com
> > > >
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > http://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> >
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 




More information about the AccessD mailing list