Re: Re: EDB from a system designer's viewpoint
posted by: shenpen at freemail.hu
Dear All,
thank you all for answering me. Special thanks to Mike Nelson - putting every
table in a different EDB is a very good idea, and I'm a bit ashamed I did forgot
this possibility - I'm too much accustomed to modern one-file database systems
and forgot that many ERP systems like SunSystems can work very well with a
separate files for every table. So, yes, in that case, tables can be locked
individually, and an edb could have index tables besides the main table. Of
course, one must develop a very fast sorting algorithm to mantain multiple
indexes.
About transactioning... perhaps it may be the point where the flexibility of the
data part of an EDB record - which actually scares me 
- could be very good:
so the client application would open transaction_stack.edb, hurl the stuff into
it, and close it happily. The server sees that new data appeared in the stack,
checks everything, if thinks everything is OK, locks the necessary edbs and post
it, if not, throws it back into the face of the client application... it would be
like SAP R/2, where everything you do is a predefined transaction... hmmmmm...
quite a good idea, Mike!
Best Regards to all,
Miklos Hollender
Budapest, Hungary
System Designer/Developer
P.S. Why can't Topica send me the verification letters?... maybe the .hu domain?
|
Not Categorized, Please Help
|
|
