Re: [GENERAL] Specific database vars, again...
От | Ben Chobot |
---|---|
Тема | Re: [GENERAL] Specific database vars, again... |
Дата | |
Msg-id | 29BD5FD6-5485-465B-962C-0073D8763178@silentmedia.com обсуждение исходный текст |
Ответ на | Re: [GENERAL] Specific database vars, again... (Glus Xof <gtglus@gmail.com>) |
Список | pgsql-novice |
On Apr 20, 2010, at 12:35 PM, Glus Xof wrote:
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 (andso, 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.
В списке pgsql-novice по дате отправления: