[103395] users/cal/base-sqlite-portindex/src/port1.0/portmain.tcl

Lawrence Velázquez larryv at macports.org
Sun Feb 24 16:24:29 PST 2013

On Feb 24, 2013, at 7:05 PM, Clemens Lang <cal at macports.org> wrote:

> The problem with allowing duplicates and invalid values is comes back to
> bite you in the wrong place as soon as you start putting data into a
> format where that matters.
> Just an example: If I want to store dependencies in SQL as a list (i.e.,
> a proper separate table with a foreign key) and don't want to declare an
> artificial primary key I need to use the combination
> 	(port_id, dependency)
> as primary key.
> Now as you can see, having duplicate values in dependencies causes SQL
> errors when trying to put the second dependency into the database. Ugh.

Ah yes, the SQLite port index. That's a pretty good reason.

> We even have more options that shouldn't be handled like lists, as they
> currently are. Have you ever used use_autoconf-replace? Or
> use_autoconf-append? Did you ever set use_autoconf to 567?

I… ugh. Stop it, you're making my head hurt.

> But I agree, this should be documented.

Shouldn't everything?


More information about the macports-dev mailing list