Hi,
I don't think its at all off topic. Essentially yes I believe that just as
hibernate (amongst others) led to the JPA for java the C++ community should
aim to provide something as standard in C++. I recall SOCI has some ORM
features but when I last reviewed them they were less mature than those in the
database template library (DTL). SOCI has seen a flurry of development since
then but I don't know how much of that has focused on the ORM side. DTL
provides an elegant and easy to use ORM solution but on the other hand has less
of the low level access features that SOCI development has been keen to focus
on. I suppose I was aiming to minimise my exposure to SQL rather than find a
safer way to embed it in C++. But perhaps the crux of the argument would be
that it should be possible to have the schema of a class reflect the table's
schema and create an object that maps to the table such that the objects read
methods query the table and its update method insert to it. DTL does this so
well that the class may in fact represent a join or indeed any query and still
allow you to read or write as if you are
reading or writing
a non-persistent data structure (of course you aren't so you have to wary of
that).
Regards,
Bruce.
>________________________________
> From: Viacheslav Naydenov <[email protected]>
>To: Bruce Adams <[email protected]>; SOCI general discussion list
><[email protected]>
>Sent: Wednesday, April 3, 2013 1:13 PM
>Subject: Re: [soci-users] The next three big things
>
>Did you mean there should or could be an ultimate ORM interface to promote as
>a standard into C++?
>Though I doubt this is feasible, I agree with you, that a higher level of
>interaction with DB may be preferred.
>What ORM solutions for C++ are you familiar with?
>If you feel this question is a bit off topic, you can answer me direclty.
>
>02.04.2013, 15:54, "Bruce Adams" <[email protected]>:
>> Hi,
>> One key thing missing from N3612 is object relational mapping. It is not
>> appropriate in all cases but it does make working
>> with databases so much more convenient. Low level access should be possible
>> (though sometimes I question this) but not required.
>>
>> Regards,
>>
>> Bruce.
>>
>>> ----------------------------------------
>>> From: Sergei Nikulov <[email protected]>
>>> To: SOCI general discussion list <[email protected]>
>>> Sent: Thursday, March 28, 2013 3:34 PM
>>> Subject: Re: [soci-users] The next three big things
>>>
>>> 2013/3/28 Mateusz Loskot <[email protected]>
>>>> Hi,
>>>>
>>>> There has been interesting discussions about integer support
>>>> and new tests lately and I'll follow up in relevant threads in details
>>>> soon.
>>>> There is also lots of ideas and brainstorming about future plans:
>>>>
>>>> https://github.com/SOCI/soci/wiki/Roadmap
>>>>
>>>> There are three big things that will either require substantial
>>>> amount of work or will introduce major changes:
>>>>
>>>> 1. Buried headers - major structural change
>>>> Perhaps it is good chance to
>>>> - rename headers .h to .hpp,
>>>> - introduce backend specific namespaces (see Roadmap)
>>>> - clean up the repo tree a bit, evict www to separate repository
>>>> - ???
>>>>
>>>> 2. New tests
>>>>
>>>> 3. C++ integer types support
>>>>
>>>> Do we all agree to release those features in SOCI 4?
>>>>
>>>> Initially, having SVN experiences in mind, I thought it's
>>>> important to do the buried headers and all structural
>>>> changes first.
>>>> Is my concern justified, shall we do the revolution first?
>>>>
>>>> OTOH, it's Git, so we branching is effortless (tm).
>>>> We can branch off of develop and start working on
>>>> each of them in parallel.
>>>> Does anyone see any problem with that?
>>>>
>>>> The branches will be most likely long-running
>>>> branches, so I'd like to publish them in SOCI/soci repo,
>>>> i.e.
>>>> feature/buried-headers
>>>> feature/new-tests
>>>> feature/cpp-integer
>>>> Then, everyone will be able to contribute with pull requests
>>>> against those branches, review, the code, etc.
>>>>
>>>> Any comments on how we should proceed?
>>>>
>>>> p.s. It looks, development discussions wiggle between soci-users
>>>> and soci-devel. I personally have no problem with use either or both.
>>>> But, if there are subscribers on soci-users list who do not wish to receive
>>>> posts related to development process, speak up please.
>>>> Then I'll ask to move such talks to soci-devel completely.
>>>>
>>>> Best regards,
>>>> --
>>>> Mateusz Loskot, http://mateusz.loskot.net
>>>
>>> Here the database interface proposal
>>> http://isocpp.org/files/papers/n3612.pdf
>>>
>>> I think we can pick something from this paper.
>>>
>>> --
>>> Best Regards,
>>> Sergei Nikulov
>>>
>>> ------------------------------------------------------------------------------
>>> Own the Future-Intel® Level Up Game Demo Contest 2013
>>> Rise to greatness in Intel's independent game demo contest.
>>> Compete for recognition, cash, and the chance to get your game
>>> on Steam. $5K grand prize plus 10 genre and skill prizes.
>>> Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
>>> _______________________________________________
>>> soci-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/soci-users
>>
>> ,
>> ------------------------------------------------------------------------------
>> Own the Future-Intel(R) Level Up Game Demo Contest 2013
>> Rise to greatness in Intel's independent game demo contest. Compete
>> for recognition, cash, and the chance to get your game on Steam.
>> $5K grand prize plus 10 genre and skill prizes. Submit your demo
>> by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
>>
>> ,
>> _______________________________________________
>> soci-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/soci-users
>
>--
>Best regards,
>Viacheslav Naydenov.
>
>
>
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
soci-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/soci-users
