Oleg Kobchenko wrote: > Another use case, which I hesitate to consider automatable, is importing > hierarchies allowing errors within a single transaction, such as accounts > and their operations. One way to do this is to use one transaction, > prepare several statements, and cycle through items of the same type > for the same ancestors. This should gain speed, but smells like overdesign. > The other two more reasonable approaches are used in making > Phrase DB in JHP demo.
Not so sure if I understand correctly as I did not use JHP. Perhaps you meant JHP as a web server accepting independent requests need a way to serialise error message to the matching channel. If this is the case then it may be solved by combining return code with result for each request. APLX takes this approach. It also provides a native access to ibm db2 using the same interface as odbc. Developer Productivity with APLX Version 3.0 and SQL by Ajay Askoolum http://www.vector.org.uk/archive/v214/ajay214.htm -- regards, bill ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
