Lorenzo Amorelli comments

Results 8 comments of


                                            Lorenzo Amorelli

Pymouse / PyMouseEvent .run() doesn't resume function after .stop() is called

I faced a cpu-hungry behavior when stop() is called. This is due to being stucked in the while loop in `reply` function (line 1483 in Xlib/protocol/rq.py). The reason here is...

Pymouse / PyMouseEvent .run() doesn't resume function after .stop() is called

> Same issue! Maybe xlib had some updates which broke pymouse. ([Here](https://github.com/SavinaRoja/PyUserInput/issues/55) the related issue) For some reason it gets stuck in the [context manager](https://github.com/SavinaRoja/PyUserInput/blob/master/pymouse/x11.py#L201). I'm currently not sure what...

is this project still under maintain?

well... it's been 2 years since this question... you can use https://github.com/moses-palmer/pynput

[Model] DateTime hardcoded format `Y-m-d H:i:s` drives to error on some databases

A possible solution would be to allow a transiction when inserting/updating from inside the Model (so we can call `SET DATEFORMAT ymd` before), but I think just choosing the desired...

DateTime hardcoded format `Y-m-d H:i:s` drives to "Error converting data type varchar to datetime"

Yes, it can but my company wants it to not be modified. It's standard notation for some locales, not for all

DateTime hardcoded format `Y-m-d H:i:s` drives to "Error converting data type varchar to datetime"

The title of this post should be edited. It's not about LoginModel only. It's about every datetime value insertion in db. The solution is to change the hardcoded 'Y-m-d H:i:s'...

DateTime hardcoded format `Y-m-d H:i:s` drives to "Error converting data type varchar to datetime"

I've just noticed that codeigniter 4 hardcodes the format too. They call "datetime" the "SQL datetime format" as you can see [here](https://github.com/codeigniter4/CodeIgniter4/blob/29c31173b6ecdd3be75ea69b3f5eb876e7b5dcbe/system/BaseModel.php#L1278) . I think it's a mistake because there...

DateTime hardcoded format `Y-m-d H:i:s` drives to "Error converting data type varchar to datetime"

> YYYY-MM-DD H:i:s is a standard. For me, it's a bad decision in your company to use something else. Not my decision and there's no turning back but as far...