Results 1 to 2 of 2

Thread: New database events in Lianja 5

  1. #1
    Lianja Development Team barrymavin's Avatar
    Join Date
    Feb 2012
    UK, USA, Thailand

    New database events in Lianja 5

    I have added two new database events in Lianja 5.


    These are both called with two parameters, database and table.

    Example usage of dbc_beforeopentable you could SET CONNSTR TO "..." to handle user specific VT authentication with MSSQL MySQL etc.

    when dbc_afteropentable is called the table is now open so you could restrict data accessible to a user by specifying a filter.

    If SET DBCEVENTS OFF is in effect the event procs are not called.

    There are quite a few uses for these two new database events.

    Name:  Screen Shot 2019-01-02 at 12.48.23 PM.jpg
Views: 208
Size:  67.2 KB

    It's worth mentioning that in Lianja 5 you can specify global connection strings for virtual tables using SET CONNSTR TO "....".

    If the CONNSTR for a virtual table is missing the the global one is used. If it starts with a "?" and there is a global connstr then that is used otherwise the "?" is removed from the connstr and that is used.

    This all makes for simplified virtual table usage and a simpler way to switch database servers.
    Last edited by barrymavin; 2019-01-01 at 23:59.
    Principal developer of Lianja, Recital and other products

    Follow me on:


  2. #2
    Lianja MVP
    Join Date
    Feb 2012
    Berea, KY, USA

    Developers: these are incredibly important features when you get to the stage of deployment.

    These features allow us to meet modern security requirements (such as database passwords changing every 90 days) and also deployment/redeployment issues (servers changing; deploying at multiple customers) using secure, data-driven methods.

    Whether it's a customer's KMS (Key Management System) or one we write in Lianja, this means the connection string will a) never have to exist in any form on the same network as the Lianja database and b) will exist in unencrypted form only in memory for the amount of time the table takes to open, by setting it back to nonsense in the dbcAfterTableOpen.

    If writing your own, let me point out that Chilkat's diffie-hellman implementation is in its default configuration fast enough to handle the encryption between the dbcBeforeOpenTable event and the KMS, so even that connection becomes protected (e.g., to an https web service on it's own DMZ), with no keys stored anywhere in your app. And if you haven't explored Chilkat's controls, which integrate a first-class objects in Lianja, let me suggest you do. They are force multipliers because, like Lianja, the needs of developers have been wrapped into the basic functions.





Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Journey into the Cloud
Join us