According to the book the connection string for MySql is:
mysql://username:password@localhost/test?set_encoding=utf8mb4
Maybe adding the TCP port solves the issue:
mysql://username:password@localhost:13306/test?set_encoding=utf8mb4
Kind regards,
Annet
--
Resources:
- http://web2py.com
- htt
ROFL! I don't think it's quite ready for my prime-time cash-producing
website yet. I'll definitely keep an eye on it and start playing around
with it. I need to keep you from making any decisions I don't like, after
all!
-- Joe
On Monday, September 9, 2019 at 8:48:54 PM UTC-7, Massimo Di P
Thanks Rastafarian,
I included your patch with some modifications but did not test my changes.
Please check it still woks for you.
massimo
On Monday, 9 September 2019 13:03:51 UTC-7, rastafarien wrote:
>
> Hello
>
> I have also proposed a patch to make redis work with my applications under
>
py4web supports redis. Just saying. ;-)
On Monday, 9 September 2019 09:27:20 UTC-7, Joe Barnhart wrote:
>
> I sure wish somebody could fix this. It's a real bottleneck to Python3
> adoption for my site. I tried using local storage for sessions but the
> limitation on data size makes it a no-go
I will confirm that it was redis 3 that broke this.
Jim
On Mon, Sep 9, 2019, 6:57 PM rastafarien
wrote:
> It seems that redis3 introduced a couple of nasty breaking changes.
>
> Yes it "used to" work with python2 as well, but more testing is welcomed !
>
> Stephane
>
>
> Le mardi 10 septembre
It seems that redis3 introduced a couple of nasty breaking changes.
Yes it "used to" work with python2 as well, but more testing is welcomed !
Stephane
Le mardi 10 septembre 2019 00:04:53 UTC+2, Joe Barnhart a écrit :
>
> If you're asking if it runs unmodified under Python2 I do not know as of
If you're asking if it runs unmodified under Python2 I do not know as of
yet. I would need to dust off a Python2 site, apply the patch, configure
it for redis, and test.
That might happen in a week or two as I don't have a Python2/redis site
right now so I need to do some work to create a te
Is it backward compatible as well?
-Jim
On Mon, Sep 9, 2019 at 4:54 PM Joe Barnhart wrote:
> YES. This seems to work fine in my case. It permits me to save both
> sessions and cache data to redis using Python3. Maybe we can get it
> accepted and blessed for the next release.
>
> Joe
>
> On M
YES. This seems to work fine in my case. It permits me to save both
sessions and cache data to redis using Python3. Maybe we can get it
accepted and blessed for the next release.
Joe
On Monday, September 9, 2019 at 1:03:51 PM UTC-7, rastafarien wrote:
>
> Hello
>
> I have also proposed a pat
Hello
I have also proposed a patch to make redis work with my applications under
wep2py latest ( 2.18.5-stable+timestamp.2019.04.08.04.22.03) and python3
it is attached to this post.
"onetwomany" also released a patch.
Basically
2 files are to be adjusted : redis_session.py and global.py
1/ Re
I agree
I submitted a patch but it got rejected for some reason. I don't recall
why.
-Jim
On Mon, Sep 9, 2019 at 11:27 AM Joe Barnhart wrote:
> I sure wish somebody could fix this. It's a real bottleneck to Python3
> adoption for my site. I tried using local storage for sessions but the
>
I've just downloaded web2py 2.18.5 and set the MySQL URI as follows:
uri = 'mysql://rota:rota@localhost/rota'
Web2py gives:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
Traceback (most recent call last):
File "/home/kae/web2py-2.18.5/gluon/restricted.py", line 219, in restric
I sure wish somebody could fix this. It's a real bottleneck to Python3
adoption for my site. I tried using local storage for sessions but the
limitation on data size makes it a no-go for my site. If I can't use redis
I'll have to drop back to storing sessions in files and that really sucks
f
13 matches
Mail list logo
