Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] Specific database vars, again...

From: Ben Chobot <bench(at)silentmedia(dot)com>
To: Glus Xof <gtglus(at)gmail(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: [GENERAL] Specific database vars, again...
Date: 2010-04-20 19:38:15
Message-ID: 29BD5FD6-5485-465B-962C-0073D8763178@silentmedia.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-novice
On Apr 20, 2010, at 12:35 PM, Glus Xof wrote:

> 2010/4/20 Ben Chobot <bench(at)silentmedia(dot)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 ???

I could probably think of some, but why? Storing values in tables is a perfectly sensible way to allow clients to access per-database data.

In response to

Responses

pgsql-novice by date

Next:From: Glus XofDate: 2010-04-20 20:08:03
Subject: Re: [GENERAL] Specific database vars, again...
Previous:From: Glus XofDate: 2010-04-20 19:35:16
Subject: Re: [GENERAL] Specific database vars, again...

pgsql-general by date

Next:From: Glus XofDate: 2010-04-20 20:08:03
Subject: Re: [GENERAL] Specific database vars, again...
Previous:From: Glus XofDate: 2010-04-20 19:35:16
Subject: Re: [GENERAL] Specific database vars, again...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group