Recent changes to feature-requests

SQL Express

2006-08-31T11:06:02Z

Title says it all, add sql express support...

download zip file does not extract

2004-12-20T07:36:28Z

zip file corrupt? try to download and extract. (I tried
multiple sites)

postgresql support

2004-12-20T07:29:50Z

postgresql support, maybe it already has this? maybe I
can add it if not. please send me an email. Thanks.

bradsnboar@netscape.net

Add the ability to specify naming standard for procs

2003-10-18T16:59:04Z

It would be nice to allow the ability to change the
naming convention of the stored procedures without
modifying the code. I have made a quick patch of the
2.0 source to allow this.

Recordset Paging Stored Procedures

2003-07-16T20:39:05Z

I believe the next version should have a feature to
generate a record paging feature.

An example of this idea can be found at:

http://www.4guysfromrolla.com/webtech/062899-1.shtml

The stored procedure accepts two parameters: Page and
Number of Records to return and spits out the
appropriate number of records.

This is a vital feature in a distributed app to avoid
passing around huge datasets.

Next Version?

2002-11-18T20:21:06Z

I have been doing some work with this application.
Mostly trying to create a CodeDOM version that will
support multiple languages. Having it create class
objects for the tables in addition to class collection
objects. Having the select statements return a class
collection instead of a DataReader. I am also working on
making it write a default set of TESTS for DataTier that
will test the Insert, Select, Delete, and Update methods.

Anyway, what I am getting at is that I would love to see
where version 2 is going and participate if possible.

Thanks!

VB.Net edition

2002-06-22T14:52:35Z

Hello,

Great work on the Data Tier Generator.

Hope you could find time to make one that generates
VB.NET code too.

Thanks.

- Danny Sinang

Inefficient queries

2002-04-09T08:15:40Z

Hi,

First of all: your program is a wonderful idea. I
developed a dozen of these codelibs by hand (mainly
because VB6 doesn't support inheritance) but with C#,
generating them is very OK.

I first tried to modify your code to meet my
requirements for the C# classes and the SP code, but
this was too cumbersome so I'm developing my generator
from scratch (it's a nice learning experience for
C# :)). I'll mail you the code when I'm done.

While I was investigating SQLserver 7 support (yours
does sqlserver2000 mainly), and reading the docs about
sp_help* and the INFORMATION_SCHEMA queries, I found
that the queries you're using to retrieve data from
the database, are very inefficient.

Below are the two I'm using.

1) Retrieve all keys and foreign keys:
SELECT * FROM INFORMATION_SCHEMA.KEY_COLUMN_USAGE
INNER JOIN INFORMATION_SCHEMA.TABLE_CONSTRAINTS ON
INFORMATION_SCHEMA.KEY_COLUMN_USAGE.CONSTRAINT_NAME=
INFORMATION_SCHEMA.TABLE_CONSTRAINTS.CONSTRAINT_NAME
WHERE INFORMATION_SCHEMA.KEY_COLUMN_USAGE.TABLE_NAME
= 'Tablename'

2) Retrieve all fields plus all the info needed. This
is done without the usage of syscolumns or other
system tables, since that's not recommended because
Microsoft will change these in future releases. Using
T-SQL commands is better, it will work on SQLserver7
as well.
SELECT INFORMATION_SCHEMA.COLUMNS.*,
(SELECT COLUMNPROPERTY(OBJECT_ID(@sTableName),
INFORMATION_SCHEMA.COLUMNS.COLUMN_NAME, 'IsComputed'))
AS IsComputed, (SELECT COL_LENGTH(@sTableName,
INFORMATION_SCHEMA.COLUMNS.COLUMN_NAME)) AS Length
FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_NAME
= 'tablename'

That's it, more queries not needed. You can add a
column for a ROWGUID propertie like the IsComputed
column.

For the rest: the program is very solid and well done.
However for a person who uses a different codingstyle
(and wants to use a baseclass for the C# classes) it's
very cumbersome to adjust the code. (not because you
did a bad job, these kind of programs are always
limited, no matter what).

nullable columns

2002-04-08T17:33:42Z

I am interested in this project. I have been
envisioning a such a generator for some time.

I think there are several enhancements necessary to
make this a success.

1) One way of implementing concurrency in the middle
tier is to add an UpdateDate column to every table in
the database with a default of getDate(). This column
should not be passed as an input parameter to insert
or update stored procedures. Therefore, there needs
to be a mechanism for excluding columns from the
action queries.

2) Some DBA's do NOT allow a SELECT * from [table].
Mainly because if the table structure changes, the
stored procedure has to be re-compiled. In the
generated world, this may not be an issue. But to
make the DBA's happy, it is easy to include a list of
columns to be selected in all SELECT statements.

3) The generator should provide a mechanism for
allowing nullable parameters to be passed to stored
procedures. I am not sure how this is handled can be
handled in the data tier classes and C#, but is a
necessity.

If there are any questions, feel free to contact me at
rick.mokros@e-visionsonline.com.

Use OleDb instead of Sql statements

2002-03-31T20:15:26Z

Dear developer,

Maybe it's an idea to change all the SqlConnection,
SqlCommand, Sql... statements to OleDbConnection,
OleDbCommand, OleDb.... statements. In that case you
can support Oracle databases as well.
Use "Provider=SQLOLEDB" in the connectionstring to
connect to Sql and Provider=MSDAORA for Oracle.

With kind regards,
Taco Ditiecher.