ENODATA under windows does not use the same errno as errno.ENODATA

[skinkie]

Very strange problem. Under Windows when a dupsort key is not found via SET_RANGE, GET_CURRENT, this currently triggers an errno=38, "Filename too long". Obviously it has nothing to do with a filename, and the same error, at the same position does not trigger under Linux.

It seems that https://github.com/wtdcode/mdbx-py/blob/master/mdbx/mdbx.py#L3065 at this point ret == 38 triggers a not found. But I fail to see why MDBX uses different errno's than specified in Python's errno.

https://github.com/wtdcode/mdbx-py/blob/master/mdbx/mdbx.py#L1045

[erthink]

I am sure that in the same situation on Linux and on Windows, the MDBX_ENODATA error will be returned. But if you show a test that refutes this, then it is a bug and I will immediately start fixing it (inside libmdbx).

However, the value corresponding to MDBX_ENODATA is different on Linux (MDBX_ENODATA=ENODATA=61) and Windows (MDBX_ENODATA=ERROR_HANDLE_EOF=0x00000026=38), since MDBX_ENODATA uses the value of the corresponding native system error.