Friday, February 20, 2009

Rails and Legacy Databases

I finally started to work on the actual content for the upcoming Twin Cities Code Camp. I am really struggling with a good "bad" database to use. I am looking for real world examples where you would have to work with a bad database and could not re-write it or migrate to something better.

Unfortunately for me I have one really good example (the reason for this talk) however I can not divulge the customers name and the data is sensitive make this not the ideal situation. So if anyone has any good ideas shoot them my way by contacting me at [blog] at [johnsonch] dot [com].

Thanks for the help,

1 comment:

71s8nsguft said...

One was designed to produce uniform gold sheets that have been used in the creation of cash, whereas the opposite was designed to cut beforehand fashioned sheets into strips. Over a hundred years after drawing his sketch, Da Vinci’s rolling mill is lastly delivered to life in 1590 by using two heavy cylinders to press sorts of|several types of|various kinds of} metallic, thereby altering thickness. With low carbon metal, it has much less strength than stainless steel. This kind of metallic is prone to corrosion, making it a nasty possibility for any kind of water setting. With high carbon metal, the high carbon content perfect cooling towel review material may cause brittle metallic.