Replies: 1 comment
-
|
It's very easy to try this out yourself. First: cds init --add tiny-sample q && cd $_
echo "using CatalogService from './cat-service'; annotate CatalogService.Books : author with @readonly;" > srv/annotations.cdsThen: cds deploy --to sqlite
sqlite3 db.sqlite 'select * from CatalogService_Books;'which shows: Thus: No impact on initial data deployment. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi CAP community,
I am trying to update our CDS model by using @readonly annotation for one of our fields.
Based on provided documentation Declarative Constraints | capire , I've understood that this will permit to ignore the field value on both Create and Update operation.
My question here is: will this impact deploying initial data for that field for that field using CSV file ? should I expect a regeneration of this table artifact with a different column definition when using @readonly annotation?
BR,
Tesnim
Beta Was this translation helpful? Give feedback.
All reactions