there is onother serious problem
after adding the period field to the accounting module in ONE database it is necessary to update all databases concurrently otherways no login is possible - complains of not finding period_id in the table
serious, because it is unlikely that it is possible to update all databases "at once " so it has to be done one by one and the server must be restarted to make the very database working, whilst making it impossible to login in other databases not having received the update
IMHO the idea was that the server executes the code which lives IN the database for each database, but apparently the code outside the database (from filesystem) is executed for all loaded/installed modules regardless if the db has received the last update.
hope this explains what I mean
there is onother serious problem
after adding the period field to the accounting module in ONE database it is necessary to update all databases concurrently otherways no login is possible - complains of not finding period_id in the table
serious, because it is unlikely that it is possible to update all databases "at once " so it has to be done one by one and the server must be restarted to make the very database working, whilst making it impossible to login in other databases not having received the update
IMHO the idea was that the server executes the code which lives IN the database for each database, but apparently the code outside the database (from filesystem) is executed for all loaded/installed modules regardless if the db has received the last update.
hope this explains what I mean