[#1010651] DbConnection.GetSchema: Reserved words

View Trackers | Feature Requests | Download .csv | Monitor

Date:
2009-06-10 21:02 Priority:
3

State:
Open

Submitted by:
Dario Quintana (darioquintana) Assigned to:
Nobody (None)

Category: Group:

Resolution:
None

Summary:
DbConnection.GetSchema: Reserved words

Detailed description
Useful for frameworks that use this information in Schema Update, like NHibernate.

Followup

Message
Date: 2009-06-12 15:50 Sender: Dario Quintana I think it's not necessary to be version-dependant, the npgsql can provide the union between both keywords set, then we can prevent event to the clients to fall into migration issues. The purpouse behind NH, is auto-quote the columns/tables wich names are included in the set when DDL-creation/Configuration ocurrs. About this "key word is not reserved in PostgreSQL does not mean that the feature related to the word is not implemented". What this means? Do it means that I can have a non-reserved word 'foo', but with exactly that word 'foo' I have some X funcionality? If it's yes, then we should add the 'foo' word to the reserved-word set, becuase that can cause issues/conflicts with .Net clients. And if we have the word as a reserved-word and that word hasn't functionality, I don't see the problem to exclude that word from the reserved-word set (maybe should be keeped to be compliance with PostgreSQL) Conclusion, in my opinion, we should add the words that can cause conflicts in the applications of the npgsql clients.
Date: 2009-06-11 02:54 Sender: Josh Cooley Do you expect the list to be version dependent? We support 7.x and 8.x http://www.postgresql.org/docs/7.3/static/sql-keywords-appendix.html http://www.postgresql.org/docs/8.3/interactive/sql-keywords-appendix.html SqlClient has things such as POSITION which can be used as column names. Should all words listed in one of those documents be listed even if they are not reserved?

Attached Files:

Changes:

No Changes Have Been Made to This Item