As I'm starting the work to bring SqlProvider forward to the 2.0
architecture, I'm confronted with the usual question I have when perusing
the FlexWiki code: if I see something obviously broken, should I change it
when the price is loss of backwards compatibility?
In this case, it's the database design. It's.a bit horrible. Specifically,
things like the author and the modification date are all encoded in the
"name" column. This ranks right up there with using comma-delimited fields
within the database. So I could fix it by making a proper table structure,
but it means that people are going to have to update their databases, and
I'm going to have to write a tool that does the update.
I'm inclined to just leave it the way it is. It makes my skin crawl, but I
think maybe I should just learn to live with it.
Thoughts?
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
