objecttothis

> Nope. "after database.sql" is the show stopper. The changes MUST be made to the table.sql and constraints.sql. > > The generated database.sql script is what needs to be able...

I just ran the database.sql from 3.3.9 on an empty database in MySQL 8.2.0. @SteveIreland does that database.sql work for you? I ask because it will be helpful to know...

I wonder if this is a difference between MySQL 8.4.0 and 8.2.0. I'll try to recreate in the morning. If we do find that it's an incompatibility then we would...

Thanks @SteveIreland . It sounds like they introduced this as a breaking change feature in 8.4.0 then didn't deprecate or document it. SNAFU. That said it sounds like going forward...

> So I guess my question is "Can any or all of the changes you made in constraints.sql and tables.sql be reverted and replaced with a migration script?" I'm working...

@SteveIreland @jsiddall I am using MySQL 8.2.0 against 3.4.0 and it's running without problems in a dev environment. I've also been running OSPOS 3.3.2 in a MySQL 8.0.31 environment in...

@Juan6680 This change will be a prime candidate for a 3rd party integration as it likely will not work in all countries and not all users will want it. 3.4.0...

> Thanks odiea for your help. One more question about mass import: the template expose a field "IMAGE". Kindly Ask: > > * In which DIRECTORY are the file supposed...

@jekkos alternately we could convert the current UI CSV import to be a multi-step import where we take them to the image upload form before taking them to the CSV...

From the way it was described to me, I would rename requisitions to stock transfer but maybe that's just because I'm not a logistics guy.