Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Art datasource inconsistent between hyper and postgres writer #175

Open
DavMrc opened this issue Oct 18, 2023 · 1 comment
Open

Art datasource inconsistent between hyper and postgres writer #175

DavMrc opened this issue Oct 18, 2023 · 1 comment

Comments

@DavMrc
Copy link

DavMrc commented Oct 18, 2023

Specifications

  • Logshark version 4.2.3
  • Identical ziplog set

Running Logshark using the default hyper writer

Outcome:

  • Art.hyper is populated
  • ArtDesktop.hyper is left without records
  • Art.twbx exists and has data
  • Art Desktop [No Data].twbx exists and has no data to display

Running Logshark using postgres writer on a local db

Outcome:

  • public.Art table is not created
  • public.ArtDesktop table is created and populated with records
  • Art.twb exists but can't connect to the public.Art table as it does not exist
  • ArtDesktop [No Data].twb exists but instead has data and is usable
@TomBiztory
Copy link

Can confirm, I have the same. We were doing a complete setup with postgreSQL and the main workbook we were interested in was the Art workbook.
Unfortunately that specific one is currently not working via the postgreSQL solution...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants