VARBINARY is not supported

[labor4]

Hi

I was just newly starting with python, and now DBs, so I was delighted to find your effort on github.

in the case of me working with redbeanphp on the other side of the DB...

with version 1.0.2, connecting to an existing redbeanphp-DB:
NotImplementedError: Type VARBINARY(100) is not supported

A thought...
Is there an argument of a unsolvable race condition if we use the two libraries against the same DB?
They could counter-optimize each other?
I don't know how redbeanpython works yet, but if this is as dynamic as the other, maybe not such a good idea of mine...

[adamhmetal]

NotImplementedError: Type VARBINARY(100) is not supported

Indeed VARBINARY is currently not supported.
I will leave this ticket open and try to add VARBINARY support in future.

Is there an argument of a unsolvable race condition if we use the two libraries against the same DB?
They could counter-optimize each other?
I don't know how redbeanpython works yet, but if this is as dynamic as the other, maybe not such a good idea of mine...

It depends on what library you have in mind; RebBeanPython works well with sqlalchemy, without races, and can supply each other (as described in the documentation) but is not designed to work with any other Python ORM at the same time. It can provide unexpected behaviour.

Which other library are you using currently?

[labor4]

To be fair I was not sure how to describe the nature of my foolish question.

I am hitting a MySql DB from two sides: PHP and Python.
I use RedBeanPHP from one side.
Since I develop the DB using PHP, I should not do the same from the Python side.

(Given of course RedBeanPython has similar auto-create features)

I now continue with expansion from PHP side and ingest the DB structure into an sqlalchemy.ext.automap.Base object to work with (and I cache that).

Note: I am learning...