Spring+Hibernate+JPA: Add dynamic tables/entities - spring

An application permits admin users to upload CSV-files and save them as database tables.
The application uses Spring+JPA+Hibernate to access the database. How can I access the dynamically added new tables/entities to the system, without restarting or even recoding the system?

Related

How to change database connection dynamically in laravel-octane?

I need to change database dynamically on the fly in laravel-octane or laravel-swoole package.
I am working on a custom multi tenant system. Application is working fine without swoole/octane.

is it possible to authenticate in a springboot app using the different oracle accounts

I'm developing a web application and I'm wondering if i can set the authentication to check the oracle users instead of a user table I that I manually make.
Basically I want this to make it easier to trace user activities using oracle's native logs and add an extra layer to manage permissions.

Existing data model getting replaced while uploading a new rpd file?

when I upload a new RPD file in obiee12c existing data model getting replaced, if I wanna see the datamodel for multiple applications how can I do it
An RPD upload does just that. It uploads an RPD. You work with multiple applications by having all those applications inside one RPD. Whether one source or 50 makes no difference at all to the RPD.

How to prevent accessing particular database in SQL Server 2008?

I'm working on a Windows application. When I give this software to the client it is necessary to give database also? I want to lock the database of SQL Server on his computer so that he can not open that database or copy or view its schema or anything by which he can access that database.
When he tries to access that, it must ask for a password. So, what is the solution for the above?
SQL Server databases cannot be password-protected - they're not just files that get opened (like dBase or SQLite)
"normal" access control is handled via permissions and users - you can define who can see what, modify what, delete what
This does not however prevent a system admin from looking at your database schema and contents; there's really no way to prevent this, a sysadmin can also just copy the .mdf file to another server and attach it there and circumvent all your "security"
if you really must hide all of this, don't deliver a database - hide the database in your own company and provide a web-service based interface to the customer who can then call those web services to do his work - then the schema and data is under your control, but also: the customer's data is no longer under his control so he might not like that.....

H2 Database multiple connections

I have the following issue:
Two instances of an application on two different systems should share a small database.
The main problem is that both systems can only exchange data through a network-folder.
I don't have the possibilty to setup a database-server somewhere.
Is it possible to place a H2 database on the network-folder and let both instances connect to the database (also concurrently)?
I could connect with both instances to the db using the embedded mode if I disable the file-locking, right?
The instances can perfom either READ or INSERT operations on the db. Do I risk data corruptions using multiple concurrent embedded connections?
As the documentation says; ( http://h2database.com/html/features.html#auto_mixed_mode
)
Multiple processes can access the same database without having to start the server manually. To do that, append ;AUTO_SERVER=TRUE to the database URL. You can use the same database URL independent of whether the database is already open or not. This feature doesn't work with in-memory databases.
// Application 1:
DriverManager.getConnection("jdbc:h2:/data/test;AUTO_SERVER=TRUE");
// Application 2:
DriverManager.getConnection("jdbc:h2:/data/test;AUTO_SERVER=TRUE");
From H2 documentation:
It is also possible to open the database without file locking; in this
case it is up to the application to protect the database files.
Failing to do so will result in a corrupted database.
I think that if your application use always the same configuration (shared file database on network folder), you need to create an application layer that manages concurrency

Resources