summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/oracle
Commit message (Collapse)AuthorAgeFilesLines
* - happy new yearMike Bayer2014-01-054-4/+4
|
* - Added ORA-02396 "maximum idle time" error code to list ofMike Bayer2013-12-031-1/+2
| | | | "is disconnect" codes with cx_oracle. [ticket:2864]
* Merge pull request #46 from vrajmohan/mastermike bayer2013-11-291-4/+4
|\ | | | | More fixes for cross references and reducing warnings (3rd wave)
| * Fix cross referencespr/46Vraj Mohan2013-11-171-4/+4
| |
* | - fix up rendering of "of"Mike Bayer2013-11-281-4/+4
| | | | | | | | | | | | - move out tests, dialect specific out of compiler, compiler tests use new API, legacy API tests in test_selecatble - add support for adaptation of ForUpdateArg, alias support in compilers
* | - work in progress, will squashMike Bayer2013-11-281-21/+10
| |
* | Merge branch 'for_update_of' of github.com:mlassnig/sqlalchemy into ↵Mike Bayer2013-11-281-2/+22
|\ \ | | | | | | | | | for_update_of
| * | added LockmodeArgspr/42Mario Lassnig2013-11-281-6/+16
| | |
| * | added ORM supportMario Lassnig2013-11-141-2/+12
| |/
* | - evaulate decimal_return_scale statelessly. Don't re-assign to ↵Mike Bayer2013-11-231-1/+1
| | | | | | | | | | | | self.decimal_return_scale so that __repr__() is maintained (for alembic tests)
* | - The precision used when coercing a returned floating point value toMike Bayer2013-11-221-4/+1
| | | | | | | | | | | | | | | | | | | | Python ``Decimal`` via string is now configurable. The flag ``decimal_return_scale`` is now supported by all :class:`.Numeric` and :class:`.Float` types, which will ensure this many digits are taken from the native floating point value when it is converted to string. If not present, the type will make use of the value of ``.scale``, if the type supports this setting and it is non-None. Otherwise the original default length of 10 is used. [ticket:2867]
* | Fixed bug where Oracle ``VARCHAR`` types given with no lengthMike Bayer2013-11-221-1/+3
|/ | | | | (e.g. for a ``CAST`` or similar) would incorrectly render ``None CHAR`` or similar. [ticket:2870]
* - Fixed bug where Oracle table reflection using synonyms would failMike Bayer2013-10-251-5/+7
| | | | | if the synonym and the table were in different remote schemas. Patch to fix courtesy Kyle Derr. [ticket:2853]
* add caveats regarding RETURNINGMike Bayer2013-09-022-3/+59
|
* - cx_oracle seems to have a bug here though it is hard to track downMike Bayer2013-08-272-2/+0
| | | | - cx_oracle dialect doesn't use normal col names, lets just not rely on that for now
* - A rework to the way that "quoted" identifiers are handled, in thatMike Bayer2013-08-271-1/+2
| | | | | | | | | | | | | | | | instead of relying upon various ``quote=True`` flags being passed around, these flags are converted into rich string objects with quoting information included at the point at which they are passed to common schema constructs like :class:`.Table`, :class:`.Column`, etc. This solves the issue of various methods that don't correctly honor the "quote" flag such as :meth:`.Engine.has_table` and related methods. The :class:`.quoted_name` object is a string subclass that can also be used explicitly if needed; the object will hold onto the quoting preferences passed and will also bypass the "name normalization" performed by dialects that standardize on uppercase symbols, such as Oracle, Firebird and DB2. The upshot is that the "uppercase" backends can now work with force-quoted names, such as lowercase-quoted names and new reserved words. [ticket:2812]
* - rework of correlation, continuing on #2668, #2746Mike Bayer2013-06-261-6/+2
| | | | | | | | | | | | | | | | | | | | | | | | - add support for correlations to propagate all the way in; because correlations require context now, need to make sure a select enclosure of any level takes effect any number of levels deep. - fix what we said correlate_except() was supposed to do when we first released #2668 - "the FROM clause is left intact if the correlated SELECT is not used in the context of an enclosing SELECT..." - it was not considering the "existing_froms" collection at all, and prohibited additional FROMs from being placed in an any() or has(). - add test for multilevel any() - lots of docs, including glossary entries as we really need to define "WHERE clause", "columns clause" etc. so that we can explain correlation better - based on the insight that a SELECT can correlate anything that ultimately came from an enclosing SELECT that links to this one via WHERE/columns/HAVING/ORDER BY, have the compiler keep track of the FROM lists that correspond in this way, link it to the asfrom flag, so that we send to _get_display_froms() the exact list of candidate FROMs to correlate. no longer need any asfrom logic in the Select() itself - preserve 0.8.1's behavior for correlation when no correlate options are given, not to mention 0.7 and prior's behavior of not propagating implicit correlation more than one level.. this is to reduce surprises/hard-to-debug situations when a user isn't trying to correlate anything.
* get nested joins to render on oracle 8Mike Bayer2013-06-081-3/+10
|
* - additional oracle fixes. cx_oracle under py3k is complaining about tuples ↵Mike Bayer2013-05-271-0/+5
| | | | | | | to executemany(), so just unconditionally turn this into a list - this one test segfaults only on py3k + cx_oracle
* - oracle py3k fixMike Bayer2013-05-271-1/+3
|
* a few more oracle fixesMike Bayer2013-05-261-11/+11
|
* cleanup for oracleMike Bayer2013-05-262-60/+57
|
* - the raw 2to3 runMike Bayer2013-04-273-65/+66
| | | | - went through examples/ and cleaned out excess list() calls
* oracle doesn't have TRUE/FALSE, put 1/0 here, see how that goesMike Bayer2013-04-261-0/+6
|
* - remove all compat items that are pre-2.5 (hooray)Mike Bayer2013-03-091-1/+1
| | | | | | - other cleanup - don't need compat.decimal, that approach never panned out. hopefully outside libs aren't pulling it in, they shouldn't be
* happy new year (see #2645)Diana Clarke2013-01-014-4/+4
|
* Fixed table reflection for Oracle when accessing a synonym that refersMike Bayer2012-12-091-58/+93
| | | | | | | | | | to a DBLINK remote database; while the syntax has been present in the Oracle dialect for some time, up until now it has never been tested. The syntax has been tested against a sample database linking to itself, however there's still some uncertainty as to what should be used for the "owner" when querying the remote database for table information. Currently, the value of "username" from user_db_links is used to match the "owner". [ticket:2619]
* The Oracle LONG type, while an unbounded text type, does not appearMike Bayer2012-12-061-0/+11
| | | | | | | to use the cx_Oracle.LOB type when result rows are returned, so the dialect has been repaired to exclude LONG from having cx_Oracle.LOB filtering applied. Also in 0.7.10. [ticket:2620]
* Repaired the usage of ``.prepare()`` in conjunction withMike Bayer2012-12-061-9/+50
| | | | | | | | | | | cx_Oracle so that a return value of ``False`` will result in no call to ``connection.commit()``, hence avoiding "no transaction" errors. Two-phase transactions have now been shown to work in a rudimental fashion with SQLAlchemy and cx_oracle, however are subject to caveats observed with the driver; check the documentation for details. Also in 0.7.10. [ticket:2611]
* kill me now, pep8 pass, so closeDiana Clarke2012-11-203-46/+55
|
* just a pep8 passDiana Clarke2012-11-202-22/+15
|
* juts a 'expected 2 blank lines' pep8 passDiana Clarke2012-11-193-1/+31
|
* Fixed bug in type_coerce() whereby typing informationMike Bayer2012-11-122-3/+3
| | | | | | | | could be lost if the statement were used as a subquery inside of another statement, as well as other similar situations. Among other things, would cause typing information to be lost when the Oracle/mssql dialects would apply limit/offset wrappings. [ticket:2603]
* - rework the sphinx customizations into distinct modulesMike Bayer2012-10-193-24/+20
| | | | | | | - build a new Sphinx extension that allows dialect info to be entered as directives which is then rendered consistently throughout all dialect/dbapi sections - break out the "empty_strings" requirement for oracle test
* - move out maxdbMike Bayer2012-10-181-3/+0
| | | | | | - begin consolidating docs for dialects to be more self contained - add a separate section for "external" dialects - not sure how we're going to go with this yet.
* - [bug] The CreateIndex construct in OracleMike Bayer2012-09-301-0/+4
| | | | | | | | will now schema-qualify the name of the index to be that of the parent table. Previously this name was omitted which apparently creates the index in the default schema, rather than that of the table.
* - [feature] The types of columns excluded from theMike Bayer2012-09-051-22/+41
| | | | | | | | setinputsizes() set can be customized by sending a list of string DBAPI type names to exclude. This list was previously fixed. The list also now defaults to STRING, UNICODE, removing CLOB, NCLOB from the list. [ticket:2469]
* - refine oracle returning some more to use purely positional approachMike Bayer2012-08-252-22/+22
|
* - more oracle tweaks for returning; the method here is still kind of brittle ↵Mike Bayer2012-08-251-5/+6
| | | | | | and might have issues with pks, multiple function calls
* a few oracle fixesMike Bayer2012-08-251-1/+2
|
* - [bug] Fixed cextension bug whereby theMike Bayer2012-08-221-3/+5
| | | | | | | | | | | | | | | | | | | "ambiguous column error" would fail to function properly if the given index were a Column object and not a string. Note there are still some column-targeting issues here which are fixed in 0.8. [ticket:2553] - find more cases where column targeting is being inaccurate, add more information to result_map to better differentiate "ambiguous" results from "present" or "not present". In particular, result_map is sensitive to dupes, even though no error is raised; the conflicting columns are added to the "obj" member of the tuple so that the two are both directly accessible in the result proxy - handwringing over the damn "name fallback" thing in results. can't really make it perfect yet - fix up oracle returning clause. not sure why its guarding against labels, remove that for now and see what the bot says.
* - update all the visit_mod() functions with new naming schemeMike Bayer2012-08-141-2/+3
| | | | | | - visit_mods all seemed to not propagate **kw down to process(). this is [ticket:2548] which may be backported to 0.7 pending a test case to illustrate wrong behavior.
* - fix concat() operator, testsMike Bayer2012-08-141-3/+4
| | | | | | | | - [feature] Custom unary operators can now be used by combining operators.custom_op() with UnaryExpression(). - clean up the operator dispatch system and make it more consistent. This does change the compiler contract for custom ops.
* - [bug] Fixed compiler bug whereby a givenMike Bayer2012-08-121-1/+1
| | | | | | select() would be modified if it had an "offset" attribute, causing the construct to not compile correctly a second time. [ticket:2545]
* - break out engine/base.py into base, interfaces, result, util.Mike Bayer2012-08-072-9/+9
| | | | - remove deprecated 0.7 engine methods
* -whitespace bonanza, contdMike Bayer2012-07-281-54/+54
|
* trailing whitespace bonanzaMike Bayer2012-07-281-48/+48
|
* - pass kw through hereMike Bayer2012-06-251-3/+3
|
* Add some `Sphinx` paragraph level versions informations markups,Mike Bayer2012-06-082-9/+15
| | | | such as ``.. versionadded::``, ``.. versionchanged::`` and ``.. deprecated::``.
* - [bug] Added ROWID to oracle.*, [ticket:2483]Mike Bayer2012-05-171-1/+1
| | | | Also in 0.7.8.