/usr/include/pqxx/transaction_base.hxx is in libpqxx-dev 4.0.1+dfsg3-8.
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 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 | /*-------------------------------------------------------------------------
*
* FILE
* pqxx/transaction_base.hxx
*
* DESCRIPTION
* common code and definitions for the transaction classes.
* pqxx::transaction_base defines the interface for any abstract class that
* represents a database transaction
* DO NOT INCLUDE THIS FILE DIRECTLY; include pqxx/transaction_base instead.
*
* Copyright (c) 2001-2011, Jeroen T. Vermeulen <jtv@xs4all.nl>
*
* See COPYING for copyright license. If you did not receive a file called
* COPYING with this source code, please notify the distributor of this mistake,
* or contact the author.
*
*-------------------------------------------------------------------------
*/
#ifndef PQXX_H_TRANSACTION_BASE
#define PQXX_H_TRANSACTION_BASE
#include "pqxx/compiler-public.hxx"
#include "pqxx/compiler-internal-pre.hxx"
/* End-user programs need not include this file, unless they define their own
* transaction classes. This is not something the typical program should want
* to do.
*
* However, reading this file is worthwhile because it defines the public
* interface for the available transaction classes such as transaction and
* nontransaction.
*/
#include "pqxx/connection_base"
#include "pqxx/isolation"
#include "pqxx/result"
/* Methods tested in eg. self-test program test001 are marked with "//[t1]"
*/
namespace pqxx
{
class connection_base;
class transaction_base;
namespace internal
{
class sql_cursor;
class PQXX_LIBEXPORT transactionfocus : public virtual namedclass
{
public:
explicit transactionfocus(transaction_base &t) :
namedclass("transactionfocus"),
m_Trans(t),
m_registered(false)
{
}
protected:
void register_me();
void unregister_me() throw ();
void reg_pending_error(const PGSTD::string &) throw ();
bool registered() const throw () { return m_registered; }
transaction_base &m_Trans;
private:
bool m_registered;
/// Not allowed
transactionfocus();
/// Not allowed
transactionfocus(const transactionfocus &);
/// Not allowed
transactionfocus &operator=(const transactionfocus &);
};
class PQXX_LIBEXPORT parameterized_invocation : statement_parameters
{
public:
parameterized_invocation(connection_base &, const PGSTD::string &query);
parameterized_invocation &operator()() { add_param(); return *this; }
parameterized_invocation &operator()(const binarystring &v)
{ add_binary_param(v, true); return *this; }
template<typename T> parameterized_invocation &operator()(const T &v)
{ add_param(v, true); return *this; }
parameterized_invocation &operator()(const binarystring &v, bool nonnull)
{ add_binary_param(v, nonnull); return *this; }
template<typename T>
parameterized_invocation &operator()(const T &v, bool nonnull)
{ add_param(v, nonnull); return *this; }
result exec();
private:
/// Not allowed
parameterized_invocation &operator=(const parameterized_invocation &);
connection_base &m_home;
const PGSTD::string m_query;
};
} // namespace internal
namespace internal
{
namespace gate
{
class transaction_subtransaction;
class transaction_tablereader;
class transaction_tablewriter;
class transaction_transactionfocus;
} // namespace internal::gate
} // namespace internal
/// Interface definition (and common code) for "transaction" classes.
/**
* @addtogroup transaction Transaction classes
* All database access must be channeled through one of these classes for
* safety, although not all implementations of this interface need to provide
* full transactional integrity.
*
* Several implementations of this interface are shipped with libpqxx, including
* the plain transaction class, the entirely unprotected nontransaction, and the
* more cautions robusttransaction.
*/
class PQXX_LIBEXPORT PQXX_NOVTABLE transaction_base :
public virtual internal::namedclass
{
public:
/// If nothing else is known, our isolation level is at least read_committed
typedef isolation_traits<read_committed> isolation_tag;
virtual ~transaction_base() =0; //[t1]
/// Commit the transaction
/** Unless this function is called explicitly, the transaction will not be
* committed (actually the nontransaction implementation breaks this rule,
* hence the name).
*
* Once this function returns, the whole transaction will typically be
* irrevocably completed in the database. There is also, however, a minute
* risk that the connection to the database may be lost at just the wrong
* moment. In that case, libpqxx may be unable to determine whether the
* transaction was completed or aborted and an in_doubt_error will be thrown
* to make this fact known to the caller. The robusttransaction
* implementation takes some special precautions to reduce this risk.
*/
void commit(); //[t1]
/// Abort the transaction
/** No special effort is required to call this function; it will be called
* implicitly when the transaction is destructed.
*/
void abort(); //[t10]
/**
* @addtogroup escaping String escaping
*/
//@{
/// Escape string for use as SQL string literal in this transaction
PGSTD::string esc(const char str[]) const { return conn().esc(str); }
/// Escape string for use as SQL string literal in this transaction
PGSTD::string esc(const char str[], size_t maxlen) const
{ return conn().esc(str, maxlen); }
/// Escape string for use as SQL string literal in this transaction
PGSTD::string esc(const PGSTD::string &str) const { return conn().esc(str); }
/// Escape binary data for use as SQL string literal in this transaction
/** Raw, binary data is treated differently from regular strings. Binary
* strings are never interpreted as text, so they may safely include byte
* values or byte sequences that don't happen to represent valid characters in
* the character encoding being used.
*
* The binary string does not stop at the first zero byte, as is the case with
* textual strings. Instead, they may contain zero bytes anywhere. If it
* happens to contain bytes that look like quote characters, or other things
* that can disrupt their use in SQL queries, they will be replaced with
* special escape sequences.
*/
PGSTD::string esc_raw(const unsigned char str[], size_t len) const //[t62]
{ return conn().esc_raw(str, len); }
/// Escape binary data for use as SQL string literal in this transaction
PGSTD::string esc_raw(const PGSTD::string &) const; //[t62]
/// Represent object as SQL string, including quoting & escaping.
/** Nulls are recognized and represented as SQL nulls. */
template<typename T> PGSTD::string quote(const T &t) const
{ return conn().quote(t); }
/// Binary-escape and quote a binarystring for use as an SQL constant.
PGSTD::string quote_raw(const unsigned char str[], size_t len) const
{ return conn().quote_raw(str, len); }
PGSTD::string quote_raw(const PGSTD::string &str) const;
/// Escape an SQL identifier for use in a query.
PGSTD::string quote_name(const PGSTD::string &identifier) const
{ return conn().quote_name(identifier); }
//@}
/// Execute query
/** Perform a query in this transaction.
*
* This is one of the most important functions in libpqxx.
*
* Most libpqxx exceptions can be thrown from here, including sql_error,
* broken_connection, and many sql_error subtypes such as
* feature_not_supported or insufficient_privilege. But any exception thrown
* by the C++ standard library may also occur here. All exceptions will be
* derived from std::exception, however, and all libpqxx-specific exception
* types are derived from pqxx::pqxx_exception.
*
* @param Query Query or command to execute
* @param Desc Optional identifier for query, to help pinpoint SQL errors
* @return A result set describing the query's or command's result
*/
result exec(const PGSTD::string &Query,
const PGSTD::string &Desc=PGSTD::string()); //[t1]
result exec(const PGSTD::stringstream &Query,
const PGSTD::string &Desc=PGSTD::string())
{ return exec(Query.str(), Desc); }
/// Parameterize a statement.
/* Use this to build up a parameterized statement invocation, then invoke it
* using @c exec()
*
* Example: @c trans.parameterized("SELECT $1 + 1")(1).exec();
*/
internal::parameterized_invocation parameterized(const PGSTD::string &query);
/**
* @name Prepared statements
*/
//@{
/// Execute prepared statement.
/** Prepared statements are defined using the connection classes' prepare()
* function, and continue to live on in the ongoing session regardless of
* the context they were defined in (unless explicitly dropped using the
* connection's unprepare() function). Their execution however, like other
* forms of query execution, requires a transaction object.
*
* Just like param_declaration is a helper class that lets you tag parameter
* declarations onto the statement declaration, the invocation class returned
* here lets you tag parameter values onto the call:
*
* @code
* result run_mystatement(transaction_base &T)
* {
* return T.prepared("mystatement")("param1")(2)()(4).exec();
* }
* @endcode
*
* Here, parameter 1 (written as "<tt>$1</tt>" in the statement's body) is a
* string that receives the value "param1"; the second parameter is an integer
* with the value 2; the third receives a null, making its type irrelevant;
* and number 4 again is an integer. The ultimate invocation of exec() is
* essential; if you forget this, nothing happens.
*
* To see whether any prepared statement has been defined under a given name,
* use:
*
* @code
* T.prepared("mystatement").exists()
* @endcode
*
* @warning Do not try to execute a prepared statement manually through direct
* SQL statements. This is likely not to work, and even if it does, is likely
* to be slower than using the proper libpqxx functions. Also, libpqxx knows
* how to emulate prepared statements if some part of the infrastructure does
* not support them.
*
* @warning Actual definition of the prepared statement on the backend may be
* deferred until its first use, which means that any errors in the prepared
* statement may not show up until it is executed--and perhaps abort the
* ongoing transaction in the process.
*
* If you leave out the statement name, the call refers to the nameless
* statement instead.
*/
prepare::invocation prepared(const PGSTD::string &statement=PGSTD::string());
//@}
/**
* @name Error/warning output
*/
//@{
/// Have connection process warning message
void process_notice(const char Msg[]) const //[t14]
{ m_Conn.process_notice(Msg); }
/// Have connection process warning message
void process_notice(const PGSTD::string &Msg) const //[t14]
{ m_Conn.process_notice(Msg); }
//@}
/// Connection this transaction is running in
connection_base &conn() const { return m_Conn; } //[t4]
/// Set session variable in this connection
/** The new value is typically forgotten if the transaction aborts.
* Known exceptions to this rule are nontransaction, and PostgreSQL versions
* prior to 7.3. In the case of nontransaction, the set value will be kept
* regardless; but in that case, if the connection ever needs to be recovered,
* the set value will not be restored.
* @param Var The variable to set
* @param Val The new value to store in the variable
*/
void set_variable(const PGSTD::string &Var, const PGSTD::string &Val);//[t61]
/// Get currently applicable value of variable
/** First consults an internal cache of variables that have been set (whether
* in the ongoing transaction or in the connection) using the set_variable
* functions. If it is not found there, the database is queried.
*
* @warning Do not mix the set_variable with raw "SET" queries, and do not
* try to set or get variables while a pipeline or table stream is active.
*
* @warning This function used to be declared as @c const but isn't anymore.
*/
PGSTD::string get_variable(const PGSTD::string &); //[t61]
protected:
/// Create a transaction (to be called by implementation classes only)
/** The optional name, if nonempty, must begin with a letter and may contain
* letters and digits only.
*
* @param c The connection that this transaction is to act on.
* @param direct Running directly in connection context (i.e. not nested)?
*/
explicit transaction_base(connection_base &c, bool direct=true);
/// Begin transaction (to be called by implementing class)
/** Will typically be called from implementing class' constructor.
*/
void Begin();
/// End transaction. To be called by implementing class' destructor
void End() throw ();
/// To be implemented by derived implementation class: start transaction
virtual void do_begin() =0;
/// To be implemented by derived implementation class: perform query
virtual result do_exec(const char Query[]) =0;
/// To be implemented by derived implementation class: commit transaction
virtual void do_commit() =0;
/// To be implemented by derived implementation class: abort transaction
virtual void do_abort() =0;
// For use by implementing class:
/// Execute query on connection directly
/**
* @param C Query or command to execute
* @param Retries Number of times to retry the query if it fails. Be
* extremely careful with this option; if you retry in the middle of a
* transaction, you may be setting up a new connection transparently and
* executing the latter part of the transaction without a backend transaction
* being active (and with the former part aborted).
*/
result DirectExec(const char C[], int Retries=0);
/// Forget about any reactivation-blocking resources we tried to allocate
void reactivation_avoidance_clear() throw ()
{m_reactivation_avoidance.clear();}
protected:
/// Resources allocated in this transaction that make reactivation impossible
/** This number may be negative!
*/
internal::reactivation_avoidance_counter m_reactivation_avoidance;
private:
/* A transaction goes through the following stages in its lifecycle:
* <ul>
* <li> nascent: the transaction hasn't actually begun yet. If our connection
* fails at this stage, it may recover and the transaction can attempt to
* establish itself again.
* <li> active: the transaction has begun. Since no commit command has been
* issued, abortion is implicit if the connection fails now.
* <li> aborted: an abort has been issued; the transaction is terminated and
* its changes to the database rolled back. It will accept no further
* commands.
* <li> committed: the transaction has completed successfully, meaning that a
* commit has been issued. No further commands are accepted.
* <li> in_doubt: the connection was lost at the exact wrong time, and there
* is no way of telling whether the transaction was committed or aborted.
* </ul>
*
* Checking and maintaining state machine logic is the responsibility of the
* base class (ie., this one).
*/
enum Status
{
st_nascent,
st_active,
st_aborted,
st_committed,
st_in_doubt
};
/// Make sure transaction is opened on backend, if appropriate
void PQXX_PRIVATE activate();
void PQXX_PRIVATE CheckPendingError();
template<typename T> bool parm_is_null(T *p) const throw () { return !p; }
template<typename T> bool parm_is_null(T) const throw () { return false; }
friend class pqxx::internal::gate::transaction_transactionfocus;
void PQXX_PRIVATE RegisterFocus(internal::transactionfocus *);
void PQXX_PRIVATE UnregisterFocus(internal::transactionfocus *) throw ();
void PQXX_PRIVATE RegisterPendingError(const PGSTD::string &) throw ();
friend class pqxx::internal::gate::transaction_tablereader;
void PQXX_PRIVATE BeginCopyRead(const PGSTD::string &, const PGSTD::string &);
bool ReadCopyLine(PGSTD::string &);
friend class pqxx::internal::gate::transaction_tablewriter;
void PQXX_PRIVATE BeginCopyWrite(
const PGSTD::string &Table,
const PGSTD::string &Columns);
void WriteCopyLine(const PGSTD::string &);
void EndCopyWrite();
friend class pqxx::internal::gate::transaction_subtransaction;
connection_base &m_Conn;
internal::unique<internal::transactionfocus> m_Focus;
Status m_Status;
bool m_Registered;
PGSTD::map<PGSTD::string, PGSTD::string> m_Vars;
PGSTD::string m_PendingError;
/// Not allowed
transaction_base();
/// Not allowed
transaction_base(const transaction_base &);
/// Not allowed
transaction_base &operator=(const transaction_base &);
};
} // namespace pqxx
#include "pqxx/compiler-internal-post.hxx"
#endif
|