Forum > Databases

IBX : Can it handle database operation when network connection is not stable?

<< < (9/9)

tonyw:
I have today released an experimental version of IBX that supports Client side journaling. Client side journaling creates a per database attachment file recording each read/write transaction start and end, and each SQL query that modifies data in the database. It can optionally record each read only transaction and queries that do not modify data (e.g. select queries).

The purpose of client side journaling is:

    1. To create transaction and query log that can be used to recover from a lost database connection or server crash, and

    2. To provide a record of database activity for debugging purposes.

The experimental version currently supports the creation of the journal. However, applying the journal for recovery purposes is left to a later update - probably after Christmas.

The journal file is a text file and is intended to be human readable. Each record in the journal starts with an asterisk and is terminated by a line separator. Each record is identified by a single character immediately after the asterisk, followed by a timestamp, session id and transaction id. Each query is recorded as the original SQL with the parameters replaced by the parameter values as literals.

In order to support programmatic parsing of the journal file, the class TJournalProcessor may be found in the IBUtils unit.

For more information see ibx/fbintf/doc/README.ClientSideJournaling.pdf. Test22 in ibx/fbintf/testsuite also provides an example of direct use of the journaling capability, and ibx/testsuite Test29 provides an example of use of the new component IBJournal. Additional examples should follow in later releases.

This experimental version can be downloaded by svn using

svn co https://svn.mwasoftware.co.uk/viewvc/public/ibx/branches/journaling/ ibx-experimental

or point your browser at

https://svn.mwasoftware.co.uk/viewvc/public/ibx/branches/journaling/

and click on "Download Tarball" to get an archive of the experimental version.

incendio:

--- Quote from: tonyw on December 07, 2021, 02:53:31 pm ---or point your browser at

https://svn.mwasoftware.co.uk/viewvc/public/ibx/branches/journaling/

and click on "Download Tarball" to get an archive of the experimental version.

--- End quote ---

Downloaded and tried to unpack, got an error, see attachment

tonyw:

--- Quote from: incendio on December 08, 2021, 02:59:33 am ---
--- Quote from: tonyw on December 07, 2021, 02:53:31 pm ---or point your browser at

https://svn.mwasoftware.co.uk/viewvc/public/ibx/branches/journaling/

and click on "Download Tarball" to get an archive of the experimental version.

--- End quote ---

Downloaded and tried to unpack, got an error, see attachment

--- End quote ---

Looks like the software you are using to unpack the archive can't support symbolic links - or you are still using Windows XP! Although googling the subject, it looks like support in Windows for symbolic links is problematic (https://blogs.windows.com/windowsdeveloper/2016/12/02/symlinks-windows-10/).

svn (for windows) foes not have this problem.

The files affected are not critical and, apart from the first, are only used by the testsuite. You can always copy them from an older version - or from the archive as the links are to files in the archive. The first link is to a documentation file. fbintf is developed as a separate package with its own changelog and documentation - see fbintf/doc. A link to the user guide is placed in the top level doc folder for user convenience only.

Navigation

[0] Message Index

[*] Previous page

Go to full version