Thinh Nguyen
Thinh Nguyen
Proposed solution number 1: Special feature for `filepath@store` (and potentially `attach@store` to have meta_information attached to it. Example of how that may look like: ``` @schema class NWBRaw(dj.Manual): definition =...
@guzman-raphael , the problem with `table.progress()` is that it is not taking into account entries in the jobs table (e.g. `reserved`, `error`, `ignore`).
Yeah, ideally we'd fix the `.progress()` at the table level to account for `reserve`, `error` and `ignore` jobs, but that would break backward compatibility.
You mean for the new `schema.progress()` to return a query expression instead of pandas dataframe?
A `key-source filler` solution prepared by Edgar, a decorator on any table with potentially expensive keysource, to create a corresponding key-source filler table where the key-source are computed separately. See...
I think you're suggesting some sort of a user-provided functions on insert and on fetch for `attach` type. This is very much the idea of DataJoint's AttributeAdapter feature - see...