Just not to be buried under messages :-(
Pritpal Bedi wrote: > > Hello Przemek > > I am developing a RDBMS RDD (real-time) on top of USRRDD. > So far so good, thanks for this superb tool. > > Now MT is in picture, but the RDBMS communication layer is not > MT safe. I have guarded all functions in the communication layer > with hb_mutexLock()/hb_mutexUnlock() and it is working great. > > Now the real issue: > I have built the RDD on back of nWA which needs to be unique > for each table open. Now in MT every thread has common nWAs > and this is breaking my methodology. Thou I can issue like: > > STATIC nWorkArea := 0 > nWorkArea++ > > SELECT( nWorkArea ) > USE 'SomeTable' SHARED > > This gives me unique workarea for each new table opened, but you > know it has a lot of limitations: > 1) I can exhaust maximum WAs > 2) Workareas cannot be reused once table is closed > 3) MOST IMPORTANT: I have to change the sources whereever a table is > opened. > > My feature request: > Is it possible that Harbour defines something like: > SET( _SET_WORKAREAS, lUnique ) > and internally nWA is fetched form common pool if NEW clause is included > in USE. > > I will be saved days of work just to change the sources. > > Regards > Pritpal Bedi > -- View this message in context: http://www.nabble.com/MT---WorkAreas---A-Feature-Request-tp20268713p20284099.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
