https://doc.sibvisions.com/ 2026-04-24T07:21:08+00:00 https://doc.sibvisions.com/ https://doc.sibvisions.com/lib/tpl/material/images/favicon.ico text/html 2020-06-26T13:22:20+00:00 https://doc.sibvisions.com/jvx/server/storage/abstract_memory?rev=1593177740&do=diff Sometimes, you don't have a database accessible, but you need a storage for temporary or session relevant data. In that case, you could use an AbstractMemStorage. This storage stores data in an internal MemDataBook. It fully implements IStorage interface and allows clients to access data via databooks. text/html 2020-07-22T13:19:22+00:00 https://doc.sibvisions.com/jvx/server/storage/custom_sql?rev=1595423962&do=diff JVx has very useful database support based on DBStorage and DBAccess. The DBStorage is very powerful and supports automatic foreign, primary, and unique key detection. It reads allowed (check constraints) and default values automatically from your database table. text/html 2020-06-15T11:41:38+00:00 https://doc.sibvisions.com/jvx/server/storage/datasourcehandler_dbcredentials?rev=1592221298&do=diff Simple integration of multiple databases is an easy task with JVx. Configuration is usually completed via the application's config.xml file. This allows for easy access in the life cycle objects: <?xml version="1.0" encoding="UTF-8"?> <application> <securitymanager> <class>com.sibvisions.rad.server.security.DBSecurityManager</class> <database datasource="mydb" /> </securitymanager> <datasource> <db name="mydb"> <url>jdbc:oracle:thin:@localhost:1521:mydb</url> <… text/html 2020-06-29T13:32:45+00:00 https://doc.sibvisions.com/jvx/server/storage/dbcheck_constraints?rev=1593437565&do=diff In addition to the use of default values, the restriction to “allowed values” is another advantage of JVx. The “allowed values” for columns are usually defined in the database using check constraints. These are evaluated by JVx and assumed as allowed values. text/html 2020-06-29T13:31:34+00:00 https://doc.sibvisions.com/jvx/server/storage/dbdefault_values?rev=1593437494&do=diff Behind a well-designed database application, there is always a well-designed data model. This model ideally fulfills the third NF, or at least a reasonable medium between second and third NF. In the standard case, the user interface visualizes the data model and allows the collection of master- and transaction data. text/html 2020-06-29T12:31:09+00:00 https://doc.sibvisions.com/jvx/server/storage/filter?rev=1593433869&do=diff Usually the data for the client UI is limited on the server side, so that the client only receives data it needs. One efficient way to limit data is to use views in the respective database. This method, however, leaves us dependent on the database, and not all databases offer this feature. text/html 2024-11-18T10:23:37+00:00 https://doc.sibvisions.com/jvx/server/storage/insteadof?rev=1731925417&do=diff If you're an Oracle user, you'll know that it's possible to update views with insteadOf triggers. An insteadOf trigger will do the CRUD operation(s), and it will be called with new/changed values like any other trigger. It's like a procedure that does CRUD programatically. It's a simple concept but not available in all databases. text/html 2020-06-26T13:21:39+00:00 https://doc.sibvisions.com/jvx/server/storage/metadata?rev=1593177699&do=diff Metadata are an important element of JVx' model. Every column used in DataBook or Editor has a ColumnDefinition internally. This controls which editor will be used (date, text, number, selection, etc.), the datatype of the column, how many characters can be entered, and the like. A ColumnDefinition is created from metadata. The metadata are generated on server side. text/html 2020-07-22T13:10:42+00:00 https://doc.sibvisions.com/jvx/server/storage/metadata_caching?rev=1595423442&do=diff Databooks at the client already allow for the caching of metadata to minimize communication with the server. However, server-side storage updates metadata each time data is accessed. During productive use, this is unnecessary overhead that we would prefer to avoid. text/html 2020-06-15T11:57:47+00:00 https://doc.sibvisions.com/jvx/server/storage/sort?rev=1592222267&do=diff User-friendly UIs prepare and display data in clearly arranged form. This includes clear and relevant sorting of data. There are several different ways to sort data, and sorting can happen at various tiers. The client (client tier) can handle sorting, although that would mean that unwanted logic is located at the client. The database (data tier) also offers ways to sort data, for example, through the use of views. Unfortunately, not all databases support sorting using views. That only leaves th… text/html 2020-06-29T13:34:35+00:00 https://doc.sibvisions.com/jvx/server/storage/trigger?rev=1593437675&do=diff With JVx, the business logic can be developed in either the database or the middle tier. For the development of the business logic entirely in the middle tier, so-called server-side triggers are required. These triggers work just like the DataBook events at the client. text/html 2020-06-15T11:46:12+00:00 https://doc.sibvisions.com/jvx/server/storage/userdefined?rev=1592221572&do=diff JVx uses IStorage to transfer table data between client and server in standardized form. JVx contains an existing implementation for databases, DBStorage, and for dynamically assembled data, AbstractMemStorage. At the client, data is accessed via RemoteDataBooks.