Hello,
I just tried to create a new security module. Given the draconian database table naming rules here in our company, I decided to precreate the tables (using names conforming to our naming policy) and then select tables and fields during the module creation process, as appears to be possible. Until you finish the creation dialog and the whole thing crashes on you. Reading the error reports, I see that lots of applications fail to generate due to trying to read tables using the default table names.
Which got me into inspecting the applications in depth, with events and PHP programming, and what do I find there?
Lots and lots of references to the default tables.
Which don’t exist.
Using a connection that adhers to the minimum permissions principle (another of those compliance rules that have to be followed around here).
Soooo,
in case that’s a bug: I hereby report it.
in case that’s a feature: Thank you.
Applications that failed to compile:
app_search_sec_groups
app_retrieve_pswd
app_sync_apps
app_form_edit_users
app_form_sec_apps
But that’s not all the fun: Even those applications that do compile do have faulty SQL inside. Which means I get to manually fix every piece of SQL in the entire module and pray, that it will work afterwards.
I hope it will.
Fred
Edit:
- The predefined admin account was never created
- in the app_login application, within the SQL string a variable was not exempted from being marked as String (Examples show that variables in an SQL-String ought to look like this: [String]".$spswd."[String])