Re: APQ (Connection Cloning)

["Warren W. Gay VE3WWG" <ve3wwg@NoSPAM.cogeco.ca>]

Georg Bauhaus wrote:
> Warren W. Gay VE3WWG <ve3wwg@nospam.cogeco.ca> wrote:
> : Why a second database connection? The reasons vary, but the following
> : reasons come to mind right away:
> 
>  Another one:
>    - one database system is very fast but is more or less a simple SQL
>      front end to a quick ISAM store or some such; another database
>      system supports transactions, subselects, partial locks, etc..
>      But this comes at a price, you cannot use the second database for
>      storing larger amounts of data quickly. Solution: use two database
>      systems for two needs.
> 
>  And another one:
>    - say, my application is a component to be integrated with other
>      components that use an existing database system. As is, mine comes
>      with its own database handling, using a different database system.
>      Can all components use the same DBMS?
>      There can be various reasons why the existing database system
>      may or may not fulfill the requirements of my component, and 
>      similarly the other components may not be happy with the DB that
>      may component uses by default.
> 
> Let alone the cost of integration, of adaption effort, and planning backup
> anew.
>  
> 
> -- Georg

I think you confused the OP's question. His was along the lines of
"why would you need more than one connection to the very same database
in one application?"

Same database product and same database/schema.  APQ certainly does
not stop anyone from messing with different products or instances
at the same time. In fact I did a lot of this successfully when
I was testing Sybase, with PostgreSQL and MySQL as comparisons on
similar tables.

-- 
Warren W. Gay VE3WWG
http://home.cogeco.ca/~ve3wwg