>>>>> Igor Tandetnik <itandet...@mvps.org> writes:
>>>>> Ivan Shmakov <i...@gray.siamics.net> wrote:
>> This structure is, obviously, could just as well be represented
>> with, e. g.:
>> CREATE TABLE "foo" (
>> "key" INTEGER PRIMARY KEY,
>> "value" INTEGER NOT NULL,
>> "value-1" INTEGER,
>> …
>> "value-N" INTEGER);
> Or else with this:
> CREATE TABLE "foo" (
> key INTEGER PRIMARY KEY,
> value INTEGER NOT NULL);
> create table fooDetails(
> key INTEGER PRIMARY KEY
> REFERENCES "foo" (key),
> L integer not null,
> value integer not null);
> That's what a fully normalized schema would look like for your data.
Indeed. But I don't quite understand how does it make my task
any easier? I fail to see how can I ensure that the
(value _1, …, value _N) tuple is unique. (I. e., that there's
an /invertible/ mapping of keys to value tuples.)
--
FSF associate member #7257
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
