Basically it means that _only_ stored procedures can be used in model
class' operations in order to modify/access DB data, they have to be
written as generic as possible.
Also stored procedures may be used in not-login-protected pages on UI and
it means that not every DB session should start from calling
login(username, password) stored proc.
See below for more...
> In PostgreSQL, there is now session variables. Our only possibility is to
> use temporary table(s). Every database session should start from calling
> login(username,password) stored proc. After successful authentication the
> login information is stored and all the stored procs would use it
> automatically. This way, we can allow/disallow modifications of data on
> level. So, if we manage to keep the database connection after the login
> - there is now need for keeping login information. Currently, we can store
> username and password this way. Let me know if we need more session
Maybe user's first and last names too for now would be nice to have.
Authoright © Total Knowledge: 2001-2008