| From: | Glus Xof <gtglus(at)gmail(dot)com> |
|---|---|
| To: | Ben Chobot <bench(at)silentmedia(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Specific database vars, again... |
| Date: | 2010-04-20 19:35:16 |
| Message-ID: | r2q18c2d6a11004201235se742207cw79b6af47dc2766a5@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-novice |
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 ???
Glus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben Chobot | 2010-04-20 19:38:15 | Re: [GENERAL] Specific database vars, again... |
| Previous Message | Peter Hunsberger | 2010-04-20 19:32:42 | Re: Ltree - how to sort nodes on parent node |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben Chobot | 2010-04-20 19:38:15 | Re: [GENERAL] Specific database vars, again... |
| Previous Message | Ben Chobot | 2010-04-20 19:16:31 | Re: [GENERAL] Specific database vars, again... |