I'm looking at an application that has 30+ lookup tables. By that I
mean your typical (id, description, created_on) affairs that contain
locations, zip codes, contract types and what not. Things that rarely
change, and are maintained by administrators.
It's well known that when you have many lookup tables in the schema,
eager loading is not good enough anymore, and you need to cache them
in memory as ready-made objects, to avoid abusing the database.
I'm looking at an application that has 30+ lookup tables. By that I
mean your typical (id, description, created_on) affairs that contain
locations, zip codes, contract types and what not. Things that rarely
change, and are maintained by administrators.
It's well known that when you have many lookup tables in the schema,
eager loading is not good enough anymore, and you need to cache them
in memory as ready-made objects, to avoid abusing the database.