Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

mysql and sessions

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello everyone, I'm new here. Nice to meet you.

I have a question I think involves sessions. My problem I'm thinking is...

1) I have someone log into my application.
2) The user has to add his "username","password".
3) My application checks the database to see if the username/password already exists.
4) My application returns, "username"/"password" does not exist..."username/password" added to database.

MY QUESTION.
what if 5 people are logging in and checking the data at the same time. Do sessions prevent more than one user viewing or modifying the data in a single instance? I want to prevent someone adding a password that doesn't exist at the same time someone may be adding that password.

Please help me understand this process, if sessions don't take care of that and I don't have to worry then how does one implement code to prevent an error.

best regards,
Hassan





 
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My first suggestion, since it should be quick to query, and then add the
information, would be to place the code for that in a single method and
synchronize that method.
 
Hassan Schnieder
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,
Okay that's what I was thinking "sort-of". I thought that if you had your own session that would prevent 2 people access at the same time? Is that the only way to do it?

Regards,
Hassan
 
Sheriff
Posts: 13411
Firefox Browser VI Editor Redhat
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Sessions do nothing to prevent multiple threads (requests) from trying to access the same database tables simultaneously.

If your database doesn't have transaction support (not sure where mySql stands on this) then you would want to synchrnoize methods where this is a potential problem.
 
Hassan Schnieder
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

Thanks for all the replys. Synchronized connection methods it is. Time to do more homework on this.

Best Regards,
Hassan
 
Martin Simons
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Not all db interaction methods need to be synchronized. Only those where
you believe there will be a probable conflict, as in the posted example.
Also, as stated above, using transactions will also prevent alot of
problems. If you are using the InnoDB engine in MySQL then, you have
transaction support.
[ June 13, 2006: Message edited by: Martin Simons ]
 
Whose rules are you playing by? This tiny ad doesn't respect those rules:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic