Re: [GENERAL] Specific database vars, again...
От | Thomas Kellerer |
---|---|
Тема | Re: [GENERAL] Specific database vars, again... |
Дата | |
Msg-id | hql2g3$o6v$1@dough.gmane.org обсуждение исходный текст |
Ответ на | Re: [GENERAL] Specific database vars, again... (Glus Xof <gtglus@gmail.com>) |
Ответы |
Re: [GENERAL] Specific database vars, again...
|
Список | pgsql-novice |
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');
В списке pgsql-novice по дате отправления: