Ticket #1585 (closed defect: fixed)
Oracle building model fails due to "precision" element
| Reported by: | tchakkapark | Owned by: | jwage |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.0.4 |
| Component: | Import/Export | Version: | 1.0.3 |
| Severity: | Keywords: | oracle build-model precision build-schema | |
| Cc: | Has Test: | no | |
| Status: | Pending Core Response | Has Patch: | yes |
Description (last modified by tchakkapark) (diff)
I am using Symfony 1.1 with the sfDoctrinePlugin along with PHP version 5.2.6. I've confirmed that this happens with the 1.0.x version of Doctrine, as well as the latest 1.1 version of doctrine in SVN (changeset 5110).
My Oracle database has precision set to some of the number datatypes.
When reverse-engineering using
symfony doctrine:build-schema
The schema.yml gets generated, but also includes the precision:
ACTIVITIES:
tableName: ACTIVITIES
columns:
id:
type: integer(8)
autoincrement: true
primary: true
activity_id:
notnull: true
type: integer(22)
precision: '12'
When that YML syntax is passed to
symfony doctrine:build-model
I encounter the following:
Invalid schema element named "precision" at path "ACTIVITIES->columns->activity_id
However, the ORM builds fine when I remove any precision items in the YML syntax.
I'm unsure if having that element is necessary at all for the purposes of Doctrine.
Change History
Note: See
TracTickets for help on using
tickets.