|
|
|
ABOUT DATALG IN GENERAL
Does the generated assembly include any error trapping?
Is there a way to use the assembly to query the database with custom built SQL queries?
Is there support for a custom WHERE clause?
Is there support for transactions?
What characters should be avoided in the table / views / stored procedures / field names?
What else is there to know about table / views / stored procedures / field names?
Is there support for 'null' values?
Is there support to update / insert / delete in views?
Is there support for default values?
ABOUT DATALG FOR MS ACCESS 2000
Are queries supported?
Are 'required' fields supported?
What kind of security does the DbConnection object supports?
ABOUT DATALG FOR MS SQL SERVER 2000
Does it work with MSDE too?
In which manner are stored procedures supported?
Can stored procedures return parameters?
Is trusted security supported?
ABOUT DATALG IN GENERAL
Does the generated assembly include any error trapping?
No. There's is no explicit error trapping in the assemblies, furthermore, there is error throwing
in certain occasions, such as when a too lengthy value is assign to a text field. We find that it
is better to keep the error trapping at a higher level to avoid errors being ignored
or "swallowed".
Is there a way to use the assembly to query the database with
custom built SQL queries?
Yes. The DbConnection class includes public methods to send custom built queries. There
are three methods for such custom queries :
- Int32 ResolveNonQuery(Data.OleDb.OleDbCommand)
- Object ResolveScalar(Data.OleDb.OleDbCommand)
- Data.OleDb.OleDbDataReader ResolveSelect(Data.OleDb.OleDbCommand)
Using the ResolveSelect without turning off the AutoConnect will cause an error. The DataReader requires
the connection to be alive while it is being read.
Is there support for a custom WHERE clause?
No. For now. It might be added in future releases. For now, only completely custom built SQL queries
are supported (see the preceding question).
Is there support for transactions?
Yes. There is full support for transactions in both MS Access and Sql Server modules.
What characters should be avoided in the
table / views / stored procedures / field names?
Other characters than alphanumeric, space, period and underscore characters may not be
used in table /... names. The generator will not allow to include such table, view or stored
procedure in the assembly. Also, a table /... name may not begin with a numeric character.
What else is there to know about table / views / stored
procedures / field names?
Since space and period characters are replaced with an underscore '_', there shouldn't be two
field of a same table where the only difference between their respective names is a space or period
character with an underscore character. The same rule applies to table, views and stored procedures
in a same database.
Is there support for 'null' values?
Yes. If a column of a table or a view allows nulls, the assembly will verify if values from that
column are null, but won't do the verification if the column cannot be null.
Is there support to update / insert / delete in views?
No, for now. We are considering adding support for modifying data in views in future releases.
Is there support for default values?
No. When inserting records, the assembly initializes all the field values to 0, an empty string, or
an empty byte array, just like a variable in your code would be if it had no significant initial
value. This is by design and corresponds to the objective creating a more transparent layer for
data development.
ABOUT DATALG FOR MS ACCESS 2000
Are queries supported?
Yes. Regular queries, such a 'join' queries a re supported and considered as 'views'. Some
queries are not supported such as 'union' queries.
Are 'required' fields supported?
Yes. But they are not enforced in the assembly.
What kind of security does the DbConnection object supports?
No security, database password security and system database security is supported.
ABOUT DATALG FOR MS SQL SERVER 2000 :
Does it also work with MSDE?
Yes. It works exactly the same way for an MSDE database than a SQL Server one.
In which manner are stored procedures supported?
Stored procedures are supported in a static way, this means that there may be only one type
of record returned for each stored procedures. Stored procedures that can return different
type of records should not be included when the assembly is generated, for the assembly could
throw an error when the procedure is called.
Can stored procedures return parameters?
Yes, parameters for stored procedures are supported in both directions.
Also note that the 'return' variable is ALWAYS ignored in the assembly, therefore it should
not be used with a such assembly.
Is trusted security supported?
Yes, this may be specified using the right constructor, or by explicitly setting the
'IntegratedSecurity' to true.
|
|
| |