make the webdb_create update be called webdb_create_update. it breaks things otherwis...

[mir.git] / source / mir / storage / Database.java

diff --git a/source/mir/storage/Database.java b/source/mir/storage/Database.java
index 2e8f893..79ac9ac 100755 (executable)
--- a/source/mir/storage/Database.java
+++ b/source/mir/storage/Database.java
@@ -27,10 +27,13 @@ import  mir.misc.*;
  * Treiber, Host, User und Passwort, ueber den der Zugriff auf die
  * Datenbank erfolgt.
  *
- * @version $Revision: 1.18 $ $Date: 2002/06/28 20:42:13 $
+ * @version $Revision: 1.19 $ $Date: 2002/06/29 15:44:46 $
  * @author $Author: mh $
  *
  * $Log: Database.java,v $
+ * Revision 1.19  2002/06/29 15:44:46  mh
+ * make the webdb_create update be called webdb_create_update. it breaks things otherwise. a fixme case I know..
+ *
  * Revision 1.18  2002/06/28 20:42:13  mh
  * added necessary bits in templates and Database.java to make webdb_create modifiable. make the conversion from sql/Timestamp to String more robust
  *
@@ -786,8 +789,14 @@ public class Database implements StorageObject {
                if (metadataFields.contains("webdb_lastchange")) {
                        sql.append(",webdb_lastchange=NOW()");
                }
+    // special case: the webdb_create requires the field in yyyy-mm-dd format
+    // so anything extra will be ignored. which breaks actual updating when a 
+    // a change in date is not desired but the values hash has the correct and
+    // full "webdb_create" field and value in it. solution make it so the update
+    // must be called webdb_create_update. a hack I know.. hopefully
+    // we can replace this whole layer soon. -mh
                if (metadataFields.contains("webdb_create") &&
-        theEntity.hasValueForField("webdb_create")) {
+        theEntity.hasValueForField("webdb_create_update")) {
       // TimeStamp stuff
       try {
         java.util.Date d = _dateFormatterIn.parse(