Currently any objects pulled into database panels have nested fields skipped. That's not ideal since there are plenty of good reasons for nested structures.
This will require bringing the Go port of shape completely up to date with the original JavaScript implementation since the Go shape library completely skips nested fields while the JS one does not.
Once we know about nested fields in the shape the DB panels can do the collapse when they ingest panels.
This means you'd be able to query like SELECT "x.y.z" FROM DM_getPanel('My JSON rows'). You'll need to quote the field though with dots in it because the column name will literally have dots in it which would conflict with the natural SQL parser unless the column is escaped.
Currently any objects pulled into database panels have nested fields skipped. That's not ideal since there are plenty of good reasons for nested structures.
This will require bringing the Go port of
shapecompletely up to date with the original JavaScript implementation since the Goshapelibrary completely skips nested fields while the JS one does not.Once we know about nested fields in the shape the DB panels can do the collapse when they ingest panels.
This means you'd be able to query like
SELECT "x.y.z" FROM DM_getPanel('My JSON rows'). You'll need to quote the field though with dots in it because the column name will literally have dots in it which would conflict with the natural SQL parser unless the column is escaped.Required for https://github.com/multiprocessio/dsq/issues/10