themsaid/wink

Error with postgresql

MahmoudDevo opened this issue · 5 comments

Hi,
I use wink with POSTGRESQL 9.3 AND 12.3 ;

My composer.json:

 "require": {
        "php": "^7.3|^8.0",
        "fideloper/proxy": "^4.4",
        "fruitcake/laravel-cors": "^2.0",
        "guzzlehttp/guzzle": "^7.0.1",
        "laravel/framework": "^8.12",
        "laravel/jetstream": "^2.2",
        "laravel/tinker": "^2.5",
        "themsaid/wink": "^1.2"
    },
    "require-dev": {
        "facade/ignition": "^2.5",
        "fakerphp/faker": "^1.9.1",
        "laravel/sail": "^1.0.1",
        "mockery/mockery": "^1.4.2",
        "nunomaduro/collision": "^5.0",
        "phpunit/phpunit": "^9.3.3"
    },

When i do: http://127.0.0.1:8000/wink

Illuminate\Database\QueryException
SQLSTATE[22P02]: Invalid text representation: 7 ERREUR: syntaxe en entrée invalide pour l'entier : « 7a2ae1d5-7252-4282-867c-ea17f6d2d735 » (SQL: update "sessions" set "payload" = YTo1OntzOjY6Il90b2tlbiI7czo0MDoibmpvbElnWDNINW1SYmF5bjZVSXZ1dGthMTJ6SHZWMjVaSlZiSjljVSI7czozOiJ1cmwiO2E6MTp7czo4OiJpbnRlbmRlZCI7czoyNjoiaHR0cDovLzEyNy4wLjAuMTo4MDAwL3dpbmsiO31zOjk6Il9wcmV2aW91cyI7YToxOntzOjM6InVybCI7czoyNjoiaHR0cDovLzEyNy4wLjAuMTo4MDAwL3dpbmsiO31zOjY6Il9mbGFzaCI7YToyOntzOjM6Im9sZCI7YTowOnt9czozOiJuZXciO2E6MDp7fX1zOjUxOiJsb2dpbl93aW5rXzU5YmEzNmFkZGMyYjJmOTQwMTU4MGYwMTRjN2Y1OGVhNGUzMDk4OWQiO3M6MzY6IjdhMmFlMWQ1LTcyNTItNDI4Mi04NjdjLWVhMTdmNmQyZDczNSI7fQ==, "last_activity" = 1620006676, "user_id" = 7a2ae1d5-7252-4282-867c-ea17f6d2d735, "ip_address" = 127.0.0.1, "user_agent" = Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0 where "id" = lcZJxWlAGTYbIqFG0PA9qFRx8jM5tkVrXMDjzxtT)

Thank you

Did you ever get this resolved? I'm having the same problem.

Hi,
no it doesn't work and I canceled the package .

I found a workaround. But It's not ideal.

On the Sessions table, change the user_id datatype to varchar.

I'm not sure why this is necessary, but it got me over the hump for now.

I am running this with Postgres 12.2 and NOT having any issue at all.
Works fine for me.

Is the issue specific to the mentioned Postgres versions only (including 12.3, but not 12.2) or with any version?

Hi,
v1.3.1 version works fine.
Thank you