Re: Embedded SQL in C#
- From: "VictorReinhart" <victora.reinhart@xxxxxxx>
- Date: 30 Dec 2005 08:27:47 -0800
<<There are all sorts of database factory patterns that would enable
multiple database support>>
That is true. I looked at NHibernate, which is a factory. It looks
like it has a lot of merit but there seems to be a substantial up-front
effort to make it work, and lots of lines of code.
Embedded SQL can be verified at compile-time. Do you know of any way
to catch an SQL error at compile time in C#? An example is invalid
column name, invalid table name, or SQL syntax error.
PowerBuilder provides an option to report SQL errors at compile time.
It is extremely helpful to find an error at compile time rather than at
runtime. And, it is very nice to be able to validate all SQL in the
entire application in a compile, if desired. This compile-time error
detection, plus the easy ability to copy and paste the SQL for unit
testing, saves a lot of time when developing an application. Also, it
makes for far fewer lines of code, which are much easier to understand.
Victor Reinhart
.
- Follow-Ups:
- Re: Embedded SQL in C#
- From: Robbe Morris [C# MVP]
- Re: Embedded SQL in C#
- From: Jon Skeet [C# MVP]
- Re: Embedded SQL in C#
- References:
- Embedded SQL in C#
- From: VictorReinhart
- Re: Embedded SQL in C#
- From: Robbe Morris [C# MVP]
- Re: Embedded SQL in C#
- From: VictorReinhart
- Re: Embedded SQL in C#
- From: Robbe Morris [C# MVP]
- Embedded SQL in C#
- Prev by Date: Re: C# user.config confusion
- Next by Date: Re: C# user.config confusion
- Previous by thread: Re: Embedded SQL in C#
- Next by thread: Re: Embedded SQL in C#
- Index(es):
Relevant Pages
|