*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/executor/execQual.c,v 1.45 1999/02/22 19:40:09 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/executor/execQual.c,v 1.46 1999/02/23 07:33:44 thomas Exp $
*
*-------------------------------------------------------------------------
*/
EV_printf("\n");
/*
- * Return a dummy tuple if the targetlist is empty .
+ * Return a dummy tuple if the targetlist is empty.
* the dummy tuple is necessary to differentiate
* between passing and failing the qualification.
*/
{
/*
* I now think that the only time this makes
- * any sence is when we run a delete query. Then
+ * any sense is when we run a delete query. Then
* we need to return something other than nil
* so we know to delete the tuple associated
* with the saved tupleid.. see what ExecutePlan
*
* Copyright (c) 1994, Regents of the University of California
*
- * $Id: tuptable.h,v 1.10 1999/02/13 23:21:29 momjian Exp $
+ * $Id: tuptable.h,v 1.11 1999/02/23 07:36:31 thomas Exp $
*
* NOTES
* The tuple table interface is getting pretty ugly.
#include <access/htup.h>
/* ----------------
- * Note: the executor tuple table is managed and manipulated by special
- * code and macros in executor/execTuples.c and tupTable.h
+ * The executor tuple table is managed and manipulated by special
+ * code in executor/execTuples.c and tupTable.h
*
* TupleTableSlot information
*
* "retrieve (EMP.hobbies.all)", a single scan may return tuples
* of many types, so now we return pointers to tuple descriptors
* along with tuples returned via the tuple table. -cim 1/18/90
+ *
+ * Tuple table macros are all excised from the system now.
+ * See executor.h for decls of functions defined in execTuples.c
+ * -jolly
+ *
* ----------------
*/
typedef struct TupleTableSlot
typedef TupleTableData *TupleTable;
-/*
- tuple table macros are all excised from the system now
- see executor.h for decls of functions defined in execTuples.c
-
- - jolly
-*/
-
#endif /* TUPTABLE_H */