Re: .NET/SQL naming convention

There seems to be a trend toward the SQL naming convention advocated by
Joe
Celko that replaces Pascal casing of column names with underscores. For
instance rather than naming a column SaleDate the trend seems to be to use
the name sale_date instead. I much prefer this convention, but in the
.NET
world the preferences seems to remain Pascal casing, at least for public
properties.

Why are you discussing this here?
This newsgroup is for classic ADO (on-topic) and not for ADO.NET
(off -topic)
I really don't understand why .NET developers insist on inflicting their
discussions on every Microsoft newsgroup particularly when Microsoft have
gone to the trouble of setting up 100's of newgroups just for .NET
development. An act of sheer cruelty.

See below

=====================================================

Microsoft has created a whole hierarchy of newsgroups, just for .NET
programming.
Newsgroups that have "dotnet" somewhere in the name, are for .NET
development
Newsgroups that _DO NOT_ have "dotnet" somewhere in the name, are for _NOT_
for .NET development

Newsgroup support on .NET:
microsoft.public.dotnet.* hieracrchy

Newsgroup support on ADO.NET:
microsoft.public.dotnet.framework.adonet

Newsgroup support on VB.NET:
microsoft.public.dotnet.framework.languages.vb
microsoft.public.dotnet.framework.languages.vb.controls
microsoft.public.dotnet.framework.languages.vb.data
microsoft.public.dotnet.framework.languages.vb.upgrade

Newsgroup support on C#:
microsoft.public.dotnet.framework.languages.csharp

Newsgroup support on Datagrid:
microsoft.public.dotnet.framework.aspnet.datagridcontrol

Newsgroup support on Windows Forms
microsoft.public.dotnet.framework.windowsforms
microsoft.public.dotnet.framework.windowsforms.control
microsoft.public.dotnet.framework.windowsforms.databinding

Stephen Howe


.