This issue seems to be postgres-specific, and is currently supported through manual update of properties (barring bugs/missing features) .
Being a database-neutral platform, we don't plan to include specific handling of this issue in the platform itself.
Note that my understanding of the postgres documentation is that referring to the "Properties" table as properties (without quotes) should work as long as there isn't another table in the schema which has the same name using in a different case (for example: "PROPERTIES").Given the above, I speculate that in most real-world cases there would be no need to use quotes, as using the same name for multiple tables in the same schema seems like bad practice in the first place.
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign