Asterisk - The Open Source Telephony Project GIT-master-f36a736
res_odbc_transaction.h
Go to the documentation of this file.
1/*
2 * Asterisk -- An open source telephony toolkit.
3 *
4 * Copyright (C) 2016, Digium, Inc.
5 *
6 * Mark Michelson <mmichelson@digium.com>
7 *
8 * See http://www.asterisk.org for more information about
9 * the Asterisk project. Please do not directly contact
10 * any of the maintainers of this project for assistance;
11 * the project provides a web site, mailing lists and IRC
12 * channels for your use.
13 *
14 * This program is free software, distributed under the terms of
15 * the GNU General Public License Version 2. See the LICENSE file
16 * at the top of the source tree.
17 */
18
19#ifndef RES_ODBC_TRANSACTION_H
20#define RES_ODBC_TRANSACTION_H
21
22/*!
23 * \brief
24 *
25 * Retrieve an ODBC transaction connection with the given ODBC class name.
26 *
27 * \note The name passed here is *not* the name of the transaction but the name of the
28 * ODBC class defined in res_odbc.conf.
29 *
30 * \note Do not call ast_odbc_release_obj() on the retrieved connection. Calling this function
31 * does not make you the owner of the connection.
32 *
33 * XXX This function is majorly flawed because it ignores properties of transactions and simply
34 * finds one that corresponds to the given DSN. The problem here is that transactions have names
35 * and they maintain which transaction is "active" for operations like transaction creation,
36 * commit, and rollback. However, when it comes to intermediary operations to be made on the
37 * transactions, all that is ignored. It means that if a channel has created multiple transactions
38 * for the same DSN, it's a crapshoot which of those transactions the operation will be performed
39 * on. This can potentially lead to baffling errors under the right circumstances.
40 *
41 * XXX The semantics of this function make for writing some awkward code. If you use func_odbc as
42 * an example, it has to first try to retrieve a transactional connection, then failing that, create
43 * a non-transactional connection. The result is that it has to remember which type of connection it's
44 * using and know whether to release the connection when completed or not. It would be much better
45 * if callers did not have to jump through such hoops.
46 *
47 * \param chan Channel on which the ODBC transaction was created
48 * \param objname The name of the ODBC class configured in res_odbc.conf
49 * \retval NULL Transaction connection could not be found.
50 * \retval non-NULL A transactional connection
51 */
52struct odbc_obj *ast_odbc_retrieve_transaction_obj(struct ast_channel *chan, const char *objname);
53
54#endif /* RES_ODBC_TRANSACTION_H */
struct odbc_obj * ast_odbc_retrieve_transaction_obj(struct ast_channel *chan, const char *objname)
Retrieve an ODBC transaction connection with the given ODBC class name.
Main Channel structure associated with a channel.
ODBC container.
Definition: res_odbc.h:46