Wouldn't it be better if it was just null if we don't know the mime type? Where would a mime type that isn't in the database come from anyway?
-David On Jan 22, 2007, at 5:47 PM, [EMAIL PROTECTED] wrote:
Author: sichen Date: Mon Jan 22 16:47:34 2007 New Revision: 498877 URL: http://svn.apache.org/viewvc?view=rev&rev=498877 Log:Removing fk constraint on Content and DataResource. This constraint is a bad idea because mime types are open ended. Fixes bug where attempting to upload esoteric files like .patch files would crash because the MimeType isn't there.Modified: ofbiz/trunk/applications/content/entitydef/entitymodel.xml Modified: ofbiz/trunk/applications/content/entitydef/entitymodel.xmlURL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/content/ entitydef/entitymodel.xml?view=diff&rev=498877&r1=498876&r2=498877 ====================================================================== ======== --- ofbiz/trunk/applications/content/entitydef/entitymodel.xml (original) +++ ofbiz/trunk/applications/content/entitydef/entitymodel.xml Mon Jan 22 16:47:34 2007@@ -114,7 +114,7 @@<relation type="one" fk-name="CONTENT_PRIVENM" title="Privilege" rel-entity-name="Enumeration"> <key-map field-name="privilegeEnumId" rel-field- name="enumId"/></relation>- <relation type="one" fk-name="CONTENT_MMTP" rel-entity- name="MimeType">+ <relation type="one-nofk" rel-entity-name="MimeType"> <key-map field-name="mimeTypeId"/> </relation><relation type="one" fk-name="CONTENT_CHST" rel-entity- name="CharacterSet">@@ -757,7 +757,7 @@<relation type="one" fk-name="DATA_REC_DTSRC" rel-entity- name="DataSource"><key-map field-name="dataSourceId"/> </relation>- <relation type="one" fk-name="DATA_REC_MMTP" rel-entity- name="MimeType">+ <relation type="one-nofk" rel-entity-name="MimeType"> <key-map field-name="mimeTypeId"/> </relation><relation type="one" fk-name="DATA_REC_CHST" rel-entity- name="CharacterSet">
smime.p7s
Description: S/MIME cryptographic signature
