### 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
Specifications
Running Logshark using the default hyper writer
Outcome:
Art.hyperis populatedArtDesktop.hyperis left without recordsArt.twbxexists and has dataArt Desktop [No Data].twbxexists and has no data to displayRunning Logshark using postgres writer on a local db
Outcome:
public.Arttable is not createdpublic.ArtDesktoptable is created and populated with recordsArt.twbexists but can't connect to the public.Art table as it does not existArtDesktop [No Data].twbexists but instead has data and is usable