Martin Adámek

The `clearDatabase` calls are taking a lot of time (>500ms). Its pretty much all from the `truncate.sql` script. Will try the other suggestions from https://stackoverflow.com/questions/253849/cannot-truncate-table-because-it-is-being-referenced-by-a-foreign-key-constraint edit: ok, much better now,...

All the mapped types you added seems to be not needed, I guess that was for some initial implementation, right? Will remove them, all the tests are passing just fine...

> They are absolutely needed! I guess you are missing my point. Those types should be applied to all strings/dates, right? We dont need them if things work out of...

@UTGuy I guess I got confused by what the unicode strings mean. Initially I thought the other "regular" strings will support only ASCII, but thats probably not true? I mean...

Hello there and thanks! Unfortunately there is no list of users/companies, obviously I know about few people using it (starting with myself :]). Let's keep this open and pinned to...

Why do you think it's not possible? You can have multiple ORM instances, and let it discover different entities: ```typescript const orm1 = await MikroORM.init({ entities: [EntityA], dbName: 'db1' });...

The problem with that was reusing the entity definition, but if you will have dedicated entities for each connection, there is no problem. Btw ORM's tests are using the same...

So better to raise the issue there - or a PR right ahead. I had to implement this myself too in the mysql2 package. https://github.com/sidorares/node-mysql2/pull/1200

> Manual migration but mikro-orm try to delete my index with every new migration created, but maybe I missed something A workaround is to define any index with some name,...

In v5 you can use custom index expressions: ```ts @Index({ name: 'test_on_json_index', expression: `CREATE INDEX "test_on_json_index" ON test((data->>'somefield'), "userId");` }) ``` This works both on entity level and property level...