Best Of

This should now be fixed in 6.10.11. Let me know how you get on.

Thanks for reporting - it no longer throws in 6.10.11. Let me know how you get on.

Stored procedures are not part of the mapping, but you can still list them via Reflection:

typeof (TypedDataContext).GetMethods(BindingFlags.Public | BindingFlags.Instance | BindingFlags.DeclaredOnly).Where (m => !m.IsSpecialName)

It looks like a number of those options don't work when selected from the menu. I'll look into what's going on.

In LINQPad 6, you can call xx.Dump (noTotals:true);

The problem I believe is caused by the period in the schema name. I'll get a fix into the next LINQPad beta build.

You'll need to keep running LINQPad 5 if you need a driver that's not supported in LINQPad 6. However, the most popular drivers have LINQPad 6 equivalents. In place of the IQ Driver, there's is now a built-in EF Core driver which supports Postgres, as well as SQL Server, Oracle, SQLite and MySQL. The LINQ-to-DB driver has been ported to LINQPad 6, as has the Azure Storage driver.

In the connection properties dialog, it lets you choose a version of the Oracle provider - either latest release or latest beta. Which one have you chosen? Does it make any difference if you choose the other option?

The workaround for LINQPad 5:

// public class UserQuery {

  void Main()
  {
    // Main method...
    var x = new Foo.Bar();
  }

} // end of UserQuery class

namespace Foo
{
  class Bar
  {
  }

Good call. This is easy to fix, so it should make it into the next build.