search

google-code-export / ords

Automatically exported from code.google.com/p/ords
1 stars 0 forks source link

Risk of session time-out whilst crafting a database using the schema designer #556

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Use the schema designer to create a really nice, well thought-through 
database schema
2. Try to save that schema
3. Be puzzled as to why it won't save, even though there is nothing visibly 
wrong.
4. Work out that it's because your session timed out whilst you were crafting 
the database, and now all your work is lost.

What is the expected output? What do you see instead?
It seems that using the db designer is tantamount to not interracting with your 
session, which consequently times out. We should ideally de-activate session 
time outs whilst using the schema designer, or otherwise include a warning 
message at the top of the screen telling the user to save their schema 
regularly. What actually is the time-out length at the moment?

Mark, will your changes to the way the schema designer works overcome this 
issue?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by annelies...@gmail.com on 29 Oct 2014 at 6:37

GoogleCodeExporter commented 9 years ago 
The changes brought in by Issue 442 mean that requests are being sent to the 
server every time you make a change, which should prevent the user's session 
timing out unless they leave the schema designer idle for an extended period of 
time without saving.

If we can verify that this is a session timeout issue and we're still worried 
about it, then I can mitigate it by sending a request in the background every 
(session timeout - 1 minute) to keep the session alive.

Original comment by marxjohn...@gmail.com on 13 Nov 2014 at 3:16

GoogleCodeExporter commented 9 years ago 
As there's been no more word on this issue, I'm assuming we can mark it as 
fixed?

Original comment by marxjohn...@gmail.com on 8 Jan 2015 at 11:56

GoogleCodeExporter commented 9 years ago 
I'm not sure it's fixed as such, rather that you would only encounter it if 
you'd been away from your computer for quite some time, but this is improvement 
enough that we can mark this issue as resolved I think

Original comment by jajwil...@gmail.com on 8 Jan 2015 at 1:42