If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Freigabe der Version 0.1.8
Diese neue Version ist der großartigen Arbeit von Christian Zoffoli (xteklabs.com) geschuldet, der die OXGUI auf Italienisch übersetzt hat!
Weitere Details zu kleineren Änderungen können hier
@outlow: Die Erweiterung, dass die Anzahl der Benutzer limitiert werden kann ist machbar - da aber von der Entwicklung her dringendere Probleme anstehen wird dieser Punkt zwar in die Liste der Änderungen aufgenommen, aber mit niedriger Priorität.
When its OX based behaviour then there is really nothing to worry about here. Must be the DB admin inside me that worries when (empty) Databases gets deleted without notice. :-)
if a schema is empty, it will be deleted for performance causes. There is nothing bad about it since you can use wildcards to backup and restore database schemas.
The counter for database names will never decrease so there is no way one database can be created two times. Those databases are referenced at "configdb" so there is no way to loose track of databases and contexts.
The database version is in fact saved at the "version" table within each schema, you might want to check this. Using some OX version number for schema name is not wise since a "6.10" schema can also be used with "6.14", renaming the whole schema just for an update does not seem to be useful. Additionally, we use several updatetasks per OX update so the version number of the database is inconsistent to the OX version. Right now we're at DB Version 103 while OX is version 6.14.
The OXGUI uses only the official RMI interface to interact with the OX server - there is no direct manipulation of the database. The CLI commands 'createcontext' & 'deletecontext' show also the same behaviour. Deleting the last context, deletes also the whole DB - tested.
Perhaps, Martin Braun has a idea for this behaviour.
I still playing around with OX 6.14 and the admin GUI. Today I noticed that with deleting the last context and creating a new one, the OX MYSQL database also gets deleted and replaced with another one, incremented by 1 (example: oxdatabase_11 becomes oxdatabase_12)
I have such a feeling that this is a very bad idea in cases where a total data failure happened and a restore from backup is needed.
IMHO the database should never get deleted when the last context is deleted, just empty the DB but leave it where it is.
On creating a new context, check if there is already a OX DB existing and create the new context inside, if no DB is present, create a new one but always with the same name.
In any case the OX DB name should always stick to the same one the initial OX script on creation uses, to avoid any possible admin confusion when it comes to backup/restore with scripts.
On top (in a perfect world) I hope that the OX install script chooses the DB name according to the OX DB format (like 6.1) so admins KNOW what DB they backup, and in which OX format it is.
Werde das gleich mal installieren, nur noch schnell auf die Knie fallen und den Urheber preisen
"‘minPasswordLen’ setzt die minimale geforderte Länge der Benutzerpassworts"
DANKE !
Leave a comment:
Guest replied
@pezi:
Ich habe die Version 0.1.6 fehlerfrei installiert, leider komme ich aber nicht auf das GUI, wo soll das nach der Installation sein ?
Unter http://mein oxserver/servlet/webserver/index.html oder ähnlichem kann ich das GUI nicht finden ?
Ich hätte gerne eine Möglichkeit die mind. Länge von Passwörter irgendwo in der psoxgui Datei abzulegen. Im Moment sperrt sich die GUI gegen Passwörter mit weniger als 5 Zeichen. Würde das gerne abschalten.
Leave a comment: