From: | Glus Xof <gtglus(at)gmail(dot)com> |
---|---|
To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Specific database vars, again... |
Date: | 2010-04-20 21:11:01 |
Message-ID: | l2l18c2d6a11004201411g3d111b7dtddcf28b751341ddc@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-novice |
2010/4/20 Thomas Kellerer <spam_eater(at)gmx(dot)net>:
> Glus Xof wrote on 20.04.2010 21:35:
>>
>> 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...
>>
>
> I don't understand why you need a column per variable.
>
> I'd use something like
>
> CREATE TABLE configuration_settings
> (
> variable_name text primary key not null,
> variable_value text
> );
>
> INSERT INTO configuration_settings
> (variable_name, variable_value)
> VALUES
> ('myfirstvar', 'Some value');
>
> INSERT INTO configuration_settings
> (variable_name, variable_value)
> VALUES
> ('mysecondvar', 'Another value');
>
I can write it as you suggested.
Thanks a lot !,
Glus
From | Date | Subject | |
---|---|---|---|
Next Message | Andy | 2010-04-20 21:15:52 | Performance impact of log streaming replication |
Previous Message | mai fawzy | 2010-04-20 20:54:03 | Rollback Failure |
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian von Bidder | 2010-04-21 08:11:48 | Re: Specific database vars, again... |
Previous Message | Thomas Kellerer | 2010-04-20 20:23:34 | Re: [GENERAL] Specific database vars, again... |