Hi all This topic seems to have separate discussions going on in the harbour and harbour-users lists and the two seem rather disconnected. I suggest that we might all get a lot further if we consolidate the discussion into one of the two lists. At this stage the most important questions probably relate to what users may or may not want, so on that basis I would suggest the harbour-users list but I would be happy either way.
If we were to develop an "ORM" or "OODBMS" or whatever you want to call such a thing it shouldn't require any change to the xBase language as currently implemented. I am no software theorist but I have played with an OO database - is that an ORM? - and in my opinion such an approach does provide advantages over what is already implemented in the xBase language. These presumably include: application client receives data in a more readily usable format "scatter gather" (I think that is what people call it) happens automatically automate much of the process of persistence (eg object id / primary key allocation) application can make a single request to persist an object that contains other objects (cf multiple SQL statements if using an SQL based data server) depending on how the server stores the data more flexibility in the structure of what you store Regards Doug
_______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
