/usr/share/doc/ruby-pg/rdoc/PG/Constants.html is in ruby-pg 0.17.1-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 | <!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>module PG::Constants - pg: The Ruby Interface to PostgreSQL</title>
<link href="../fonts.css" rel="stylesheet">
<link href="../rdoc.css" rel="stylesheet">
<script type="text/javascript">
var rdoc_rel_prefix = "../";
</script>
<script src="../js/jquery.js"></script>
<script src="../js/navigation.js"></script>
<script src="../js/search_index.js"></script>
<script src="../js/search.js"></script>
<script src="../js/searcher.js"></script>
<script src="../js/darkfish.js"></script>
<body id="top" role="document" class="module">
<nav role="navigation">
<div id="project-navigation">
<div id="home-section" role="region" title="Quick navigation" class="nav-section">
<h2>
<a href="../index.html" rel="home">Home</a>
</h2>
<div id="table-of-contents-navigation">
<a href="../table_of_contents.html#pages">Pages</a>
<a href="../table_of_contents.html#classes">Classes</a>
<a href="../table_of_contents.html#methods">Methods</a>
</div>
</div>
<div id="search-section" role="search" class="project-section initially-hidden">
<form action="#" method="get" accept-charset="utf-8">
<div id="search-field-wrapper">
<input id="search-field" role="combobox" aria-label="Search"
aria-autocomplete="list" aria-controls="search-results"
type="text" name="search" placeholder="Search" spellcheck="false"
title="Type to search, Up and Down to navigate, Enter to load">
</div>
<ul id="search-results" aria-label="Search Results"
aria-busy="false" aria-expanded="false"
aria-atomic="false" class="initially-hidden"></ul>
</form>
</div>
</div>
<div id="class-metadata">
</div>
</nav>
<main role="main" aria-labelledby="module-PG::Constants">
<h1 id="module-PG::Constants" class="module">
module PG::Constants
</h1>
<section class="description">
</section>
<section id="5Buntitled-5D" class="documentation-section">
<section class="constants-list">
<header>
<h3>Constants</h3>
</header>
<dl>
<dt id="CONNECTION_AUTH_OK">CONNECTION_AUTH_OK
<dd><p>Received authentication; waiting for backend start-up to finish.</p>
<dt id="CONNECTION_AWAITING_RESPONSE">CONNECTION_AWAITING_RESPONSE
<dd><p>Waiting for a response from the server.</p>
<dt id="CONNECTION_BAD">CONNECTION_BAD
<dd><p><a href="Connection.html">Connection</a> failed</p>
<dt id="CONNECTION_MADE">CONNECTION_MADE
<dd><p><a href="Connection.html">Connection</a> OK; waiting to send.</p>
<dt id="CONNECTION_NEEDED">CONNECTION_NEEDED
<dd><p>connect() needed.</p>
<dt id="CONNECTION_OK">CONNECTION_OK
<dd><p><a href="Connection.html">Connection</a> succeeded</p>
<dt id="CONNECTION_SETENV">CONNECTION_SETENV
<dd><p>Negotiating environment-driven parameter settings.</p>
<dt id="CONNECTION_SSL_STARTUP">CONNECTION_SSL_STARTUP
<dd><p>Negotiating SSL encryption.</p>
<dt id="CONNECTION_STARTED">CONNECTION_STARTED
<dd><p>Waiting for connection to be made.</p>
<dt id="INVALID_OID">INVALID_OID
<dd><p>Invalid OID constant</p>
<dt id="INV_READ">INV_READ
<dd><p>Flag for lo_creat, lo_open – open for reading</p>
<dt id="INV_WRITE">INV_WRITE
<dd><p>Flag for lo_creat, lo_open – open for writing</p>
<dt id="InvalidOid">InvalidOid
<dd>
<dt id="PGRES_BAD_RESPONSE">PGRES_BAD_RESPONSE
<dd><p>The server’s response was not understood.</p>
<dt id="PGRES_COMMAND_OK">PGRES_COMMAND_OK
<dd><p>Successful completion of a command returning no data.</p>
<dt id="PGRES_COPY_BOTH">PGRES_COPY_BOTH
<dd>
<dt id="PGRES_COPY_IN">PGRES_COPY_IN
<dd><p>Copy In (to server) data transfer started.</p>
<dt id="PGRES_COPY_OUT">PGRES_COPY_OUT
<dd><p>Copy Out (from server) data transfer started.</p>
<dt id="PGRES_EMPTY_QUERY">PGRES_EMPTY_QUERY
<dd><p>The string sent to the server was empty.</p>
<dt id="PGRES_FATAL_ERROR">PGRES_FATAL_ERROR
<dd><p>A fatal error occurred.</p>
<dt id="PGRES_NONFATAL_ERROR">PGRES_NONFATAL_ERROR
<dd><p>A nonfatal error (a notice or warning) occurred.</p>
<dt id="PGRES_POLLING_FAILED">PGRES_POLLING_FAILED
<dd><p>Async connection failed or was reset</p>
<dt id="PGRES_POLLING_OK">PGRES_POLLING_OK
<dd><p>Async connection succeeded</p>
<dt id="PGRES_POLLING_READING">PGRES_POLLING_READING
<dd><p>Async connection is waiting to read</p>
<dt id="PGRES_POLLING_WRITING">PGRES_POLLING_WRITING
<dd><p>Async connection is waiting to write</p>
<dt id="PGRES_SINGLE_TUPLE">PGRES_SINGLE_TUPLE
<dd>
<dt id="PGRES_TUPLES_OK">PGRES_TUPLES_OK
<dd><pre>Successful completion of a command returning data</pre>
<p>(such as a SELECT or SHOW).</p>
<dt id="PG_DIAG_COLUMN_NAME">PG_DIAG_COLUMN_NAME
<dd><p>If the error was associated with a specific table column, the name of the
column. (When this field is present, the schema and table name fields
identify the table.)</p>
<dt id="PG_DIAG_CONSTRAINT_NAME">PG_DIAG_CONSTRAINT_NAME
<dd><p>If the error was associated with a specific constraint, the name of the
constraint. The table or domain that the constraint belongs to is reported
using the fields listed above. (For this purpose, indexes are treated as
constraints, even if they weren't created with constraint syntax.)</p>
<dt id="PG_DIAG_CONTEXT">PG_DIAG_CONTEXT
<dd><p>An indication of the context in which the error occurred. Presently this
includes a call stack traceback of active procedural language functions and
internally-generated queries. The trace is one entry per line, most recent
rst.</p>
<dt id="PG_DIAG_DATATYPE_NAME">PG_DIAG_DATATYPE_NAME
<dd><p>If the error was associated with a specific datatype, the name of the
datatype. (When this field is present, the schema name field provides the
name of the datatype's schema.)</p>
<dt id="PG_DIAG_INTERNAL_POSITION">PG_DIAG_INTERNAL_POSITION
<dd><p>This is dened the same as the <a
href="Constants.html#PG_DIAG_STATEMENT_POSITION">PG_DIAG_STATEMENT_POSITION</a>
eld, but it is used when the cursor position refers to an internally
generated command rather than the one submitted by the client. The <a
href="Constants.html#PG_DIAG_INTERNAL_QUERY">PG_DIAG_INTERNAL_QUERY</a> eld
will always appear when this eld appears.</p>
<dt id="PG_DIAG_INTERNAL_QUERY">PG_DIAG_INTERNAL_QUERY
<dd><p>The text of a failed internally-generated command. This could be, for
example, a SQL query issued by a PL/pgSQL function.</p>
<dt id="PG_DIAG_MESSAGE_DETAIL">PG_DIAG_MESSAGE_DETAIL
<dd><p>an optional secondary error message carrying more detail about the problem.
Might run to multiple lines.</p>
<dt id="PG_DIAG_MESSAGE_HINT">PG_DIAG_MESSAGE_HINT
<dd><p>an optional suggestion what to do about the problem. This is intended to
differ from detail in that it offers advice (potentially inappropriate)
rather than hard facts. Might run to multiple lines.</p>
<dt id="PG_DIAG_MESSAGE_PRIMARY">PG_DIAG_MESSAGE_PRIMARY
<dd><p>The primary human-readable error message (typically one line). Always
present.</p>
<dt id="PG_DIAG_SCHEMA_NAME">PG_DIAG_SCHEMA_NAME
<dd><p>If the error was associated with a specific database object, the name of
the schema containing that object, if any.</p>
<dt id="PG_DIAG_SEVERITY">PG_DIAG_SEVERITY
<dd><p>The severity; the field contents are ERROR, FATAL, or PANIC (in an error
message), or WARNING, NOTICE, DEBUG, INFO, or LOG (in a notice message), or
a localized translation of one of these. Always present.</p>
<dt id="PG_DIAG_SOURCE_FILE">PG_DIAG_SOURCE_FILE
<dd><p>The le name of the source-code location where the error was reported.</p>
<dt id="PG_DIAG_SOURCE_FUNCTION">PG_DIAG_SOURCE_FUNCTION
<dd><p>The name of the source-code function reporting the error.</p>
<dt id="PG_DIAG_SOURCE_LINE">PG_DIAG_SOURCE_LINE
<dd><p>The line number of the source-code location where the error was reported.</p>
<dt id="PG_DIAG_SQLSTATE">PG_DIAG_SQLSTATE
<dd><p>The SQLSTATE code for the error. The SQLSTATE code identies the type of
error that has occurred; it can be used by front-end applications to
perform specic operations (such as er- ror handling) in response to a
particular database error. For a list of the possible SQLSTATE codes, see
Appendix A. This eld is not localizable, and is always present.</p>
<dt id="PG_DIAG_STATEMENT_POSITION">PG_DIAG_STATEMENT_POSITION
<dd><p>A string containing a decimal integer indicating an error cursor position
as an index into the original statement string. The rst character has index
1, and positions are measured in characters not bytes.</p>
<dt id="PG_DIAG_TABLE_NAME">PG_DIAG_TABLE_NAME
<dd><pre>If the error was associated with a</pre>
<p>specific table, the name of the table. (When this field is present, the
schema name</p>
<pre>field provides the name of the table's schema.)</pre>
<dt id="PQERRORS_DEFAULT">PQERRORS_DEFAULT
<dd><p>Default error verbosity level (#set_error_verbosity)</p>
<dt id="PQERRORS_TERSE">PQERRORS_TERSE
<dd><p>Terse error verbosity level (#set_error_verbosity)</p>
<dt id="PQERRORS_VERBOSE">PQERRORS_VERBOSE
<dd><p>Verbose error verbosity level (#set_error_verbosity)</p>
<dt id="PQPING_NO_ATTEMPT">PQPING_NO_ATTEMPT
<dd><p><a href="Connection.html">Connection</a> not attempted (bad params).</p>
<dt id="PQPING_NO_RESPONSE">PQPING_NO_RESPONSE
<dd><p>Could not establish connection.</p>
<dt id="PQPING_OK">PQPING_OK
<dd><p>Server is accepting connections.</p>
<dt id="PQPING_REJECT">PQPING_REJECT
<dd><p>Server is alive but rejecting connections.</p>
<dt id="PQTRANS_ACTIVE">PQTRANS_ACTIVE
<dd><p>Transaction is currently active; query has been sent to the server, but not
yet completed. (#transaction_status)</p>
<dt id="PQTRANS_IDLE">PQTRANS_IDLE
<dd><p>Transaction is currently idle (#transaction_status)</p>
<dt id="PQTRANS_INERROR">PQTRANS_INERROR
<dd><p>Transaction is currently idle, in a failed transaction block
(#transaction_status)</p>
<dt id="PQTRANS_INTRANS">PQTRANS_INTRANS
<dd><p>Transaction is currently idle, in a valid transaction block
(#transaction_status)</p>
<dt id="PQTRANS_UNKNOWN">PQTRANS_UNKNOWN
<dd><p>Transaction's connection is bad (#transaction_status)</p>
<dt id="SEEK_CUR">SEEK_CUR
<dd><p>Flag for lo_lseek – seek from current position</p>
<dt id="SEEK_END">SEEK_END
<dd><p>Flag for lo_lseek – seek from object end</p>
<dt id="SEEK_SET">SEEK_SET
<dd><p>Flag for lo_lseek – seek from object start</p>
</dl>
</section>
</section>
</main>
<footer id="validator-badges" role="contentinfo">
<p><a href="http://validator.w3.org/check/referer">Validate</a>
<p>Generated by <a href="http://rdoc.rubyforge.org">RDoc</a> 4.1.0.
<p>Based on <a href="http://deveiate.org/projects/Darkfish-Rdoc/">Darkfish</a> by <a href="http://deveiate.org">Michael Granger</a>.
</footer>
|