As far as I know there are some system entities which Cuba platform creates and uses internally. Such as SEC_USER table.
And what if I need to run several independent apps with unrelated sets of tables (but in same Oracle database schema) - can I add prefix to Cuba system tables - i.e. APP1_SEC_USER, APP2_SEC_USER…
It may be more convenient and logic to run each application in its dedicated schema, but it is not always possible.
Thanks!
Ok, thanks.
Is there any solution if we want to migrate legacy app to Cuba platform but one of legacy app tables has same name with one of Cuba internal tables (i.e. SEC_USER)? Is renaming that legacy table - the only way to migrate??
I suggest you to take a look at our post Migrating a Legacy Application to CUBA Platform.
Regards,
Daniil
Thank you very much! I’ll read it as soon as I can!
And one more question… Would you please tell me if we can separate cuba tables and domain tables by schemas.
In my case there are a lot of legacy tables in single oracle schema. These tables are belong to different not interrelated applications. So I’m considering migrate one of these legacy apps on Cuba, and it would be nice to keep all Cuba tables in separate schema (i.e. “CUBA.SEC_USERS”…) - to prevent addition of even more objects to big legacy schema…
Not sure if it is possible.
Reading link you provided found very interesting thesis:
Note: It is also possible to attach a legacy database as an additional datastore to a CUBA application. Thus the legacy database will remain completely unmodified, CUBA-related tables will be stored separately.
Seems it may be possible to use Cuba in my case… Need to investigate further.
You are right, create a separate schema (or even a different database) and use it as a main datastore in your CUBA application. Then connect your legacy database as an additional datastore and create model and UI from it.