On Jul 5, 2011, at 6:26 PM, Bruce Adams wrote: > There is a development policy that implies that I should > introduce java if I want to talk to the database. To my mind that is > not a good enough reason > to require supporting an extra language. The reason for the policy > is simply that the > organisation has some okay experience with hibernate but little with > database access in C++. > The logic is flawed but backed by management a few sample programs > could demonstrate > it as flawed in a way harder to refute.
Hibernate vs. SOCI is about more than choice of programming language. A significant consideration when making that choice would be understanding how you (or those in your organization) feel about SQL. SOCI is very much an SQL library. It will appeal to people who know SQL, or those who at least think learning SQL is a good idea. > I also want to use something higher level than client side libraries > and stay > database independent where possible. SOCI makes it possible to write database independent code - to the extent that you take care to ensure that the SQL that you write is database independent. For simple programs this may work just fine, though it may also lead to least-common-denominator performance. Higher level libraries that work on top of SQL may impose similar tradeoffs. Stephen ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Soci-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/soci-users
