Persistence
3 posts
• Page 1 of 1
Persistence
Hello,
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.
Luc
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.
Luc
- lucdep
- Posts: 53
- Joined: Wed Oct 10, 2018 12:01 pm
Re: Persistence
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)
(writeback isolation level: DATASOURCE)
Usually, a workscreen will call save on close.
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.
-
Support@SIB - Posts: 353
- Joined: Mon Sep 28, 2009 1:56 pm
Re: Persistence
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.
It depends on the storage if it sends the data immediately or delayed. The standard DBStorage sends data immediately to the database.
-
Support@SIB - Posts: 353
- Joined: Mon Sep 28, 2009 1:56 pm
3 posts
• Page 1 of 1