Daniel Espendiller

> I got tired of sqlite's performance issues. sqlite (+better-sqlite3 packages) was taken for performance reason, a nosql like "mongodb" is the wrong tool and will make this project like...

just a quick hint about "sequelize / orm". the main reason why i not took it was performance. In any case its helpful for the database schema and so on....

no plans to improve from my side - orm is a too big performance issue: that was the my reason when i started this projects; all other bots using all...

yes SQLite is every good on my side with "better-sqlite3" module and some connection parameter improvements. ~1000 queries per seconds are no problem on a small vhost with ~500 watching...

i will implement it in a more generic way. So simply by just adding and removing a given "amount". So the idea would be to store the current position size...

there is nothing wrong with SQLite its not a "temp DB" :) Maybe the external lib handling the signals stopped working at some point, just replaced it with using core...

@Wladastic which exchange are you connected to? So that i can check maybe the reconnection is not working there.

@nazar-pc i am designing a plugin for all this usages see https://github.com/Haehnchen/idea-php-toolbox feel free to jump in for discussion. some examples https://github.com/Haehnchen/idea-php-toolbox-json-files

thank you for this hint. i was thinking that the named arguments automatically were resolved by `PhpAttribute`, but its likely not the case. `name: 'app:test:test'` should work. i will fix...

@ChristianVermeulen yes, i was playing also with remote interpreter support like docker, but then stripped the first iteration, as this needed some improvements first, but will be added.