paha wrote:
> provider-aware Database class, unless it deals only with common objects like
You can write your own class, which will encapsulate some DB-specific but
little bit generic procedures (like doing backup, etc.). This allows you to
make your SW independent on specific classes, you will only change the
internals of encapsulating class. It's a widely used "solution".
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
