LINQPad5 - Schema doesn't load when changing connections after a cold start
Options
Seems like a regression but the Schema doesn't seem to load for new queries after a cold start.
If the connection is changed, rather than the intellisense info loading, you see "Schema loading - try again shortly" but it will never complete. Attempting to execute will eventually load the schema. If the schema was loaded in a previous run, then it will be available immediately.
This wasn't an issue in LINQPad4. In fact, it points out that a connection should be selected when writing linq queries ("Select a database connection in the dropdown above") or load it immediately (or was really fast), not so in 5.
If the connection is changed, rather than the intellisense info loading, you see "Schema loading - try again shortly" but it will never complete. Attempting to execute will eventually load the schema. If the schema was loaded in a previous run, then it will be available immediately.
This wasn't an issue in LINQPad4. In fact, it points out that a connection should be selected when writing linq queries ("Select a database connection in the dropdown above") or load it immediately (or was really fast), not so in 5.
Comments
-
Thanks for reporting - this is now fixed in 5.0.7
-
Sorry, Joe, it doesn't look like it took. The schema still doesn't load when selecting a connection from the dropdown. Is there anything else I could do to help debug this?
Running on 5.00.07 AnyCPU.
-
Oops - looks like this fix didn't make 5.0.7. I've uploaded a new beta - it should now be resolved.
-
Looks good Joe, thanks.
