Hi guys! After thinking a little about the order problem, it could be an important problem. Imagine the user that introduces the task in an order and when it loads the tasks from the database, she receives the tasks in a different order. It will be crazy! Also I have been thinking about other ways to test that the data is complete. I take the XML storage as the reference always and the goal is that all the information in the XML are also in the database. To test that everything is ok, we can create a project with all the different kinds of info in it, the same it as XML and also in the database. We can create then a new project and load the data from the database, and save it as a XML file. Then we can compare the original XML file with this new file generated from the data in the database. If any information isn't stored in the database, we will see it. Also, I plan to start to think a little in the MySQL backend. You know that MySQL have no transactions, at least in 3.2x series, and also we have not foreign keys and other data integrity features that are now used in the Postgresql backend. Cheers El dom, 28-12-2003 a las 13:45, Alvaro del Castillo escribió: > Hi guys! > > I have find sometime this weekend to do the migration from the libpq > library from Postgres to the more general libgda library in the Planner > database backend. > > 1. I attach to this email: > > 1.1. The patch to apply to the current planner CVS > 1.2. The document of quality assurance in the migration > > 2. The work that needs to be done is: > > 2.1. Complete the error handling in a better way > 2.2. Check all the code style > 2.3. Check GDA for use UTF8 > 2.4. Complete the patch with all the ChangeLogs ;-) > > Cheers and happy new year! > > -- Alvaro > > ______________________________________________________________________ > _______________________________________________ > Planner-dev mailing list > Planner-dev lists imendio com > http://lists.imendio.com/mailman/listinfo/planner-dev
Attachment:
signature.asc
Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente