Re: Help request to improve function performance
От | Scott Marlowe |
---|---|
Тема | Re: Help request to improve function performance |
Дата | |
Msg-id | dcc563d10904221721ve3106fbubdb805d16e2d1384@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Help request to improve function performance (Seref Arikan <serefarikan@kurumsalteknoloji.com>) |
Ответы |
Re: Help request to improve function performance
Re: Help request to improve function performance Re: Help request to improve function performance |
Список | pgsql-general |
2009/4/22 Seref Arikan <serefarikan@kurumsalteknoloji.com>: > Hi Filip, > First of all: thanks a lot for your kind response. Here is the create script > for my schema: > > CREATE TABLE "app"."archetype_data" ( > "id" BIGINT NOT NULL, > "context_id" VARCHAR(1000), > "archetype_name" VARCHAR(1000), > "archetype_path" VARCHAR(1000), > "name" VARCHAR(1000), > "value_string" VARCHAR(1000), > "value_int" BIGINT, > "value_double" DOUBLE PRECISION, > "session_id" VARCHAR(1000), > "instance_index" INTEGER, > CONSTRAINT "archetype_data_pkey" PRIMARY KEY("id") > ) WITHOUT OIDS; If I'm not mistaken, you're doing Entity Attribute Value model type storage. I.e. a database in a database. Makes for easy coding, and danged near impossible to troubleshoot your data. It's a religious issue but I come down on the side that good data modelling is hard for a reason, because it pays you back so much in the end.
В списке pgsql-general по дате отправления: