Hi,
    I have some technical and some political questions about SOCI.

Firstly, when is the next release expected?

Looking from the outside development seems to have stalled.
However, I see there was a lot of activity around January towards releasing 
v3.1.
What's remaining to be done?

I can offer to do some basic testing of release candidates on redhat linux if 
that helps.

There seems to have been some discussion of alternative build systems as well,
such as boost jam. I'm personally a big fan of cmake. 
So to my mind the issue is closed as soci builds perfectly well with cmake.
It is trivial to get it to build rpm, deb and tarball packages. 
IMHO this is the only step missing.

What are the main targets for SOCI these days?
I originally started off with the soci RPM for Red hat 5 but this only supports 
postgresql & mysql.
The last official release 3.0 supports oracle but not ODBC.

The latest git repository would appear to support ODBC but Oracle less well.
(by the way the web-site still claims you are using CVS).

I tried Installing the oracle RPMs in their default location and running:

cmake . -DSOCI_ORACLE:=ON 
-DORACLE_INCLUDE_DIR:=/usr/include/oracle/10.2.0.4/client 
-DORACLE_LIBRARIES:=/usr/lib/oracle/10.2.0.4/client

but SOCI_ORACLE remains disabled because cmake can't find oracle.

-- Oracle:
-- WARNING:
-- Oracle not found, some libraries or features will be disabled.
-- See the documentation for Oracle or manually set these variables:
-- ORACLE_INCLUDE_DIR                       = 
/usr/include/oracle/10.2.0.4/client
-- ORACLE_LIBRARIES                         = /usr/lib/oracle/10.2.0.4/client

--
-- Oracle - SOCI backend for Oracle 10+
-- WARNING:
-- Some required dependencies of Oracle backend not found:
--    Oracle
-- Skipping
-- SOCI_ORACLE                              = OFF

The equivalent seemed to work in release 3.0 (obviously with the old build 
system).

Proceeding to build anyway I found the tests don't work on my system.

brucea@:download/soci/src>make test
Running tests...
Start processing tests
Test project /home/brucea/download/soci/src
  1/ 10 Testing soci_empty_test                  Passed
  2/ 10 Testing soci_empty_test_static           Passed
  3/ 10 Testing soci_mysql_test               ***Failed
  4/ 10 Testing soci_mysql_test_static        ***Failed
  5/ 10 Testing soci_odbc_test_access         ***Failed
  6/ 10 Testing soci_odbc_test_access_static  ***Failed
  7/ 10 Testing soci_odbc_test_postgresql     ***Failed
  8/ 10 Testing soci_odbc_test_postgresql_stat***Failed
  9/ 10 Testing soci_sqlite3_test                Passed
 10/ 10 Testing soci_sqlite3_test_static         Passed

40% tests passed, 6 tests failed out of 10

The following tests FAILED:
          3 - soci_mysql_test (Failed)
          4 - soci_mysql_test_static (Failed)
          5 - soci_odbc_test_access (Failed)
          6 - soci_odbc_test_access_static (Failed)
          7 - soci_odbc_test_postgresql (Failed)
          8 - soci_odbc_test_postgresql_static (Failed)
Errors while running CTest
make: *** [test] Error 8

>lsb_release -a
LSB Version:    
:core-4.0-ia32:core-4.0-noarch:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-ia32:printing-4.0-noarch

Distributor ID: RedHatEnterpriseClient
Description:    Red Hat Enterprise Linux Client release 5.6 (Tikanga)
Release:        5.6
Codename:       Tikanga

I've been looking at a lot of C++ database interfaces and SOCI seemed like it 
was closest to being standard & robust
but now I'm not so sure. However, the alternatives seem even more 
rusty/stagnant.

In my organisation some are pushing for JAVA for database use (& GUIs) and C++ 
for everything else.
I am looking to demonstrate that C++ is viable for database applications to 
avoid a 2 language solution. 

So I was very pleased to see this quote

http://lists.boost.org/Archives/boost/2004/10/74365.php

"The library was meant to be a simple tool for simple needs and as a
sword against anybody who got into belief that (db) programming in the
language beginning with 'J' is easier. ;) "

So far though my explorations are beginning to suggest the opposite. Which is 
disappointing.

One more vaguely related question. What is the deal with boost? 
>From perusing the thread above from 2004 it looked like SOCI would be a 
>suitable 
candidate
for inclusion in boost. Several years of development effort later on SOCI and 
several other C++ DB libraries there doesn't seem to be a clear winner and 
there 
still isn't one on the horizon for boost. 

I am probably old fashioned in thinking boost might be a stepping stone to 
getting something into a standard but the
glacial pace of c++ standardisation probably means it wouldn't be for another 
decard a least.

I wonder if anyone could make a compelling case the case of using C++ for 
database access rather than Java?

Regards,

Bruce.

------------------------------------------------------------------------------
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

Reply via email to