How to automatically switch service to access to shared table between HANA and SQLite?

[kaztakata]

Dear team,

Thanks for your great contribution to share multitenancy application and instruction. I am implementing multitenancy application based on your repository and I have question for shared database container.

In your explanation, we need two CDS for both HANA for production and SQLite for local testing. Currently I extended your service to access to shared table and manually change CDS file /code/db/sqlite/data-model to /code/db/hana/data-model before deployment to Cloud Foundry.

Is there smarter way to switch between two CDS files? I could not find good example of this use case. So I am helpful if you advise me.

[gregorwolf]

Please check this example: fiori/package.json#L42

[kaztakata]

Hi @gregorwolf,

Thanks for your answer. That is helpful and I already checked this code sample.

But my question is how to refer to db CDS from service CDS. For example, when I want to add Shared entity to public-service.cds, now I am writing like below.

using {susaas.common as common} from '../../db/hana/data-model';
...
service PublicService @(path : '/catalog/PublicService', impl: 'srv/public-service') {

  entity Shared as projection on common.Shared
  ...

Hence I am specifying db/hana/ directory, I cannot use it in for local SQLite. How to automatically switch path in service CDS, or something alternatives?

[alperdedeoglu]

Hi Dear @kaztakata san, Thank you very much for your contribution! 

To be honest, when we designed this "common container" approach, I personally only considered the database layer usage. But your requirement is valid and makes sense. I think it might be useful for the rest of our valued susaas community members too.

I have a nice solution proposal for the problem you have. This solution proposal should not change the behavior of the repository and should also fix the problem you have.

The main reason we have two files is that Shared  entitys DB artifacts are already created on deployment; therefore, we would like to mention it to HANA to avoid errors, but for sqlite we ne need to create the tables.

Can you please confirm if the changes on the fix/cc-localdev branch fix the problem you have?

I also linked the relevant PR to this issue.

[kaztakata]

Hi @alperdedeoglu san,

Thanks for your solution. I think extend CDS is effective for this situation. I used your code and changed package.json to switch between production and development profiles like previous answer by Gregorwolf then working.