Drop sequence table

[millenium-codebug]

I think it's better to drop _$entity_seq table in favor of AUTO_INCREMENT attribute, since your software require mysql 5.x, 8.0 and you don't seem to support other DBMS.
This will drastically reduce the query performed to the database increasing the speed reachable by the software.
Also the use of LAST_INSERT_ID generate race condition and deadlock (more information available here).

[davidegiarolo]

hi this is a good suggestion but we can't do that because we support also other kind of dbms, ex. sqlserver and oracle, so we must keep this approach. Other scenario is that to speed up massive imports we use the trick to get first the ID and then made a bulk insert.
hope it helps

[millenium-codebug]

Which are the required version of SQL server and Oracle? I'm unable to find them in documentation.
The main problem of _$entity_seq table isn't with bulk insert script but the race condition when multiple user save something.

[millenium-codebug]

Is the project dead? I didn't recived an answer in a year about required version but thing changed a little in lifecycle of that DBMSs .
Oracle (11.2.0) will be EOL in the end of the year and SQL Server (2012) dropped the support this month.
From Oracle 12c and on SQL Server 2014, identity is supported so you don't longer need sequence table on that DBMSs.
I think that your customers already migrated to release that are not EOL because of security,breaches or GDPR requirments.

Also i think you should drop PHP5 from README since it's EOL from 3 years in a half and noticebely slower than PHP7

SQL Server

Oracle