Index: trunk/psLib/src/db/psDB.h
===================================================================
--- trunk/psLib/src/db/psDB.h	(revision 4612)
+++ trunk/psLib/src/db/psDB.h	(revision 5136)
@@ -10,6 +10,6 @@
  *  @author Joshua Hoblitt
  *
- *  @version $Revision: 1.13 $ $Name: not supported by cvs2svn $
- *  @date $Date: 2005-07-26 20:00:57 $
+ *  @version $Revision: 1.14 $ $Name: not supported by cvs2svn $
+ *  @date $Date: 2005-09-26 21:13:16 $
  *
  *  Copyright 2005 Joshua Hoblitt, University of Hawaii
@@ -104,9 +104,9 @@
  * type is give by the psMetadataItem.type and psMetadataItem.ptype entries.  A
  * lookup table should be used to convert from PSLib types into MySQL
- * compatible SQL data types.  For example, a PS_META_STR would map to an SQL99
- * varchar.  If the value of type is PS_META_STR then the psMetadataItem.data
+ * compatible SQL data types.  For example, a PS_DATA_STRING would map to an SQL99
+ * varchar.  If the value of type is PS_DATA_STRING then the psMetadataItem.data
  * element is set to a string with the length for the field written as a text
  * string.  The value of the psMetadataItem.data element is unused for the
- * PS_META_PRIMITIVE types.  Other psMetadata types beyond PS_META_STR and
+ * PS_META_PRIMITIVE types.  Other psMetadata types beyond PS_DATA_STRING and
  * PS_META_PRIMITIVE are not allowed in a table definition.
  *
@@ -170,5 +170,5 @@
  * values, one per row.
  *
- * Currently, the "where" specification only supports the PS_META_STR type.
+ * Currently, the "where" specification only supports the PS_DATA_STRING type.
  * The string value can be a SQL match pattern, e.g. "%foo%", or an empty
  * string, e.g. "", to match NULL field values.
@@ -189,5 +189,5 @@
  * The "row" specification uses the psMetadataItem name as the column name.
  * The field values may be specified in any order.  psMetadata types beyond
- * PS_META_STR and PS_META_PRIMITIVE are not supported.  If fields are
+ * PS_DATA_STRING and PS_META_PRIMITIVE are not supported.  If fields are
  * specified in "row" that do not exist in "tableName", the insert will fail.
  *
