Well, As you might already know there are no SQL scripts in OM :)) The database is created by OpenJPA These columns are defined in JAVA code as `boolean` which actually mean this is `true/false` with default of `false`
Maybe one day I'll add something like `liquibase` to the project and maybe this will be improved But I have no estimates and see no value in this .... On Thu, 9 Apr 2020 at 04:02, Zenon Panoussis <ora...@provocation.net> wrote: > > In a mysql database, om_user has the following columns: > > MariaDB [openmeetings]> describe om_user; > > +-------------------------------+---------------+------+-----+---------+----------------+ > | Field | Type | Null | Key | Default | > Extra | > > +-------------------------------+---------------+------+-----+---------+----------------+ > > | deleted | bit(1) | NO | | NULL | > | > > | forceTimeZoneCheck | bit(1) | NO | | NULL | > | > > | show_contact_data | bit(1) | NO | | NULL | > | > | show_contact_data_to_contacts | bit(1) | NO | | NULL | > | > > The type bit(1) makes them invisible to "select * from om_user;" > and the constraint NOT NULL with default NULL adds an unnecessary > hassle to manipulating the database directly. > > It seems to me that saving 28 bits per record is absolutely not > worth it, and that it would be far better with > > > +-------------------------------+---------------+------+-----+---------+----------------+ > | Field | Type | Null | Key | Default | > Extra | > > +-------------------------------+---------------+------+-----+---------+----------------+ > > | deleted | tinyint(1) | NO | | 0 | > | > > | forceTimeZoneCheck | tinyint(1) | NO | | 0 | > | > > | show_contact_data | tinyint(1) | NO | | 0 | > | > | show_contact_data_to_contacts | tinyint(1) | NO | | 0 | > | > > > Maxim, will you please consider implementing this? > > Cheers, > > Z > > -- Best regards, Maxim
