SQLAlchemy weekly dev meetings: https://docs.google.com/document/d/1WuzZwV_aIV_ltDR3cJ-bXxXMZ9zCfr5pFSXZGZOSSQw/edit?usp=sharing
The last week was pure misery. On a scale of 1-10, the "pain" was 0 -- but "discomfort" was 9,999,999,999. I had these silicon nasal splits in each nostril that were the size of my pinky, and made me feel congested + waterboarded. I've only slept 45mins each day, and have been delirious.
They're out now though, and I can breathe and feel GREAT
btw shame we had to do 24->25 right away for a setup issue :(
mike brainstromed an example, but it's postgres specfic. i'd like to make it sqlite compatible.
tuple has no sqltype type
I usually leave them alone if I don't know how to handle them, so that mike does its thing
Does it make the listener run first?
@jvanasco when you call event.listen(), the function you give it is appended to a list of listener functions. When the event triggers, the handler iterates through this list and calls each listener function in order. Therefore if you register two event listeners A and B in that order, the "A" function will run first, then the "B" function second
with insert=True, you can say: event.listen(target, A); event.listen(target, B, insert=True), and then "B" will invoke first
with that mysql example, SQLAlchemy uses the "first_connect" listener itself to inspect the connection. so if we want to change the sql_mode, we want to change that before SQLAlchemy gets to check it
So.... "The default behavior for event handlers is to append the user defined function to an internal list of registered event listeners upon discovery. If a user registers a function with
insert=True, SQLAlchemy will insert (prepend) this function to the internal list upon discovery. This can be used to ensure certain functions run before others."
it's part of the sql standard and reserved, but not implemented
I'm using the example the user provided to show the different ways we can correctly repopulate the objects
instead of using
session_obj.commit(), I was under the impression we should be able to use session_obj.expire_all()
that doesn't work though.
that ends up loading an empty collection into baz.bars
am i missing something obvious?
oh wait, i see
baz.foos was not commited