-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
schema translate map poorly interacts with cache #5004
Copy link
Copy link
Closed
Labels
alchemy 2goes along with the 2.0 milestone to aid in searchinggoes along with the 2.0 milestone to aid in searchingbugSomething isn't workingSomething isn't workingengineengines, connections, transactions, isolation levels, execution optionsengines, connections, transactions, isolation levels, execution options
Milestone
Metadata
Metadata
Assignees
Labels
alchemy 2goes along with the 2.0 milestone to aid in searchinggoes along with the 2.0 milestone to aid in searchingbugSomething isn't workingSomething isn't workingengineengines, connections, transactions, isolation levels, execution optionsengines, connections, transactions, isolation levels, execution options
the schema translate feature takes place within the compiler and this is plainly wrong. the schema assignment should be taking place after the SQL is generated so that we only need one cache key. This is along the lines of #5002 however I think even the existing cache key mechanism used with baked etc. needs to pull the schema translate out of the compiler entirely for 1.4 and add it to the translations which occur from the ExecutionContext, along with the expanding parameter sets of logic. schema translate is intended to service many hundreds / thousands of schemas so having this occur pre-cache has to change.