I have a legitimate workspace with rows deleted using sql scripting, (delete from table where field = value).
I want to confirm the deletion so I'll be using a simple select statement.
For my initial testing:
I've set up my SQLExecutor as I would to read from LIVE, ran the statement and have a row returned which is what I'd expect from an unmerged workspace.
I've repeated the process, this time plugging in the workspace name. Running the statement with the workspace param returns the same row which is not what I would expect.
I then added an Oracle Spatial Reader to replicate the process.
Running with no workspace, (LIVE) returns row as I would expect.
Running with workspace, returns no row as I would expect.
Has anyone else seen this behavior since the bug in 2015?
Thank you in advance!