You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently using a schema to qualify the table name e.g. "SELECT * FROM schema.table" doesn't work. The parser is actually the easy part, if I just parse and ignore the schema, I get an error message of the kind "Unknown table XXX". It seems that this is because only data about the current schema is being loaded. If this is the case, what strategies might be used to get all relevant schemas? All? Lazily load the schema on first encounter? Configure schemas to load in a config file?
The text was updated successfully, but these errors were encountered:
Reading all schemas is probably not practical as it is a relatively expensive operation (I once had almost 100 schemas in my db). Lazy loading as needed would be very nice in my opinion as configuration options often tend to complicate stuff from user's point of view.
Just wondering, why is the schema cache implemented using a WeakHashMap? The entries cannot be reused between context runs anyway, and within a run a schema seems to be produced only once. Is there something I'm missing here? This is something I'm considering for the implementation of extending the schema with different schema names in addition to the default one.
Currently using a schema to qualify the table name e.g. "SELECT * FROM schema.table" doesn't work. The parser is actually the easy part, if I just parse and ignore the schema, I get an error message of the kind "Unknown table XXX". It seems that this is because only data about the current schema is being loaded. If this is the case, what strategies might be used to get all relevant schemas? All? Lazily load the schema on first encounter? Configure schemas to load in a config file?
The text was updated successfully, but these errors were encountered: