• Welcome, Guest. Please login.
November 28, 2020, 06:59:23 PM


Welcome to the SQLitening support forums!

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.

Topics - Bern Ertl

Assuming the client application does not attempt to write any local data, is the SQLitening server Vista compatible?  Are there any special installation or set-up rules required for the SQLitening server to work nicely with Vista?
You've got Questions? We've got Answers! / error handling
November 21, 2008, 06:46:39 PM
Am I correct in assuming that SQLitening functions may return any of the SQLitening or SQLite error codes (-19 to 101)?

If so, would it also be correct to say that the following error codes represent situations where it might be possible to retry the command successfully (pending a change in conditions):

    -8 = Access denied
   -18 = Error sending or receiving message"
     3 = Access permission denied
     5 = The database file is locked
     6 = A table in the database is locked
    10 = Some kind of disk I/O error occurred
    15 = NOT USED. Database lock protocol error
    23 = Authorization denied

I'm not sure what these errors represent:
   100 = sqlite_step() has another row ready
   101 = sqlite_step() has finished executing
I see global return errors flag referenced a lot in the function descriptions in the SQLitening.TXT file.  What does this mean?
You've got Questions? We've got Answers! / Exits
November 18, 2008, 04:46:30 PM
Fred, I'm not sure how to create the "exits" as you call them without modifying the source for the server (causing additional work in the future to reconcile with any updates), so I am wondering if you might adapt something like this in a future release:

'============================<[ Globals ]>=============================
GLOBAL glFlags AS LONG                       'General purpose flags
GLOBAL glLogFileNumber AS LONG               'File number for the log

'=========================<[ Exits File ]>=========================
#INCLUDE "Exitmacros.inc"


'========================<[ Connection Main ]>=========================
   ' Close Tcp and log it
   TCP CLOSE llTcpFileNumber
   IF (llFlags AND &H01) AND (glFlags AND %gbfLogConnDcon) THEN LogIt "Dcon #" & FORMAT$(llTcpFileNumber) & "  " & IIF$(ERR = 57 OR ERR = 0, "", "Unknown Reason")

   'Call an Exit Macro


Quote'  ==========================================================================
'  |                                                                        |
'  | SQLitening Server - Exit Macros                                        |
'  |                                                                        |
'  ==========================================================================

MACRO mDisconnected
   'Put exit code here
I thought I'd create a new discussion thread to focus specifically on this issue (as originally touched upon here).

I want to build a log-in system to manage access in accordance with licensing restrictions.  There will be a db/table containing licensing information (# of allowed concurrent users/connections).  There will be a separate table of user accounts (with designated access levels).  The licensing restrictions only affect some of the user accounts (the ones with appropriate access levels).

Building a log-in system is not really a problem.  The client application can update the status of users who log in. My question is how to best handle dropped connections (auto-log outs)?

I'm guessing that I could write some code in the SQLiteningServerMonitor to read the SQLitening log file and analyze it for dropped connections, but how can that monitor application then communicate back with the server application?  Would it be wise to have it adjusting the db/table with the user account information directly?
Hi everyone.

I've been investigating SQLitening after accepting that Tsunami's future is uncertain.

I was pleasantly surprised to read about the recent update including server side processing.  This looks to be a viable back end solution for one of my projects, but I do have a few questions:

  • Does SQLitening offer any method to count/track connections to a database and/or table (that could be used to implement a licensing system)?  IOW, if I build an application that requires clients to store a licensing key which encodes the maximum number of allowed concurrent users, is there a mechanism that can be used to enforce it?  Complicating things a bit more, if my app has a login system where users can have different access levels, would it be possible to limit connections by access level?
  • Is there a physical or practical limit on the number of connections SQLite/SQLitening can handle?
  • How stable is SQLitening?  Roughly 90% of my client base is Fortune 500 companies and their IT depts. will complain vociferously if my app is crashing their server repeatedly.
  • Who is developing SQLitening?  What plans are there for developing and supporting the product over the next few years?  Will SQLitening be updated to take advantage of SQLite updates?