Thanks Mike,
While I would rather this be a hard constraint on the database, not
enforced in python, I understand that SQLite is pretty limited in this
regard, so I'm down to try anything really. I also had the idea of using a
custom collection simply because the project already uses them heavi
Ah, I see. That makes sense. Thanks for the thorough response! We will look
elsewhere to improve our app startup time for now.
> 300 classes shouldn't be a 9 second operation.
It's 9s running with the profiling overhead. In reality, setup_mapping and
configure_mappers are closer to 2.5s each.
we might have to implement the _binary thing on our end. especially if
all the MySQL drivers have the same issue, plus Django went ahead and did
the _binary thing already making it less likely the drivers will.
that said, here's how to get _binary for now, this might be what we add on
our end:
