Re: [GENERAL] Specific database vars, again... - Mailing list pgsql-novice

From Glus Xof
Subject Re: [GENERAL] Specific database vars, again...
Date
Msg-id r2q18c2d6a11004201235se742207cw79b6af47dc2766a5@mail.gmail.com
Whole thread Raw
In response to Specific database vars, again...  (Glus Xof <gtglus@gmail.com>)
Responses Re: [GENERAL] Specific database vars, again...
Re: [GENERAL] Specific database vars, again...
List pgsql-novice
2010/4/20 Ben Chobot <bench@silentmedia.com>:
>
> On Apr 20, 2010, at 10:53 AM, Glus Xof wrote:
>
>> Hi again,
>>
>> Maybe, I didn't explain my question enough.
>>
>> I need to record properties that belongs to an specific database (and
>> so, they work at database level... not at global scope:
>>
>> * Or, must to create an specific one-row table ?.
>
> Depending on how you intend to use these variables, this sounds like a fine idea to me. What are your problems with
it?

The idea is storing values that can be remotely accessed by a
C++/libpqxx application. So, I just see that the first alternative
that I proposed (the use of \set variables) is really not good. But
the rest remains...

Now, the only option I have is to create a table, define one column
per variable, for using just one row. This can be accessed by a select
sql command...

You know other alternatives ???

Glus

pgsql-novice by date:

Previous
From: Glus Xof
Date:
Subject: Specific database vars, again...
Next
From: Glus Xof
Date:
Subject: Re: [GENERAL] Specific database vars, again...