Announcement

Migration of this forum

Dear users of this forum,

we are pleased to inform you that we will be updating the software behind this forum in the near future.

Existing posts, users and categories will remain untouched.

Important:

  • Each user will need to reset their password.
  • Please select "I forgot my password".
  • Enter the email address you used to register in this forum.
  • You will receive an email with a link to set a new password.
  • Please choose a new (secure) password and confirm the process.

We will keep you informed in the pinned thread.

Kind regards,
Your ReportServer Team


Migration des Forums

Liebe Nutzer dieses Forums,

wir freuen uns, euch mitteilen zu können, dass wir in naher Zukunft die Software hinter diesem Forum aktualisieren werden.

Existierende Beiträge, Nutzer und Kategorien bleiben weiterhin bestehen!

Wichtig:

  • Jeder Nutzer muss sein Passwort neu vergeben.
  • Wählt dazu einfach "Ich habe mein Passwort vergessen".
  • Gebt die E-Mail-Adresse ein, mit der ihr registriert seid.
  • Ihr erhaltet eine E-Mail mit einem Link zur Passwortvergabe.
  • Bitte wählt ein neues (sicheres) Passwort und bestätigt den Vorgang.

Wir halten euch im angepinnten Beitrag auf dem Laufenden!

Mit vielen Grüßen
Euer ReportServer Team

#1 2017-05-03 01:07:22

mark
Member
Registered: 2017-05-03

working with postgres schemas

Hello

My data is on greenplum DB, I'm using the following connection sting to create a new data source
jdbc:postgresql://192.168.1.41/data?searchpath=2016-data

data is the DB and 2016-data is the schema where my data is

The problem is that when I write the sql for my queries/reports if I do not use the notation schema.table or schema.table.column
Reportserver does not return any result

I also tried to specify the path in the query itself

search_path=2016-data;
select * from etc;

Again no luck

The only way to get results is to use the schema.table etc. unfortunately this add quite a bit of complexity as we have some very long and elaborated queries with many dozens of tables and hundreds of columns etc

Any idea on what I could do to be able to avoid the schema.table notation?

Thanks heaps
Mark

Offline

#2 2017-05-03 06:47:51

IF_Eduardo
Administrator
Registered: 2016-11-01
Website

Re: working with postgres schemas

Hi Mark,

you can also try this:
jdbc:postgresql://192.168.1.41/data?currentSchema=2016-data

If this doesn't work, please try a newer jdbc driver and let us know.

Cheers,
Eduardo

Offline

#3 2017-05-03 06:49:26

IF_Eduardo
Administrator
Registered: 2016-11-01
Website

Re: working with postgres schemas

Hi Mark,

this should also work:
ALTER USER user_name SET search_path to '2016-data'

Cheers,
Eduardo

Offline

#4 2017-05-04 13:33:34

mark
Member
Registered: 2017-05-03

Re: working with postgres schemas

Hello

I will try both and will update you

Thanks!

Offline

#5 2017-05-05 00:01:50

mark
Member
Registered: 2017-05-03

Re: working with postgres schemas

Hello Eduardo

Thanks it works great!

I tried many other connection strings without luck by this one does the job

edulid wrote:

you can also try this:
jdbc:postgresql://192.168.1.41/data?currentSchema=2016-data

Again thanks heaps

Mark

Offline

Board footer

Powered by FluxBB