Enrico,
the DB trigger approach sounds very exciting
to me because I really need to be sure that there is no way to
manipulate records without audit trail. I also would be very
interested in the trigger code for MySQL you mentioned.
OK. I'll append
Enrico,
In the sample MySQL trigger code of my previous message, you'll
see that I always store, in the primary table, the string username
of the most recent user to update the table. Therefore, that value
is available to the DB trigger as NEW.update_user.
Hi,
The problem here is as you say, your server doesn't know the clients
timezone. This isn't trivial to find out either. I can help you with some
pointers though:
1. ALWAYS save all times in the database in UTC. ALWAYS - never diviate
from this - one exception - if you are running a server that
Good day;
Please i need help on the issues am facing on
SESSION_EXPIRE_AT_BROWSER_CLOSE django settings.py. In my setting file i
have:
SESSION_EXPIRE_AT_BROWSER_CLOSE = True
but unfortunately, whenever my users close there browsers and open it
again, they are login automatically, which shows
Hi Mike,
thanks for that reference, I will take a look.
Enrico
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To
thanks again Mr James.
am able to solve the problem now by running the management command "python
manage.py clearsessions".
This pratically delete all the session stored on the django session
database.
so SESSION_EXPIRE_AT_BROWSER_CLOSE behave as it should now.
On Jan 22, 2017 9:41 AM, "James
Hi Fed,
the DB trigger approach sounds very exciting to me because I really need to
be sure that there is no way to manipulate records without audit trail. I
also would be very interested in the trigger code for MySQL you mentioned.
You also mentioned that you did something similar in the
Make sure you're not looking at users who already had a session cookie set
before you changed the setting. Existing cookies might not get immediately
rewritten to have the shorter expiration.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
Thanks Mr James for the urgent reply.
Even when the server and the user pc are restarted after the setting, the
situation is the same.
from the django docs; there is a section that goes :
Note
Some browsers (Chrome, for example) provide settings that allow users to
continue browsing sessions
Thinking about this topic more detailed made me realize that I also need to
track the user who performed the insert/change (delete is globally not
permitted) actions. However, that are user names managed via Django ... so
when i use DB triggers I only can track the MySQL user who is used by the
If you are going to implement JSON-RPC based on Channels, I would be happy
to participate, I suppose we will start doing this in a few week anyway.
пятница, 20 января 2017 г., 13:36:49 UTC+3 пользователь Fabien Millerand
написал:
>
> Thanks a lot for your answer Andrew.
>
> On a side note,
11 matches
Mail list logo
