"Zhu, Joshua" writes:
> I have the following (hypothetical) tables and their relationships (primary
> keys are in square brackets):
> [server_id] [device_id][sensor_id][property_id]
> SERVER --- 1:n --- DEVICE --- 1:n --- SENSOR --- 1:n --- PROPERTY
>
I have the following (hypothetical) tables and their relationships (primary
keys are in square brackets):
[server_id] [device_id][sensor_id][property_id]
SERVER --- 1:n --- DEVICE --- 1:n --- SENSOR --- 1:n --- PROPERTY
| |
On Thu, Jul 13, 2017 at 10:38 AM, Michael Paquier wrote:
> On Thu, Jul 13, 2017 at 7:23 PM, Jeff Janes wrote:
> >
> > I think that pg_stat_wal_receiver should be crossreferenced in
> > https://www.postgresql.org/docs/9.6/static/hot-standby.html, near the
> same
> > place which it crossreferences
I'm sorry. dotConnect for PostgreSql is able to set the schema at
connection time. This may be set as part of the connection string, or as
a dbconnection class' property.
i was in doubt because the version I'm using is somewhat old, but
decompiling it shows the property in place.
So, I will
On 7/14/2017 4:59 AM, marcelo wrote:
Now I have a related question.
Could I select a specific schema in the connection string? Say, by
example database=mydb.schemanumbertwo ?
the default search_path is $user,public
so if you connect with different SQL usernames for your different
schemas, a
On Fri, Jul 14, 2017 at 9:13 AM, marcelo wrote:
> I'll be using Devart's dotConnect. I have two alternatives at this moment
>
> a) To set the user name to the required schema. This has the (little)
> drawback that forces user configuration for every schema...
>
​With "ALTER ROLE SET" the user na
On Fri, Jul 14, 2017 at 9:01 AM, Jerry Sievers
wrote:
> marcelo writes:
>
> > Thank you.
> > Now I have a related question.
> > Could I select a specific schema in the connection string? Say, by
> > example database=mydb.schemanumbertwo ?
> >
> > I'm asking this because I will be using Devart's
I'll be using Devart's dotConnect. I have two alternatives at this moment
a) To set the user name to the required schema. This has the (little)
drawback that forces user configuration for every schema...
b) To manually do something like the JDBC driver you mention, but it
triggers some question
marcelo writes:
> Thank you.
> Now I have a related question.
> Could I select a specific schema in the connection string? Say, by
> example database=mydb.schemanumbertwo ?
>
> I'm asking this because I will be using Devart's dotConnect and Entity
> developer to access the database. I have not fu
marcelo schrieb am 14.07.2017 um 13:59:
> Could I select a specific schema in the connection string? Say, by example
> database=mydb.schemanumbertwo ?
The JDBC driver does indeed support that:
jdbc:postgresql://localhost/somedatabase?currentSchema=some_schema
I think in the backround it the
Thank you. I know that. It would be my last resort, because aside, I
need that every app user must login to be able to assign logical
privileges at the app level.
Of course, I will have my own tables of users and roles, independently
of the postgres users an roles.
I will think of it.
On 14/07
On Fri, 14 Jul 2017 08:59:13 -0300
marcelo wrote:
> Thank you.
> Now I have a related question.
> Could I select a specific schema in the connection string? Say, by
> example database=mydb.schemanumbertwo ?
>
> I'm asking this because I will be using Devart's dotConnect and Entity
> developer
Thank you.
Now I have a related question.
Could I select a specific schema in the connection string? Say, by
example database=mydb.schemanumbertwo ?
I'm asking this because I will be using Devart's dotConnect and Entity
developer to access the database. I have not full control, so I cannot
se
marcelo wrote:
The question is not trivial. Could I maintain two or three separate/distinct
"versions" of same
database using one schema for every of them?
Could some tables (in the public schema) be shared among all the schemas?
Yes and yes. In the Postgresql world, the word "schema" is may
On Fri, Jul 14, 2017 at 12:00 PM, marcelo wrote:
> The question is not trivial. Could I maintain two or three separate/distinct
> "versions" of same database using one schema for every of them?
> Could some tables (in the public schema) be shared among all the schemas?
The documentation gives a g
The question is not trivial. Could I maintain two or three
separate/distinct "versions" of same database using one schema for every
of them?
Could some tables (in the public schema) be shared among all the schemas?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make c
rihad wrote:
> Btw, can we wrap the update of datcollate &datctype and rebuilding of
> textual indices inside a transaction with effectively 0 downtime?
No. Building indexes takes time and will lock the tables
until the transaction is done.
Yours,
Laurenz Albe
--
Sent via pgsql-general mailing
Simple bind mode works nicely. Thank you.
From: Jeff Janes [mailto:jeff.ja...@gmail.com]
Sent: 14 July 2017 03:55
To: Gregory Nicol
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] LDAP authentication without OU in ldapbasedn
On Thu, Jul 13, 2017 at 2:46 AM, Gregory Nicol
mailto:gregory.
18 matches
Mail list logo