@mikkeyboi
I haven't used this in a while, but last time I did I got deprecation errors in my NPArrayBlobField due to its use of SubfieldBase.
Here (maybe) is the fix.
But while working on this, please take a look at this other example of how to make a numpy-compatible field in Django. They only bothered to get it working with PostgreSQL. The main difference is the database's backend data type.
Another idea: Maybe we should subclass SizedBinaryField instead.
@mikkeyboi
I haven't used this in a while, but last time I did I got deprecation errors in my NPArrayBlobField due to its use of SubfieldBase.
Here (maybe) is the fix.
But while working on this, please take a look at this other example of how to make a numpy-compatible field in Django. They only bothered to get it working with PostgreSQL. The main difference is the database's backend data type.
Another idea: Maybe we should subclass
SizedBinaryFieldinstead.