Not all schemas are showing

[Vonatzki]

I'm wondering what pgweb does/checks in order for it to show user-defined schemas on the left pane.

Because right now, only the 'public' schema is showing in one of my databases when in fact I have four defined schemas in there with labels as follows:

• agg_daily
• agg_monthly
• main_daily
• main_monthly

Do note that these schemas only contain Views as of the moment.

[sosedoff]

@Vonatzki which pgweb version are you using? Also could you provide the output (redacted if needed) of http://localhost:8081/api/objects ?

[Vonatzki]

I'm not quite sure if I followed your instructions to a tee.

Going to that link churns out {"error":"Session ID is required"}.

I have two databases in my postgresql right now. The other one has its schemas showing up on pgweb just fine.

I'm running pgweb 0.9.8 on a VM with Windows 2012 Server OS

[sosedoff]

You need to start pgweb is a single session mode, connect to you db and visit the link i provided earlier.

On Aug 30, 2017, at 12:26 AM, Von Yu notifications@github.com wrote:

I'm not quite sure if I followed your instructions to a tee.

Going to that link churns out {"error":"Session ID is required"}.

I have two databases in my postgresql right now. The other one has its schemas showing up on pgweb just fine.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Vonatzki]

Logging in to the problematic DB and accessing the link, it churns out an empty JSON {}.

Logging in to my other DB and using the link, it churned out JSON containing schemas and the database objects therein.

Again, the main difference of the two DBs is that the problematic one doesn't have any Table objects in its schemas, only Views.

Also, the views located in the problematic DB are created using foreign data wrapper that links it to views located in the other DB.

Accessing those View objects via the pgweb SQL Query produces results just fine though.

[sosedoff]

Ok i will have to reproduce this issue locally.

[Vonatzki]

Thanks! The app looks promising and I like it that it's only an executable with no dependencies (Is this the Go magic people are raving about?)

I'd help you on the technicals but I don't know Go. I'll certainly learn more about in the future :)

[sosedoff]

@Vonatzki if its possible for you to send me the test dataset (raw sql dump) i'd fix it faster. My email is in my profile.

[sosedoff]

On the other hand, if you dont see the schema on the sidebar, there's a chance that it does not have any objects (tables/views/etc). I created an example schema with a single table in it and i could verify it shows up on the sidebar: https://www.dropbox.com/s/dl0jt9gghpx1g5h/Screenshot%202017-09-14%2000.10.15.png?dl=0 Same goes for the views / etc. See my previous comment: i will need a sample sql dump to reproduce your issue.

[Vonatzki]

Same goes for the views / etc. See my previous comment: i will need a sample sql dump to reproduce your issue.

Apologies for not making a prompt response on this issue.

Copy, will make an anonymized SQL dump of the problematic DB. I really think it has something to do with schemas exclusively containing foreign-wrapped Views only.

[sosedoff]

@Vonatzki can we get this wrapped up? I don't really have anything to work with to reproduce your issue, so please send some example sql data, OR close the issue if it's no longer the case.

[Vonatzki]

Hi @sosedoff, will close this issue for now. The issue still remains though but I don't have time to recreate an anonymized version of the said issue for you. Apologies.

If you have time, the tables were created with the same process like the one in this link when creating the foreign data wrapped tables:

https://robots.thoughtbot.com/postgres-foreign-data-wrapper