#1585: Oracle building model fails due to "precision" element
----------------------------+-----------------------------------------------
  Reporter:  tchakkapark    |       Owner:  jwage                               
     
      Type:  defect         |      Status:  new                                 
     
  Priority:  minor          |   Milestone:  1.1.0                               
     
 Component:  Import/Export  |     Version:  1.1-DEV                             
     
Resolution:                 |    Keywords:  oracle build-model precision 
build-schema
  Has_test:  0              |    Mystatus:  Pending Core Response               
     
 Has_patch:  0              |  
----------------------------+-----------------------------------------------
Old description:

> 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.

New description:

 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.

-- 
Ticket URL: <http://trac.doctrine-project.org/ticket/1585#comment:1>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"doctrine-svn" group.
 To post to this group, send email to [email protected]
 To unsubscribe from this group, send email to [EMAIL PROTECTED]
 For more options, visit this group at 
http://groups.google.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---

Reply via email to