Posted On May 22, 2006
- Removed VB syntax highlighting until we develop our own.
- Identifies tables with auto-increment fields and alters the insert to not attempt to insert into that field (would generate a SQL error). The DAL class also sets the ID property of the item passed in to the new auto-incremented value.
- UPDATE statements now update every field (even the primary keys). This is weird but was needed in order to satisfy cases where every column in the table is part of the primary key (ADAL used to generate invalid code in this case). I suppose this makes the execution of the update statement a little slower, but in the interest of reliability I’m willing to make the sacrifice.
- Interprets DECIMAL datatype correctly
Now With Options!
- Options menu item opens options form!
- Change root namespace (defaults to ADAL)
- Put the item classes and DAL classes in the same or separate namespaces (Defaults to “Classes” and “DAL”)
- Customizable stored procedure prefix. This allows you to easily identify which stored procedures belong to the ADAL objects (in case you need to delete either the ADAL or your own it’ll help prevent what I did when I deleted a few custom stored procedures because they all looked the same).
- Option to generate “GRANT EXECUTE” statements on the stored procedures created. No more “Execute permission denied” errors!
- Option to include validation code on varchar property gets and sets for length. ADAL throws an exception if you enable this and you try to set an items property with a value that’s too long.
Still With Problems
- There are still data types (like tinyint that ADAL doesn’t know what to do with). I’ll get to those eventually….
Download: ADAL Version 0.3