Using reserved keyword as schema key
See original GitHub issueIn our project we have existing database scheme and there is no longer possible to change it. Is where workaround to use reserved key in schema? We need to use options
key.
Issue Analytics
- State:
- Created 10 years ago
- Comments:18 (4 by maintainers)
Top Results From Across the Web
Reserved schema names and reserved words - IBM
Reserved schema names and reserved words. There are restrictions on the use of certain names that are required by the database manager.
Read more >Reserved words and schemas | Databricks on AWS
Reserved words are literals used as keywords by the SQL language which should not be used as identifiers to avoid unexpected behavior. Reserved...
Read more >How to escape SQL reserved keywords with JPA and Hibernate
Learn how to escape SQL reserved keywords when using JPA and Hibernate. Reserved keywords can be escaped in table or column names.
Read more >Reserved keywords - Amazon Athena - AWS Documentation
Athena uses the following list of reserved keywords in SQL SELECT statements and in queries on views. If you use these keywords as...
Read more >9.3 Keywords and Reserved Words - MySQL :: Developer Zone
Keywords are words that have significance in SQL. Certain keywords, such as SELECT , DELETE , or BIGINT , are reserved and require...
Read more >Top Related Medium Post
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue was specifically about using options as a schema key, which is ok right now. As for using reserved keywords, we don’t plan on allowing using things like
save
as schema keys right now, because that would require massive api changesI agree with @smonkey72. I think mongoose should use prefixed names of reserved keys like this:
Or use
properties
for object fields (like JSON Schema):