David RENÉ / hayamiki

…in create_table_generate_one_column and in constraint for unique
version 1.19.5

…contain the read of the current generated model version. So to do the migration to the last version no need anymore to change the version number by hand like before.

make the first hayamiki web controller outside from application (i.e. Ptah ERP)

update the generator according to the new logger call (log server) by removing read of logger_service.anubis and change the Logger by (LogLevel, String) -> One provided by host applicaiton

add the generation of global define of "vtm_vxxx" which will be load during initialization of the target application

Now phone_field has attribute for describing the phone number type like (cellphone, landline, fax, etc)

in JSON extractor check for "__HK_SHOW_STRING__" for returning the show string

add mobile and url field

replace the now by db_now which was a change in Calexium lib. This avoid confusion in compilation time with primitive now
remove the generation of delete function in profit of hk_sql_utils delete
add trigger list in attached in table
in header generation, replace read by transmit
replace the function get_name by get_mb_name, where name is the type of line row of database entry. mb means Maybe type of name, because we are not sure to retrieve the data from row given index.
add function "from_web_arg_to_type_with_default" which decode the type component from web arg and fill with default value the missing component fields

…n query without that semicolon. Hence during migration the algorithm compare the creation query (the stored query in DB  with program query), because it was always different "semicolon", the migration was always applied . That happened only when the database schema version changed.

add the management of short_name in hk_table
add the generation of the menu of application

+ generate an empty db_relations which is a list of foreign keys and their relations
+ create directories if need

add checking of the model
rename almost all db_ to hk_