In the group comp.databases.theory we had a short thread on the idea of
creating comp.databases.design. Currently questions about that seem to be
distributed in both comp.databases and comp.databases.theory.
I have looked into this somewhat and it is fairly easy to propose a group.
If there is any meaningful interest I would be willing to do the work of
being the "advocate" to get the group through the process.
Any opinions?

Signature
Kenneth Downs
java.lang.String.tcpip.usenet.posting.response.sigblock.setSig("After
finally finding the right object abd method to set the sig block, I forgot
what I wanted to say!");
--CELKO-- - 19 Nov 2004 19:38 GMT
>> I have looked into this somewhat and it is fairly easy to propose a
group. If there is any meaningful interest I would be willing to do
the work of being the "advocate" to get the group through the process.
<<
I like the idea; most of the SQL programming problems I see are the
result of kludging around bad DDL :)
--CELKO--
-P- - 19 Nov 2004 20:29 GMT
> In the group comp.databases.theory we had a short thread on the idea of
> creating comp.databases.design. Currently questions about that seem to be
[quoted text clipped - 5 lines]
>
> Any opinions?
As long as we (as a group) maintain a strict policy on redirecting off-topic posts to the appropriate forum. I wouldn't
want such a group to get polluted with more "Help me write this SQL query" questions. Creating a new group is an
attempt to separate the wheat from the chaff. Otherwise, we just got more chaff...
Just something like: "This is a more appropriate question for comp.databases.doYourOwnHomework", or something to that
effect.

Signature
Paul Horan
Sr. Architect
VCI Springfield, Mass
www.vcisolutions.com