-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does @cap-js/hana support quoted sql mapping? #783
Comments
not yet, Pr still pending #681 |
just as an idea to what could be a solution. Since we have a source table like "schema.table" which gets converted to SCHEMA_TABLE, and since we generate also hdbtable, hdbview. Isn't it a good idea also to delegate to framework to generate hdbsynonym files? That would help us may be to migrate from quoted mapping if we could just rebuild the project with synonyms, generated from the model. What do you think about this? Thanks! |
So let's say in case of the entity like:
we will not generate hdbtable ( because it exists ), but we'll generate synonym ( it's ok if it's for same schema ) like |
@johannes-vogel do you know which team to address mentioned above problem with cds compiler which compiles hdbview which is not possible to deploy if sql mode is plain? Thanks! |
@danjoa Daniel, do you know may be - is it possible to generate hdbview with columns like "timestamp" in a lower case if plain mode is used? Thanks! |
@danjoa one more point about usage of npm dependencies. Now to test the logic with and without @cap-js/hana I have to change package.json dependencies and reinstall packages every time. This is very inconvenient. I'm sure there must be a better way not to use hew driver / plugin even if it's being installed, right? Thanks! |
Hi! Following the advice from SAP we've migrated to @cap-js/hana. However it seems like this connector doesn't support yet quoted sql mapping. At least our sql queries fail with error like
Invalid table name: Could not find table/view API_ODATA_BUCKET_BALANCE_MONTHLY
while we have it generated like this:The text was updated successfully, but these errors were encountered: