Index: /trunk/doc/pslib/ChangeLogSDRS.tex
===================================================================
--- /trunk/doc/pslib/ChangeLogSDRS.tex	(revision 3234)
+++ /trunk/doc/pslib/ChangeLogSDRS.tex	(revision 3235)
@@ -1,3 +1,3 @@
-%%% $Id: ChangeLogSDRS.tex,v 1.68 2005-02-11 21:06:02 jhoblitt Exp $
+%%% $Id: ChangeLogSDRS.tex,v 1.69 2005-02-16 00:38:40 jhoblitt Exp $
 
 \subsection{Changes from version 00 to version 01}
@@ -471,3 +471,5 @@
   \code{psPlaneDistort} into a straight spatial polynomial.
 \item fix typo in psVector typedef
-\end{itemize}
+\item add limit param to psDBSelectRows()
+\item change psDBUpdateRows() & psDBDeleteRows() to return signed values
+\end{itemize}
Index: /trunk/doc/pslib/psLibSDRS.tex
===================================================================
--- /trunk/doc/pslib/psLibSDRS.tex	(revision 3234)
+++ /trunk/doc/pslib/psLibSDRS.tex	(revision 3235)
@@ -1,3 +1,3 @@
-%%% $Id: psLibSDRS.tex,v 1.180 2005-02-11 21:06:02 jhoblitt Exp $
+%%% $Id: psLibSDRS.tex,v 1.181 2005-02-16 00:38:40 jhoblitt Exp $
 \documentclass[panstarrs,spec]{panstarrs}
 
@@ -4329,5 +4329,5 @@
 entries.  A lookup table should be used to convert from PSLib types
 into MySQL compatible SQL data types.  For example, a
-\code{PS_META_STR} would map to an SQL99 varchar.  If value of
+\code{PS_META_STR} would map to an SQL99 varchar.  If the value of
 \code{type} is \code{PS_META_STR} then the \code{psMetadataItem.data}
 element is set to a string with the length for the field written as a
@@ -4360,5 +4360,5 @@
 
 \begin{verbatim}
-    psArray *psDBSelectRows(psDB *dbh, const char *tableName, psMetadata *where);
+    psArray *psDBSelectRows(psDB *dbh, const char *tableName, psMetadata *where, const psU64 limit);
 \end{verbatim}
 
@@ -4402,5 +4402,5 @@
 
 \begin{verbatim}
-    psU64 psDBUpdateRows(psDB *dbh, const char *tableName, psMetadata *where, psMetadata *values);
+    psS64 psDBUpdateRows(psDB *dbh, const char *tableName, psMetadata *where, psMetadata *values);
 \end{verbatim}
 
@@ -4408,14 +4408,15 @@
 with the value indicated by \code{where} (note that this is only allows very
 limited use of SQL99's ``where'' semantics).  The number of rows modified is
-returned.  If there are multiple psMetadataItems in \code{where} then each item
-should be considered as an additional constraint.  e.g.  ``where foo = x and
-where bar = y''
-
-\begin{verbatim}
-    psU64 psDBDeleteRows(psDB *dbh, const char *tableName, psMetadata *where);
+returned.  A negative value is return to indicate an error. If there are
+multiple psMetadataItems in \code{where} then each item should be considered as
+an additional constraint.  e.g.  ``where foo = x and where bar = y''
+
+\begin{verbatim}
+    psS64 psDBDeleteRows(psDB *dbh, const char *tableName, psMetadata *where);
 \end{verbatim}
 
 Delete the rows that are matched by \code{where} using the same semantics for
-\code{where} as in psDBUpdateRow().
+\code{where} as in psDBUpdateRow().  A negative value is returned to indicate an
+error.
 
 \subsection{FITS I/O Functions}