-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot access blob data inserted with datajoint-python
>=0.12 using mym
2.8.2
#87
Comments
Hi @Alvalunasan, one workaround is to insert NumPy data types, as Python native data types (e.g. lists) are not currently supported. |
Hi @kabilar, would you mind elaborating on how this allows you to avoid blob insertion in Python? Wouldn't you still need to put the NumPy data into a blob? Any other suggestion would be greatly appreciated -- this seems to be workflow breaking for all sizeable matlab -> python data steps as far as I can tell. |
In datajoint-python 0.12, we added support for all python data types. The old serialization protocol was |
You can prohibit python from using |
Thank you @dimitri-yatsenko! So it is not all blobs inserted with new versions of datajoint-python >= 0.12, just those with some serialized python data types? As long as I have that correct, I think it would be worth updating the error message in the next release to reflect that it is blob content and not the database datatype that is incorrect. |
That's correct. What's the current error message? |
I believe it is what is in the issue above, or something very similar.
|
Yes. A better error message would be something like, "Blobs with Python-specific data structures are not yet supported in DataJoint-Matlab." |
Feature Request
Description
Cannot access blob data that are inserted with
datajoint-python
version >=0.12 usingmym
version 2.8.2.Reproducibility
Access with
mym
version 2.8.2 does not work.Thanks!
The text was updated successfully, but these errors were encountered: