In article <4a77c4af.2060...@gmx.de>,
Andreas Kalsch writes:
> To be completely
> in context of a schema - so that I can use all tables without the
> prefix - I have to reset the search_path very often.
Why? Just say "ALTER DATABASE foo SET search_path = public, bar, baz"
once and you're done.
On 4 Aug 2009, at 7:43, Andreas Kalsch wrote:
1) I have to rewrite many lines of code = time
Why? You do know that you can set multiple schemas in search_path do
you? It's a path ;)
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no fore
Andreas Kalsch wrote:
Two causes:
1) I have to rewrite many lines of code = time
2) In MySQL I have access - with superuser rights - to _all_ existing
databases inside the installation. In Postgres I haven't.
hmm? the postgresql superuser has full access to all databases in the
cluster.
Andreas Kalsch wrote:
This is what I want to do: To refer to another database, like I can do
it in MySQL. After adding a schema with database name and refering to
it from another database I get:
ERROR: schema "test" does not exist
Adding the database name:
osm_de=# select * from test.test.n
Two causes:
1) I have to rewrite many lines of code = time
2) In MySQL I have access - with superuser rights - to _all_ existing
databases inside the installation. In Postgres I haven't.
But, of course, that are just details.
Best,
Andi
Tom Lane schrieb:
Andreas Kalsch writes:
This is
Andreas Kalsch writes:
> This is what I want to do: To refer to another database, like I can do
> it in MySQL.
You're too hung up on the word "database". MySQL "databases" are very
nearly equivalent to Postgres schemas. Use multiple schemas within
one Postgres database and be happy.
> - I hav
This is what I want to do: To refer to another database, like I can do
it in MySQL. After adding a schema with database name and refering to it
from another database I get:
ERROR: schema "test" does not exist
Adding the database name:
osm_de=# select * from test.test.newt;
ERROR: cross-data
Andreas Kalsch wrote:
Will it decrease performance to refer to other schemas?
no. the schemas are simply two namespaces in the same database.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsq
Andreas Kalsch writes:
> Will it decrease performance to refer to other schemas?
No, not to any noticeable extent. I'm not actually sure whether
parsing would be faster for an explicitly qualified reference or
an unqualified one, but in any case it'd be down in the noise
compared to planning and
Will it decrease performance to refer to other schemas?
David Fetter schrieb:
On Tue, Aug 04, 2009 at 04:41:51AM +0200, Andreas Kalsch wrote:
How is it possible to refer to another database, like:
select * from otherDatabase.nodes;
Generally, you use schemas for this. Schemas are j
On Tue, Aug 04, 2009 at 04:41:51AM +0200, Andreas Kalsch wrote:
> How is it possible to refer to another database, like:
>
> select * from otherDatabase.nodes;
Generally, you use schemas for this. Schemas are just namespaces
inside the one database.
> I have read something about schemas and I ha
How is it possible to refer to another database, like:
select * from otherDatabase.nodes;
I have read something about schemas and I have simply created an own
schema for every database with the same name, but it still does not
work. Is there anything plain and simple?
Best,
Andi
--
Sent v
12 matches
Mail list logo
