Hi,

If you don't specify an id on a model in Doctrine 1 it adds an id with the
options defined in the attribute ATTR_DEFAULT_IDENTIFIER_OPTIONS:

$manager->setAttribute(Doctrine_Core::ATTR_DEFAULT_IDENTIFIER_OPTIONS,
array(...));

- Jon

On Thu, Apr 29, 2010 at 1:05 PM, Tom Boutell <[email protected]> wrote:

> I didn't realize that was possible. How do we set the default type for
> id in schema.yml? That will automatically be respected by plugin
> schemas that get merged?
>
> Thanks!
>
> On Thu, Apr 29, 2010 at 10:31 AM, Jonathan Wage <[email protected]> wrote:
> > Hi,
> >
> > I think we have a bigger problem here. Either way we have a compatibility
> > issue between models in your project and models included in a plugin if
> the
> > plugin includes a hardcoded id and length.
> >
> > I changed the plugin to not specify any id so that it uses the configured
> > default. The idea was then in Doctrine you can specify those defaults so
> > they are the same for all foreign keys and identifiers.
> >
> > Thoughts?
> >
> > - Jon
> >
> > On Thu, Apr 8, 2010 at 2:47 PM, Tom Boutell <[email protected]> wrote:
> >>
> >> Question mostly for Jon Wage:
> >>
> >> Is there a rough timetable for a stable release of the new
> >> sfDoctrineGuardPlugin?
> >>
> >> The new version has BIGINTs for IDs and incorporates email address and
> >> full name fields in the sf_guard_user schema. We are on board with
> >> that, but it's difficult to plan for the short and medium-term future
> >> without a rough idea of when that might be the commonly installed
> >> version. Right now our apps tend to have fullname and email address
> >> fields in an sfGuardUserProfile table. And our plugins (including
> >> apostrophePlugin), which need to be able to refer to sfGuardUser
> >> objects via foreign keys, have 4-byte  integers for user ID fields.
> >>
> >> MySQL generates an error if you try to add a foreign key relationship
> >> with a different integer type so there's a compatibility issue here.
> >>
> >> At the same time I see that the core Symfony and Doctrine teams are
> >> working hard on Symfony 2.0 and Doctrine 2.0. So I wonder if the new
> >> sfDoctrineGuardPlugin is to be expected any time soon, or if it might
> >> make better sense to just skip it and require the use of the currently
> >> stable release of sfDoctrineGuardPlugin unless and until we redo our
> >> stuff anyway for Symfony 2.0.
> >>
> >> Any insight welcome. Thanks!
> >>
> >> --
> >> Tom Boutell
> >> P'unk Avenue
> >> 215 755 1330
> >> punkave.com
> >> window.punkave.com
> >>
> >> --
> >> If you want to report a vulnerability issue on symfony, please send it
> to
> >> security at symfony-project.com
> >>
> >> You received this message because you are subscribed to the Google
> >> Groups "symfony developers" group.
> >> To post to this group, send email to [email protected]
> >> To unsubscribe from this group, send email to
> >> [email protected]<symfony-devs%[email protected]>
> >> For more options, visit this group at
> >> http://groups.google.com/group/symfony-devs?hl=en
> >>
> >> To unsubscribe, reply using "remove me" as the subject.
> >
> >
> >
> > --
> > Jonathan H. Wage (+1 415 992 5468)
> > Open Source Software Developer & Evangelist
> > sensiolabs.com | jwage.com | doctrine-project.org | symfony-project.org
> >
> > You should follow me on Twitter: http://www.twitter.com/jwage
> >
> > You can contact Jonathan about Doctrine, Symfony and Open-Source or for
> > training, consulting, application development, or business related
> questions
> > at [email protected]
> >
> > --
> > If you want to report a vulnerability issue on symfony, please send it to
> > security at symfony-project.com
> >
> > You received this message because you are subscribed to the Google
> > Groups "symfony developers" group.
> > To post to this group, send email to [email protected]
> > To unsubscribe from this group, send email to
> > [email protected]<symfony-devs%[email protected]>
> > For more options, visit this group at
> > http://groups.google.com/group/symfony-devs?hl=en
> >
>
>
>
> --
> Tom Boutell
> P'unk Avenue
> 215 755 1330
> punkave.com
> window.punkave.com
>
> --
> If you want to report a vulnerability issue on symfony, please send it to
> security at symfony-project.com
>
> You received this message because you are subscribed to the Google
> Groups "symfony developers" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<symfony-devs%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/symfony-devs?hl=en
>



-- 
Jonathan H. Wage (+1 415 992 5468)
Open Source Software Developer & Evangelist
sensiolabs.com | jwage.com | doctrine-project.org | symfony-project.org

You should follow me on Twitter: http://www.twitter.com/jwage

You can contact Jonathan about Doctrine, Symfony and Open-Source or for
training, consulting, application development, or business related questions
at [email protected]

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony developers" 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.com/group/symfony-devs?hl=en

Reply via email to