Opened 7 years ago

Closed 7 years ago

#4381 closed (wontfix)

Using caps in column/table names in postgresql requires those fields to be quoted in initial sql files

Reported by: Remco Wendt <remco@…> Owned by: jacob
Component: Documentation Version: master
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


This may be nice to specifically refer to in the initial data paragraph within the 'Creating models' documentation.

Attachments (0)

Change History (1)

comment:1 Changed 7 years ago by mtredinnick

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

Normally you don't need to worry about the capitalisation (if you create table "Foo", you can still refer to it as "foo" in select and insert statements), so this is very rare case. Yes, it's needed sometimes in "alter table" situations, but it's still rare.

Also, this is very database-specific and something that is the documentation for each particular database. We should not be duplicating the documentation for how to write SQL for a particular database.

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.