Robert.W wrote:
Hi,
My database has a dot in the database name so part of my connection string looks like "Initial Caltalog = XX.YYYY". It seems that LLBLGen is using
YYYY.dbo.TableName in generated SQL instead of XX.YYYY.dbo.TableName.
As far as I know a dot in a database name is allowed by SQLServer 2005. I am using latest 2.0 version of LLBLGen.
Can I expect this to be fixed in 2.5 or are there other things that rely on this behavior that would get broken by such change.
There's a problem: name overwriting. The '.' is used for delimiting names. Now, IF [] are used to specify the fragments, it could be done, however people are also able to for example specify a proc name with catalog.schema.name with no [] and it also has to work. If dots are used in names, it's not able to make the distinction.
Do you really need to use the . in the catalog name?