 |
BOOK: ASP.NET 2.0 Instant Results ISBN: 978-0-471-74951-6
 | This is the forum to discuss the Wrox book ASP.NET 2.0 Instant Results by Imar Spaanjaars, Paul Wilton, Shawn Livermore; ISBN: 9780471749516 |
|
Welcome to the p2p.wrox.com Forums.
You are currently viewing the BOOK: ASP.NET 2.0 Instant Results ISBN: 978-0-471-74951-6 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
|
|
|
|
|

May 22nd, 2008, 02:29 PM
|
|
Registered User
|
|
Join Date: May 2008
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Implementing Concurrency in BugBase
Hi,
can anybody please provide tips on implementing/dealing with concurrency in the BugBase?
Thank you.
|
|

May 22nd, 2008, 03:21 PM
|
 |
Wrox Author
|
|
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
|
|
Hi there,
You would do that the way you would do it in any other application: keep track of what has changed.
One solution is to use a WHERE clause for an UPDATE statement that includes all fields. Then when the number of affected rows is zero, you know someone else has updated the record as not all columns match anymore. You can then requery, show the user the old and new values and let them decide what to do.
In a similar approach you can use a SQL Server TimeStamp column. Then use that in the UPDATE statements to keep track of changes.
Searching for "TimeStamp sql server concurrency" should give you some interesting results.
Cheers,
Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of Beginning ASP.NET 3.5 : in C# and VB, ASP.NET 2.0 Instant Results and Dreamweaver MX 2004
Want to be my colleague? Then check out this post.
|
|

May 23rd, 2008, 10:27 AM
|
|
Registered User
|
|
Join Date: May 2008
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Imar,
As usual, your response is instant. Thank you for the attention.
Thank you for the tips, and you guided me where to start.
I will research more about this topic and build my knowledge.
|
|

May 23rd, 2008, 02:13 PM
|
|
Registered User
|
|
Join Date: May 2008
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
|
|
Imar,
after researching on this topic and with your guide, I think I've built solid understanding.
Using your first approach, I can apply this universally (to any database back-end, SQl Server, Oracle, and you name it...). I may solve most of concurrency issues for the company projects that I will work on where Oracle is the data store.
Using the alternative way, I could implement this timestamp approach in the BugBase project as this feature applies to SQL server environment.
Again, I am gaining invaluable information from you.
Having equipped the knowledge from the chapters on your book plus your guides on this forum, I will be able to develop ASP.NET applications rapidly. Hopefully, I can exceed my managers' expectation to complete the projects early so that I can prove ASP.NET development time is comparable to tools such as Oracle APEX. (in the scales of Intranet applications)
I wish good luck in your projects and hope to see more great works from you!
Regards,
|
Similar Threads
|
| Thread |
Thread Starter |
Forum |
Replies |
Last Post |
| concurrency problems |
Dorean |
Visual Studio 2005 |
1 |
September 4th, 2007 10:38 AM |
| CONCURRENCY |
pallone |
SQL Server 2000 |
13 |
December 6th, 2006 12:01 PM |
| Concurrency issues |
vitthala |
ASP.NET 2.0 Basics |
3 |
October 18th, 2006 11:42 AM |
| Concurrency problem |
sanjaymannnet |
ASP.NET 1.0 and 1.1 Professional |
0 |
July 10th, 2006 05:42 AM |
| Concurrency |
dextertoh |
Classic ASP Databases |
2 |
May 17th, 2004 12:53 AM |
|
 |