Details
-
Type:
New Feature
-
Status:
Awaiting Feedback
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.3
-
Fix Version/s: None
-
Component/s: Platforms
-
Security Level: All
-
Labels:None
Description
Please add support for uuid datatype in PostgreSQL
Activity
ross neacoders
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Summary | Support for GUIDs and UIDs for MS-SQL and PostgreSQL platforms in 2.1.x | Support for UIDs in PostgreSQL |
| Affects Version/s | 2.3 [ 10184 ] | |
| Affects Version/s | 2.1.6 [ 10181 ] | |
| Description |
I cherry-picked some changes from This is basic support of GUIDs/UUIDs types in DBAL for MSSQL and PostgreSQL platforms. I don't speak about GUID generators - this is something for 2.3 version, but just support of basic types (so reverse engineering does not crash on unknown type), and you can use guids - that's my point. |
Please add support for uuid datatype in PostgreSQL |
Benjamin Eberlei
made changes -
| Workflow | jira [ 13671 ] | jira-feedback2 [ 17607 ] |
Benjamin Eberlei
made changes -
| Workflow | jira-feedback2 [ 17607 ] | jira-feedback3 [ 19960 ] |
Ross Cousens
made changes -
| Status | Open [ 1 ] | Awaiting Feedback [ 10000 ] |
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
- Request to http://www.doctrine-project.org/fisheye/ failed: Error in remote call to 'FishEye 0 (http://www.doctrine-project.org/fisheye/)' (http://www.doctrine-project.org/fisheye) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=DBAL-264, expand=changesets[-21:-1].revisions[0:29],reviews}, methodType=GET}] : Received status code 503 (Service Temporarily Unavailable)
It seems the only missing piece is the implementation of the getGuidExpression method in the PostgreSqlPlatform class.
Details on generating UUIDs from postgres can be found here:
http://www.postgresql.org/docs/current/static/uuid-ossp.html
Things that would need to be addressed:
1) It requires the uuid-ossp module to be installed in the database. Solve with documentation or ...?
2) There isn't just one function. Just pick one or make it configurable with a sane default?