[wp-hackers] Grab a seat. On Delaying 2.2, separating tables

[Robin Adrianse]

I don't agree. One of my big, BIG pet peeves of the 2.1 release was that
link and post categories were, so to speak, "unified." If we're going to
separate them in the UI, then we should really put them in separate tables.

On 4/15/07, Matt <speedboxer at gmail.com> wrote:
>
> +0.5
>
> I think that Tags should have it's own table, but Link Categories and Post
> Categories *should* be in the same table, simply because most people
> probably won't have very many Link Cats, so you'll end up with a Table
> with
> like less than 10 rows in it.
>
>
> On 4/15/07, Brian Layman <Brian at thecodecave.com> wrote:
> >
> > > For what it's worth I'll cast my vote in favour. Getting rid of the
> > link categories table was itself bad
> > > database design and adding tags just compounds that. It's no way to
> > treat a relational database!
> >
> > I've not looked at the tagging implementation, but I will +1 categories
> > (re)split.  I never saw the bang for the buck of unifying these two
> > tables and while conversions weren't quite as bad as I predicted them to
> > be (on this list), we still lost features and broke parts of sites (link
> > categories suddenly appearing that were hidden before, missing blog roll
> > side bar sections, and other oddities.).  I can't imagine adding tags to
> > the same table will be a path to future success.  That table is going to
> > need to be split again at some point.  These are not all uniform
> > concepts.  Let's do it now before we get further down the path.
> >
> > Thanks for bringing this up again Robert.
> >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
>
>
>
> --
> Matt (speedboxer at gmail.com)
> http://mattsblog.ca/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>