So you're indeed using common filters because that's how record versioning
is implemented. In this case you can solve it by removing the reference
before deleting, however if you still want to be able to see the deleted
record on the one referencing it you can set the versioned table
No, I have just found the issue, I am using record versioning in tables,
and the child record was removed, this does not trigered the cascade,
so, the parent record was not removed and the recursive select was
failing when tries to access to a "deleted" record.
Greetings.
El 22/5/19 a las
Are you using common filters?
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
Hi, Im also having the same issue, and the fix above seemed to work -- I'm
wondering if there is an official fix for this?
On Saturday, March 2, 2013 2:55:17 PM UTC-5, Marin Pranjić wrote:
This happened to an user multiple times. No idea why it happens.
Error ticket doesn't show much, this
Hi Marin,
we've found a temporary solution for this problem until they fix it in
web2py.
Here are some code excerpts from gluon/tools.py
def login_user(self, user):
login the user = db.auth_user(id)
from gluon.settings import global_settings
if
exec('from applications.%s.modules.auth2 import Auth2' % request.
application)
Side note -- why not just:
from auth2 import Auth2
Anthony
--
---
You received this message because you are subscribed to the Google Groups
web2py-users group.
To unsubscribe from this group and stop
Hello Marin,
sorry for the late reply. I don't have your e-mail (this list doesn't show
e-mails), but I am also not sure I can provide a lot more extra info on
this.
Did you manage to look into it? Did you find anything?
Thanks!
Tamas
On Friday, March 8, 2013 4:00:24 PM UTC+1, Marin Pranjić
Hello,
I've been having this exact same problem for a long, long time.
I would also be interested in a solution, but I doubt there will be one. I
think it might be a design issue with Web2py.
Tamas
On Saturday, March 2, 2013 9:48:38 PM UTC+1, Marin Pranjić wrote:
It seems that the problem
On Friday, March 8, 2013 11:06:00 AM UTC+1, Tamas wrote:
Hello,
I've been having this exact same problem for a long, long time.
I would also be interested in a solution, but I doubt there will be one. I
think it might be a design issue with Web2py.
Tamas
I'm correct when I think that
On Friday, March 8, 2013 11:57:39 AM UTC+1, Niphlod wrote:
On Friday, March 8, 2013 11:06:00 AM UTC+1, Tamas wrote:
Hello,
I've been having this exact same problem for a long, long time.
I would also be interested in a solution, but I doubt there will be one.
I think it might be a
wait a sec who binds to that socket is apache, not web2py :D
On Friday, March 8, 2013 1:29:23 PM UTC+1, Tamas wrote:
On Friday, March 8, 2013 11:57:39 AM UTC+1, Niphlod wrote:
On Friday, March 8, 2013 11:06:00 AM UTC+1, Tamas wrote:
Hello,
I've been having this exact same problem
True, but... Apache is not raising errors, web2py is. The error message is
strange. At least we could have a nicer error if this can't be fixed.
However in my example, both instances work until i try to log in. I can use
the site without database i/o. Both instances work.
Now, why would web2py
On Friday, March 8, 2013 3:16:25 PM UTC+1, Marin Pranjić wrote:
True, but... Apache is not raising errors, web2py is. The error message is
strange. At least we could have a nicer error if this can't be fixed.
However in my example, both instances work until i try to log in. I can
use the
yep, got that part: I don't use apache and never had any problems with
multiple version running concurrently, but I guess there's a ton of users
out there using apache...I don't think that is a problem related to having
multiple web2py instances responding to the same port because that's what
Would you mind emailing me the details?
I won't promise, but I plan to look into it next week.
Dana petak, 8. ožujka 2013. 15:49:42 UTC+1, korisnik Tamas napisao je:
On Friday, March 8, 2013 3:16:25 PM UTC+1, Marin Pranjić wrote:
True, but... Apache is not raising errors, web2py is. The
It seems that the problem is because I run two web2py instances.
One runs on domain.com and the other is on testing.domain.com.
When I turn off testing instance, everything works as it should. With
testing instance turned on, production instance fails.
So... Can someone help me configure two
16 matches
Mail list logo
