Sorry it took me this long to reply. See comments inline:
Andrus wrote:
Thank you for foreign key suggestions. I started to study them.
I changed the TestSecurityManager class to fix the following issues:
1. Dabo Application superuser password is stored in client computer
2. Dabo Application login-ins to database as super-user always
I don't fully understand... the Dabo Application logs in to the database
as whatever user that you specify in the cnxml file. If this is a
superuser, then yes it will log in as the superuser.
Yes, the password can be stored -- and is, by default -- in the cnxml
file, although it is behind simple encryption.
3. Login failure message from backed is not displayed.
Ok.
4. It is not possible to send custom commands to database server at
application startup
What kind of commands do you want to send?
I added the following code to the end of TestSecurityManager
validateLogin() procedure:
from dabo.db.dConnectInfo import dConnectInfo
from dabo.db.dConnection import dConnection
ci = self.Application.dbConnectionDefs["[EMAIL PROTECTED]"]
ci.Name = "mainConnection"
ci.User = user
ci.PlainTextPassword = password
import exceptions
try:
self.connection = dConnection(ci)
except exceptions.StandardError, err:
dabo.ui.exclaim( str(err))
return False
return True
Also, I myForms MyFormBase class I changed afterInit method to
self.connection = dabo.dAppRef.SecurityManager.connection
Is is no more required to store user name and password in connection
definition file.
This is a good idea...
It it reasonable to add those changes to sample class ?
Can you provide a patch for me to review?
--
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
