Mercurial > forge
comparison main/database/inst/pq_exec_params.m @ 11697:9e624fa135a1 octave-forge
Added converters for geometric types.
| author | i7tiol |
|---|---|
| date | Sun, 12 May 2013 10:19:34 +0000 |
| parents | abd563353849 |
| children | dafee4563c36 |
comparison
equal
deleted
inserted
replaced
| 11696:a69badc25735 | 11697:9e624fa135a1 |
|---|---|
| 145 ## @tab yes | 145 ## @tab yes |
| 146 ## @item interval | 146 ## @item interval |
| 147 ## @tab 3-element cell array with 8-byte-time-value (see below), int32 | 147 ## @tab 3-element cell array with 8-byte-time-value (see below), int32 |
| 148 ## (days), and int32 (months) | 148 ## (days), and int32 (months) |
| 149 ## @tab yes | 149 ## @tab yes |
| 150 ## @item point | |
| 151 ## @tab geometric point data for one point (see below) | |
| 152 ## @tab no | |
| 153 ## @item lseg | |
| 154 ## @tab geometric point data for two points (see below) | |
| 155 ## @tab no | |
| 156 ## @item line (not yet implemented by postgresql-9.2.4) | |
| 157 ## @tab as lseg | |
| 158 ## @tab yes | |
| 159 ## @item box | |
| 160 ## @tab as lseg | |
| 161 ## @tab yes | |
| 162 ## @item cirle | |
| 163 ## @tab real vector (not uint8) with 3 elements, no. 1 and 2 centre | |
| 164 ## coordinates, no. 3 radius | |
| 165 ## @tab no | |
| 166 ## @item polygon | |
| 167 ## @tab geometric point data (see below) | |
| 168 ## @tab yes | |
| 169 ## @item path | |
| 170 ## @tab structure with fields @code{closed} (boolean, is path closed?) | |
| 171 ## and @code{path} (geometric point data, see below). | |
| 172 ## @tab yes | |
| 150 ## @item any array | 173 ## @item any array |
| 151 ## @tab Structure with fields @code{data} (holding a cell-array with | 174 ## @tab Structure with fields @code{data} (holding a cell-array with |
| 152 ## entries of a type corresponding to the Postgresql element type), | 175 ## entries of a type corresponding to the Postgresql element type), |
| 153 ## @code{ndims} (holding the number of dimensions of the corresponding | 176 ## @code{ndims} (holding the number of dimensions of the corresponding |
| 154 ## Postgresql array, since this can not be deduced from the dimensions | 177 ## Postgresql array, since this can not be deduced from the dimensions |
| 176 ## seconds, if server is configured for float date/time (deprecated). | 199 ## seconds, if server is configured for float date/time (deprecated). |
| 177 ## There is no automatic conversion from an octave variable, an error is | 200 ## There is no automatic conversion from an octave variable, an error is |
| 178 ## thrown if the wrong of both types is supplied. One can use | 201 ## thrown if the wrong of both types is supplied. One can use |
| 179 ## @code{pq_conninfo} to query the respective server configuration. | 202 ## @code{pq_conninfo} to query the respective server configuration. |
| 180 ## | 203 ## |
| 204 ## geometric point data: any real array (but not of type uint8, for this | |
| 205 ## is reserved for bytea) with even number of elements. Two adjacent | |
| 206 ## elements (adjacent if indexed with a single index) define a pair of | |
| 207 ## 2D point coordinates. In converting from postgresql data, dimensions | |
| 208 ## of Octave geometric point data will be chosen to be (2, n_points). | |
| 209 ## | |
| 181 ## Octaves @code{NA} corresponds to a Postgresql NULL value (not | 210 ## Octaves @code{NA} corresponds to a Postgresql NULL value (not |
| 182 ## @code{NaN}, which is interpreted as a value of a float type!). | 211 ## @code{NaN}, which is interpreted as a value of a float type!). |
| 183 ## | 212 ## |
| 184 ## @seealso {pq_update_types, pq_conninfo} | 213 ## @seealso {pq_update_types, pq_conninfo} |
| 185 ## @end deftypefn | 214 ## @end deftypefn |