Problems with tables named "system" and "file"
My team's inherited an SQL Server database, which unfortunately has a table called "system" in it and also one called "file".
LINQPad using the built-in LINQ to SQL driver on both 7 and 8, has issues with these names and throws exceptions. The problem with "system" can be worked around by turning off "Capitalize property names", but then the one called "file" causes an exception (it works fine with capitalize on), so I can't get past this.
Does anyone have any ideas if/how I can work around this?
Having a table called "system" causes the following Exception with "Capitalize property names" on:
LINQPad.ExecutionModel.RemoteException Exception - Unable to compile typed data context: (34,17): error CS0426: The type name 'Data' does not exist in the type 'System' (30,81): error CS1503: Argument 1: Cannot convert from 'System.Data.IDbConnection' to 'string'
Having a table called "file" causes the following Exception with "Capitalize property names" off:
LINQPad.ExecutionModel.RemoteException
Exception - Unable to compile typed data context:
(50,16): error CS8124: Tuple must contain at least two elements.
(51,3): error CS1519: Invalid token '{' in class, record, struct, or interface member declaration
(125,1): error CS1022: Type or namespace definition, or end-of-file expected
Thanks
Comments
Thanks. The issue with a table called 'file' is a regression caused by the addition of the
filecontextual keyword in C# 11.This will be fixed in the next beta, later in the week.