• Make it possible to point to a DomSQL file in another DB

    By Tommy Valand 1 decade ago

    Not sure if this is a limitation in SQLite/virtual tables or DomSQL.

     

    If I try to fetch data (SELECT * FROM tablename) in an application from another application on the same server using createConnectionFromUrl, I get this error:
    SQL logic error or missing database

     

    I can list the tables in the database using this command:
    SELECT * FROM sqlite_master

     

    From this, I think that the connection is ok.

     

    The reason I would like to connect to another database/domsql is that I want to have a standalone reporting application that connects to a range of databases. The target databases for reporting inherit from a template. This means that I can maintain one configuration for all current and future applications in one place.

     

    With the current limitation, I will need to create separate configurations per target database in the reporting application.

     

    Not sure if this is related, but I found a thread regarding Java/SQLite and virtual tables:
    https://community.oracle.com/thread/1774849

     

     

    • Not in plan,at least from my side

      By Philippe Riand 1 decade ago

      This is tricky as the SQLite DB lifecycle is tied to the NSF application lifecycle. Plus some other potential issues, like reading a design element from another DB, or DB ACL. The easiest work around is then to create the definition file in the current DB, and make it point to a different NSF for the data.

      • Ok

        By Tommy Valand 1 decade ago

        Thanks for clarifying :)