Page 1 of 1


PostPosted: Mon Dec 17, 2018 12:04 pm
by lucdep

It is not clear to me when VisionX writes the data entered in a workscreen effectively to the database. I have remarked on many occasions that data inserted or updated in a screen are not available for the HTML client or are not visible when querying the Postgres database in pgAdmin.


Re: Persistence

PostPosted: Mon Dec 17, 2018 1:54 pm
by Support@SIB
This is independent or VisionX. The JVx framework is used in the background!

Usually, a DataBook writes all data to the storage if:

(writeback isolation level: DATA_ROW)

  • you change the selected record/row#
  • you call save...

(writeback isolation level: DATASOURCE)

  • you call save...

Usually, a workscreen will call save on close.

Re: Persistence

PostPosted: Mon Dec 17, 2018 1:57 pm
by Support@SIB
The storage sends data to the data layer, e.g. a database if you use a DBStorage.

It depends on the storage if it sends the data immediately or delayed. The standard DBStorage sends data immediately to the database.