>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".
So i have done it, all operations on database are carried out in datalayer - Database class, i just got stupid idea to make this class completely common, to have to specify only provider name, and have the work done by general DbObjects but it's unreal :-), i'm thinking now of splitting this class into 2 parts, maybe base and inherited, so that base class has common functionality completely done by generic classes, and inherited class will provide additional functionality, which must be done depending on sql server type Thanks anyway for advice -- View this message in context: http://www.nabble.com/FirebirdClientFactory-tf2257525.html#a6279879 Sent from the firebird-net-provider forum at Nabble.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
