﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>CapableObjects Forums / ECO / General discussions  / Should defaults come with reverse engineer? / Latest Posts</title><generator>InstantForum.NET v4.1.4</generator><description>CapableObjects Forums</description><link>http://www.capableobjects.com/apps/InstantForum414/</link><webMaster>forums@capableobjects.com</webMaster><lastBuildDate>Wed, 08 Feb 2012 22:43:51 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Should defaults come with reverse engineer?</title><link>http://www.capableobjects.com/apps/InstantForum414/Topic4928-4-1.aspx</link><description>That sounds like useful information for the DbReverse-mechanism to pick up. Currently it doesn't, and I don't know if that information is avaialble in the generic mechanisms that we use when querying the database for metadata. I'll investigate.</description><pubDate>Tue, 02 Mar 2010 11:18:24 GMT</pubDate><dc:creator>Jonas Hogstrom</dc:creator></item><item><title>Should defaults come with reverse engineer?</title><link>http://www.capableobjects.com/apps/InstantForum414/Topic4928-4-1.aspx</link><description>I just reverse engineered a database.  Was looking at the constraints on the original.  I noticed a constraint to create a default value for one field.  When I looked at the Eco model, it did not seem to have that.  &lt;br&gt;&lt;br&gt;Am I not looking in the right place?  Or does Eco need to pull in that information too?</description><pubDate>Mon, 01 Mar 2010 14:14:01 GMT</pubDate><dc:creator>mtiede</dc:creator></item></channel></rss>
