Hi Filip,
Thanks a lot for your kind help. Selecting only once did the trick. Dropping
to 2 seconds for select instead of 50 IS an improvement indeed :)
Indexes on columns already existed, and just out of curiosity I've tested
char columns instead of varchars, with no significant positive changes.
On Thu, Apr 23, 2009 at 09:44:53AM +0100, Seref Arikan wrote:
> I have worked with very capable DBAs before, and even though it has been
> quite some time since I've done real DB work, I would like to invest in
> postgresql as much as I can
Seref, if you can muster the man power to build archetyp
On Wed, Apr 22, 2009 at 06:21:41PM -0600, Scott Marlowe wrote:
> > 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" VARCHA
On Thu, Apr 23, 2009 at 12:02:13AM +0100, Seref Arikan wrote:
> I have a set of dynamically composed objects represented in Java, with
> string values for various attributes, which have variable length. In case
> you have suggestions for a better type for this case, it would be my
> pleasure to he
W dniu 22 kwietnia 2009 23:47 użytkownik Seref Arikan <
serefari...@kurumsalteknoloji.com> napisał:
> 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" VARCH
Hi Scott,
I agree, and I am doing the entity attribute model because I simply have to.
This table is used to persist data that is hold in user defined information
models. Kind of a domain specific language. The users continously create
these hierarchical structures, so neither the amount of them, n
Seref Arikan wrote:
I have a set of dynamically composed objects represented in Java, with
string values for various attributes, which have variable length. In
case you have suggestions for a better type for this case, it would be
my pleasure to hear about them.
cut out about 3 layers of abst
2009/4/22 Seref Arikan :
> 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(1
Hi there,
I have a set of dynamically composed objects represented in Java, with
string values for various attributes, which have variable length. In case
you have suggestions for a better type for this case, it would be my
pleasure to hear about them.
2009/4/22 Grzegorz Jaśkiewicz
> you keep ev
you keep everything in varchars, and yet you request improvements in
performance.
you are a funny guy, ...
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
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_str
2009/4/22 sarikan
>
> Dear members of the list,
> I have a function which returns a custom type, that has only two fields,
> each of them being varchar arrays.
> The reason that I have written this function is that I have a table
> basically with the following structure (with simplified column na
12 matches
Mail list logo
