True, API persistence layer should be generic as said previously mentioned. Although originally it needs to be developed based on a reference DBMS and for this DB2 looks attractive (quick results?) on first sight.
On Jan 2, 2008 8:58 PM, Bert Verhees <bert.verhees at rosa.nl> wrote: > Bert Verhees schreef: > > Thilo Schuler schreef: > >> For openEHR I will concentrate on the GUI part. Had to investigate it > >> for a uni project. > >> > >> Just wanted to let everybody know about IBM DB2 9.5, which I think is > >> a fair, "uncrippled" offer. > > > > oh > Sorry, Clicked accidently on Send > > I hope someone will pick up this subject, I would be glad to help > > So, if someone considers, DB2, or any other DB, that shoudln't matter, > there are many free DB-engines, it should not be visible in the API. > > Bert > > > > > >> On Jan 2, 2008 5:18 PM, Bert Verhees <bert.verhees at rosa.nl> wrote: > >>> Thilo Schuler schreef: > >>>> Hi everybody, > >>>> > >>>> just a short note: > >>>> > >>>> I am more a front-end person (plan to start a OSS GUI project in > >>>> 2008), although I have an vested interested in a open persistence > >>>> solution, since I would like to see an end-to-end system demonstrator > >>>> based on OSS components (GUI, kernel, persistence). IMO (and in Rong's > >>>> etc) this would really boost openEHR. > >>>> > >>>> I believe a generic persistence layer API(s) - as Tom said - is the > >>>> way to go. This won't happen in one go. So in a truely agile > >>>> development style this has to happen over several iterations, while > >>>> every iteration product has to be usable! > >>>> > >>>> The reason for this post is that I recently investigated the IBM DB2 9 > >>>> DBMS . This could be a good starting point or reference to build the > >>>> API layer on. > >>>> > >>> If you need any help? > >>> > >>> Bert > >>> > >>> _______________________________________________ > >>> openEHR-technical mailing list > >>> openEHR-technical at openehr.org > >>> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > >>> > >> _______________________________________________ > >> openEHR-technical mailing list > >> openEHR-technical at openehr.org > >> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > >> > >> > > > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical at openehr.org > > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical >
