Movatterモバイル変換


[0]ホーム

URL:



Facebook
Postgres Pro
Facebook
Downloads
46.7. Database Access
Prev UpChapter 46. PL/Python — Python Procedural LanguageHome Next

46.7. Database Access

The PL/Python language module automatically imports a Python module calledplpy. The functions and constants in this module are available to you in the Python code asplpy.foo.

46.7.1. Database Access Functions

Theplpy module provides several functions to execute database commands:

plpy.execute(query [,limit])

Callingplpy.execute with a query string and an optional row limit argument causes that query to be run and the result to be returned in a result object.

Iflimit is specified and is greater than zero, thenplpy.execute retrieves at mostlimit rows, much as if the query included aLIMIT clause. Omittinglimit or specifying it as zero results in no row limit.

The result object emulates a list or dictionary object. The result object can be accessed by row number and column name. For example:

rv = plpy.execute("SELECT * FROM my_table", 5)

returns up to 5 rows frommy_table. Ifmy_table has a columnmy_column, it would be accessed as:

foo = rv[i]["my_column"]

The number of rows returned can be obtained using the built-inlen function.

The result object has these additional methods:

nrows()

Returns the number of rows processed by the command. Note that this is not necessarily the same as the number of rows returned. For example, anUPDATE command will set this value but won't return any rows (unlessRETURNING is used).

status()

TheSPI_execute() return value.

colnames()
coltypes()
coltypmods()

Return a list of column names, list of column type OIDs, and list of type-specific type modifiers for the columns, respectively.

These methods raise an exception when called on a result object from a command that did not produce a result set, e.g.,UPDATE withoutRETURNING, orDROP TABLE. But it is OK to use these methods on a result set containing zero rows.

__str__()

The standard__str__ method is defined so that it is possible for example to debug query execution results usingplpy.debug(rv).

The result object can be modified.

Note that callingplpy.execute will cause the entire result set to be read into memory. Only use that function when you are sure that the result set will be relatively small. If you don't want to risk excessive memory usage when fetching large results, useplpy.cursor rather thanplpy.execute.

plpy.prepare(query [,argtypes])
plpy.execute(plan [,arguments [,limit]])

plpy.prepare prepares the execution plan for a query. It is called with a query string and a list of parameter types, if you have parameter references in the query. For example:

plan = plpy.prepare("SELECT last_name FROM my_users WHERE first_name = $1", ["text"])

text is the type of the variable you will be passing for$1. The second argument is optional if you don't want to pass any parameters to the query.

After preparing a statement, you use a variant of the functionplpy.execute to run it:

rv = plpy.execute(plan, ["name"], 5)

Pass the plan as the first argument (instead of the query string), and a list of values to substitute into the query as the second argument. The second argument is optional if the query does not expect any parameters. The third argument is the optional row limit as before.

Alternatively, you can call theexecute method on the plan object:

rv = plan.execute(["name"], 5)

Query parameters and result row fields are converted between PostgreSQL and Python data types as described inSection 46.3.

When you prepare a plan using the PL/Python module it is automatically saved. Read the SPI documentation (Chapter 47) for a description of what this means. In order to make effective use of this across function calls one needs to use one of the persistent storage dictionariesSD orGD (seeSection 46.4). For example:

CREATE FUNCTION usesavedplan() RETURNS trigger AS $$    if "plan" in SD:        plan = SD["plan"]    else:        plan = plpy.prepare("SELECT 1")        SD["plan"] = plan    # rest of function$$ LANGUAGE plpythonu;

plpy.cursor(query)
plpy.cursor(plan [,arguments])

Theplpy.cursor function accepts the same arguments asplpy.execute (except for the row limit) and returns a cursor object, which allows you to process large result sets in smaller chunks. As withplpy.execute, either a query string or a plan object along with a list of arguments can be used, or thecursor function can be called as a method of the plan object.

The cursor object provides afetch method that accepts an integer parameter and returns a result object. Each time you callfetch, the returned object will contain the next batch of rows, never larger than the parameter value. Once all rows are exhausted,fetch starts returning an empty result object. Cursor objects also provide aniterator interface, yielding one row at a time until all rows are exhausted. Data fetched that way is not returned as result objects, but rather as dictionaries, each dictionary corresponding to a single result row.

An example of two ways of processing data from a large table is:

CREATE FUNCTION count_odd_iterator() RETURNS integer AS $$odd = 0for row in plpy.cursor("select num from largetable"):    if row['num'] % 2:         odd += 1return odd$$ LANGUAGE plpythonu;CREATE FUNCTION count_odd_fetch(batch_size integer) RETURNS integer AS $$odd = 0cursor = plpy.cursor("select num from largetable")while True:    rows = cursor.fetch(batch_size)    if not rows:        break    for row in rows:        if row['num'] % 2:            odd += 1return odd$$ LANGUAGE plpythonu;CREATE FUNCTION count_odd_prepared() RETURNS integer AS $$odd = 0plan = plpy.prepare("select num from largetable where num % $1 <> 0", ["integer"])rows = list(plpy.cursor(plan, [2]))  # or: = list(plan.cursor([2]))return len(rows)$$ LANGUAGE plpythonu;

Cursors are automatically disposed of. But if you want to explicitly release all resources held by a cursor, use theclose method. Once closed, a cursor cannot be fetched from anymore.

Tip

Do not confuse objects created byplpy.cursor with DB-API cursors as defined by thePython Database API specification. They don't have anything in common except for the name.

46.7.2. Trapping Errors

Functions accessing the database might encounter errors, which will cause them to abort and raise an exception. Bothplpy.execute andplpy.prepare can raise an instance of a subclass ofplpy.SPIError, which by default will terminate the function. This error can be handled just like any other Python exception, by using thetry/except construct. For example:

CREATE FUNCTION try_adding_joe() RETURNS text AS $$    try:        plpy.execute("INSERT INTO users(username) VALUES ('joe')")    except plpy.SPIError:        return "something went wrong"    else:        return "Joe added"$$ LANGUAGE plpythonu;

The actual class of the exception being raised corresponds to the specific condition that caused the error. Refer toTable A.1 for a list of possible conditions. The moduleplpy.spiexceptions defines an exception class for eachPostgreSQL condition, deriving their names from the condition name. For instance,division_by_zero becomesDivisionByZero,unique_violation becomesUniqueViolation,fdw_error becomesFdwError, and so on. Each of these exception classes inherits fromSPIError. This separation makes it easier to handle specific errors, for instance:

CREATE FUNCTION insert_fraction(numerator int, denominator int) RETURNS text AS $$from plpy import spiexceptionstry:    plan = plpy.prepare("INSERT INTO fractions (frac) VALUES ($1 / $2)", ["int", "int"])    plpy.execute(plan, [numerator, denominator])except spiexceptions.DivisionByZero:    return "denominator cannot equal zero"except spiexceptions.UniqueViolation:    return "already have that fraction"except plpy.SPIError as e:    return "other error, SQLSTATE %s" % e.sqlstateelse:    return "fraction inserted"$$ LANGUAGE plpythonu;

Note that because all exceptions from theplpy.spiexceptions module inherit fromSPIError, anexcept clause handling it will catch any database access error.

As an alternative way of handling different error conditions, you can catch theSPIError exception and determine the specific error condition inside theexcept block by looking at thesqlstate attribute of the exception object. This attribute is a string value containing theSQLSTATE error code. This approach provides approximately the same functionality


Prev Up Next
46.6. Trigger Functions Home 46.8. Explicit Subtransactions
pdfepub
Go to PostgreSQL 14
By continuing to browse this website, you agree to the use of cookies. Go toPrivacy Policy.

[8]ページ先頭

©2009-2025 Movatter.jp