Dimitri Yatsenko
Dimitri Yatsenko
We would need to provide a finer control of what is to be included in the backup. We could supply a `dj.Diagram` object in `dj.backup`. These objects already allow addition,...
@guzman-raphael A restriction in its most general form must be applied to a specific table but a restricted table can serve as a restriction to its descendants and ancestors. So...
Merging with #560
The `fetch_meta` argument in `fetch` may be unnecessary. If the user inserts the filepath with metadata, it will come back with metadata as a tuple. That would be cosistent and...
The separation is clean. If you insert a tuple, you fetch it back. It's simple, does not need to be explained. Users get back what they insert. If they choose...
Agreed. Yes, the option of skipping the metadata will be helpful.
Perhaps by default, `fetch_meta=None`, which means fetch whatever you inserted. `fetch_meta=True` returns tuples always. `fetch_meta=False` returns the paths only.
Then this would introduce the inconsistency that you insert one thing and fetch another. The default behavior needs to be most consistent.
Is there a good reason to treat metadata differently? It's all just data. Special behaviors require extra documentation and explanations. Fetching what is inserted is consistent behavior through all other...
Here is a more complete example using the custom data type for NWB objects. ```python class NWBTrace(dj.AttributeAdapter): """ custom datajoint attribute type for NWB objects in NWB files """ attribute_type...