Hey Oleg,
the tag to product argument makes no sense to me... What are you
attaching tags to if not the product's ID's?
In your version, you want to edit product ids.. so what happens to the
references in the product_to_tags table? You have to update them
accordingly?
If you just went with autoincrement ids internally, you'd never have
to worry about that relationship, in fact, all the retrieval would be
nicely abstracted by your ORM (ProductQuery::create() ->
filterByTag("blah"); ..no need to understand simple selects better.)
The space vs. column count argument sounds like an "early
optimization" fallacy to me - have you run into any memory issues so
far?
Regarding the extra column, my whole argument is not about how things
"can" be done - of course you can do things your way - but how things
will be more maintainable in the future. Using your internal ID all
over the place is a rookie mistake, and you'll learn that as soon as
you integrate with more than one outside system. Or, you'll never have
to do that, and so you won't need to learn it - and that may work for
your current level, but it's gonna limit you in the long run.
That all being said, if you're still trying to look into editing ID's,
this discussion here would be relevant:
http://groups.google.com/group/symfony-devs/browse_thread/thread/5dc04332a015411b
And looking at the newest propel admin generator, I think editing IDs
the way you proposed at the beginning should work.
Daniel
On May 24, 7:36 am, Oleg Sverdlov <oleg.sverd...@gmail.com> wrote:
> On Mon, May 24, 2010 at 3:57 PM, Eno <symb...@gmail.com> wrote:
> > > I do not agree. It may be simply of indicator of people relying too much
> > on
> > > belowed MySQL AUTO_INCREMENT feature.
>
> > Beloved? AUTO_INCREMENT was designed to be used this way. If humans
> > assigned IDs, how do you guarantee uniqueness when there's thousands of
> > rows? Do you expect users to check manually?
>
> > primary key has unique value. The database server is supposed to raise an
>
> error when someone tries to enter duplicate value. It's up to software to
> process this type of errors.
>
> --
> Oleg
>
> --
> 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 users" group.
> To post to this group, send email to symfony-users@googlegroups.com
> To unsubscribe from this group, send email to
> symfony-users+unsubscr...@googlegroups.com
> For more options, visit this group
> athttp://groups.google.com/group/symfony-users?hl=en
--
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 users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
