#13832 closed (duplicate)
Changeset #13363 broke PostgreSQL support for app names with uppercase characters
| Reported by: | Simon Meers | Owned by: | Simon Meers |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Keywords: | postgresql, uppercase, table_name | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
As described here http://www.postgresql.org/docs/8.4/static/functions-info.html#FUNCTIONS-INFO-CATALOG-TABLE, for pg_get_serial_sequence(table_name, column_name), "Because the first parameter is potentially a schema and table, it is not treated as a double-quoted identifier, meaning it is lowercased by default, while the second parameter, being just a column name, is treated as double-quoted and has its case preserved"
Attachments (1)
Change History (5)
by , 15 years ago
| Attachment: | 13832.diff added |
|---|
comment:1 by , 15 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
comment:2 by , 15 years ago
Ah, yes it is; no keyword searches brought that one up for me thanks to the comparatively ambiguous title and description.
My patch is better than the one provided for #13821 mind you, as it uses quote_name and includes a regression test.
Note:
See TracTickets
for help on using tickets.
This looks like a dupe of #13821.