Dimitri Yatsenko

Great thinking. Generally, the full DataJoint data model envisions being able to declare foreign keys to any query expressions https://arxiv.org/abs/1807.11104. Currently, datajoint implements projection: `-> Animal.proj(subject_id='animal_id')` but not other operators...

@zfj1 Do you have a compelling use case where this feature becomes particularly useful?

In the long term, we plan to implement the low-level functionality centrally in a compiled language or on the server side. See https://github.com/datajoint/datajoint-core for the ongoing effort to shift the...

The issue is that MySQL does not have a boolean datatype. Boolean is an alias for `tinyint`, so the distinction is lost. If this is very important, We could designate...

By the way, it's safer to use `np.logical_not` rather than the `~` for `numpy` arrays if you mean logical negation.

Duplicate #936

`Raw` means different things to different people, while `binary` is specific to SQL and has its own connotations. Let's call it `bytes` similar to the byte string data type in...

`table.drop()` already cascades through all tabes that you have access to, including those in other schemas. Dropping entire schemas recursively is a rather powerful operation, perhaps too powerful. Prevention of...

I would even support a feature to not allow dropping schemas before all the tables have been dropped. This way cascading schema drops become unnecessary. cascading schema drops gives too...

Added HDF5 as one of the formats to consider. For `dj.backup`, restriction can applied to the `table` object already. Removing the `restriction` argument.