Project

General

Profile

Feature #6898

PostgreSQL schema improvements

Added by Greg Shah over 3 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to Database - Feature #6418: represent extent fields as arrays WIP
Related to Database - Support #4058: consider denormalizing tables as the default approach New

History

#1 Updated by Greg Shah over 3 years ago

  • Related to Support #4058: consider denormalizing tables as the default approach added

#2 Updated by Greg Shah over 3 years ago

We have multiple requests for changes to the default approach to some PostgreSQL schema. We have a small window right now in which we can tolerate some improvements to the schema. The obvious changes:

  • use of a native case-insensitive data type (citext?) for character instead of using TEXT and accessing it using UPPER(RTRIM()) (see also #2949)
  • doing a non-crappy job of extent column support (see #4060, #4058 and #6418)

Eric: Am I missing anything here?

#3 Updated by Greg Shah over 3 years ago

  • Related to deleted (Support #4058: consider denormalizing tables as the default approach)

#4 Updated by Greg Shah over 3 years ago

  • Related to Feature #6418: represent extent fields as arrays added

#5 Updated by Greg Shah over 3 years ago

  • Related to Support #4058: consider denormalizing tables as the default approach added

Also available in: Atom PDF