Best Of

This looks like an issue with the LINQ to DB driver. You can report it here:
https://github.com/linq2db/linq2db.LINQPad/issues

Filled issue https://github.com/linq2db/linq2db.LINQPad/issues/72, but it will help if you provide some details there:

• oracle version
• result of SELECT USER FROM DUAL query (no need to provide real user name, just information wether it is null, empty or some value)

Hi fellow LinqPad lovers,

After an update of our SAP OData Service, I get the error mentioned in the subject, when I try to execute a query.
Has anyone a clue what the problem could be?

bye.

thanks, that was exactly what I wanted. was looking for Util.VerticalRun() :-)

A first preview of LINQPad 7 is now available for download:
https://www.linqpad.net/LINQPad7.aspx

LINQPad 7 includes full support for C# 10 and targets .NET 6. However, it's equally at home on .NET 5 and .NET Core 3.1, thanks to new custom launchers. These launchers also bootstrap the installation of .NET 6 if no compatible runtime is installed.

LINQPad 7 also runs natively on Windows ARM64 machines such as Surface Pro X laptops. A single download includes launchers for all architectures.

There's also now full support for EF Core 6 - and all older versions down to 3.0.

Let me know how you get on!

Is there a way to get rid of this? I've come to hate this line so much. For me it's a nuisance which stands between opening LINQPad and writing code... it bothers me and I hate to have to delete it every single time.

I did a global search through the drive hoping to find some template file LINQPad uses for new scripts - no dice 😞

Have you tried maximizing the window using WIN+UP (windows key + up arrow key)? Perhaps the title bar is hidden behind the task bar, maximizing should fix that.

Hey, since this hit the release now, I just wanted to let you know that there is a typo in the startup dialog, in case you want to fix this for a future release:

I'm seeing another strange behavior that seems independent from other stuff I've found today. It seems that the mere presence of a breakpoint on a line can affect the computation.

I'm using Linqpad 6.5.5 x64

.NET Core version (host): 3.0.0
.NET Core version (queries): 3.0.0
Roslyn Version: 3.3.1-beta4-19462-11
FSharp.Compiler.Service version: 32.0.0.0

Here's the reproduction.

1. Create a C# statements script

Console.WriteLine(Math.Sqrt(1));
Console.WriteLine(Math.Sqrt(1)); // breakpoint
Console.WriteLine(Math.Sqrt(1));
Console.WriteLine(Math.Sqrt(4));
Console.WriteLine(Math.Sqrt(4)); // breakpoint 
Console.WriteLine(Math.Sqrt(4));
Console.WriteLine(Math.Sqrt(9));
Console.WriteLine(Math.Sqrt(9)); // breakpoint
Console.WriteLine(Math.Sqrt(9));

2. Set breakpoints on the appropriate lines.
3. Ensure compiler optimizations are turned off.
4. Execute the script.
5. For each breakpoint, just continue the script.

The final output (on my machine) is

1
1.0000000000000278
1
2
2.0000000000000555
2
3
3.000000000000074
3

Sorry, it's my fault😭