Hi Dirk,
+1.
Could we set this goal for the 2^nd developer release ?
Luca
Dirk Kraemer wrote:
My suggestions would be:
1) throw away attribute defaultConnection.
Just because of following reason: To stay backwards compatible, a
connection without a name and without defaultConnection explicitely
set to 'true' must be taken as default connection. So that
should be the simple rule:
'It is allowed to have at most 1 connection without a name
within config file. That will be the default connection.'
The other attribute would simply make life more complicated
and irritate users.
2) Rename 'id' to dbConnectionName within dbforms-config.xml.
Same thing, same name.
3) It should not matter in which order elements
of config file appear, just values of attributes.
4) Forbid 2 connections with same name, the name is the key to access
connections.
After that someone can also check the reuse of connection, but
the above things are important to end users and easier to implement.
Regards
Dirk
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
