summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
* add sap sqlanywhereMike Bayer2013-11-121-0/+1
|
* move the css to the base so that the site can overrideMike Bayer2013-11-112-9/+9
|
* use an explcit css blockMike Bayer2013-11-112-3/+14
|
* attempt to use the css_files list so that we can integrate cssMike Bayer2013-11-111-2/+6
| | | | better with rtd
* 0.3.2 pleaseMike Bayer2013-11-101-1/+1
|
* - tutorial updatesMike Bayer2013-11-104-193/+230
| | | | | | - emphasis on not using a custom contructor by default, making sure it's clear that you *can* use one - other separation of narrative from special notes using sidebars
* - some py3k compatibilityMike Bayer2013-11-101-1/+9
|
* - use a dictionary hereMike Bayer2013-11-101-8/+5
|
* - add a new sphinx extension "viewsource". takes advantage of part of the ↵Mike Bayer2013-11-093-51/+219
| | | | | | | | | viewcode extension to allow ad-hoc display of the source of any file, as well as a "directory listing" structure. - reorganize examples/ to take advantage of new extension. in particular, keep moving all the descriptive text for files etc. into module docstrings, taking more advantage of self-documentation.
* include the start-line directive here so that we dont get warningsMike Bayer2013-11-092-0/+3
| | | | for the headers in the included files
* also update requirements file...Mike Bayer2013-11-091-0/+1
|
* - use pypi changelog pluginMike Bayer2013-11-093-369/+13
| | | | | - remove outdated pullreq links - support pullreq links for bitbucket or github and add a few
* - Fixed bug which prevented history_meta recipe from working withMike Bayer2013-11-071-0/+6
| | | | | | joined inheritance schemes more than one level deep. - don't need to use _lib.py here anymore now that these features are in sqlalchemy.testing
* - Fixed a regression introduced by the join rewriting feature ofMike Bayer2013-11-011-0/+10
| | | | | | | :ticket:`2369` and :ticket:`2587` where a nested join with one side already an aliased select would fail to translate the ON clause on the outside correctly; in the ORM this could be seen when using a SELECT statement as a "secondary" table. [ticket:2858]
* - add a section re: using column_reflect for mapping, link to it from the ↵Mike Bayer2013-10-312-10/+51
| | | | "naming columns distinctly" and "column_prefix" sections since this is often what ppl are looking for. [ticket:2856] is related.
* - Fixed a regression introduced by :ticket:`2818` where the EXISTSMike Bayer2013-10-301-0/+10
| | | | | | query being generated would produce a "columns being replaced" warning for a statement with two same-named columns, as the internal SELECT wouldn't have use_labels set.
* no such thing as default_strategy()...Mike Bayer2013-10-281-2/+3
|
* - whitespace below ..version, sighMike Bayer2013-10-281-1/+0
|
* fix to the changelog system for when there's no change recs in the bodyMike Bayer2013-10-271-1/+5
|
* - Fixed bug where index reflection would mis-interpret indkey valuesMike Bayer2013-10-272-0/+15
| | | | | | when using the pypostgresql adapter, which returns these values as lists vs. psycopg2's return type of string. [ticket:2855]
* - farm out everthing to do with rtd out to the sqlalchemy.org siteMike Bayer2013-10-276-206/+33
|
* - more updates to compatability, C extensions, building, etc.rel_0_9_0b1Mike Bayer2013-10-261-13/+19
|
* - ensure 0.9 in various documentation spacesMike Bayer2013-10-263-13/+12
| | | | - supporting py 2.6, update pypy version, jython not working these days
* - release 0.9.0b1Mike Bayer2013-10-263-2/+4
|
* will call this 0.9.0b1Mike Bayer2013-10-264-66/+66
|
* - Fixed bug where Oracle table reflection using synonyms would failMike Bayer2013-10-251-0/+9
| | | | | if the synonym and the table were in different remote schemas. Patch to fix courtesy Kyle Derr. [ticket:2853]
* - catch the metadata on ScalarTest.test_scalar_proxy, this has been leaving ↵Mike Bayer2013-10-253-0/+56
| | | | | | | | itself around for a long time - association proxy now returns None for proxied scalar that is also None, rather than raising AttributeError. [ticket:2810]
* - changelog for [ticket:2183]Mike Bayer2013-10-251-0/+8
|
* - Fix and test parsing of MySQL foreign key options within reflection;Mike Bayer2013-10-251-0/+9
| | | | | | this complements the work in :ticket:`2183` where we begin to support reflection of foreign key options such as ON UPDATE/ON DELETE cascade. [ticket:2839]
* - :func:`.attributes.get_history()` when used with a scalar column-mappedMike Bayer2013-10-252-0/+73
| | | | | | | | | attribute will now honor the "passive" flag passed to it; as this defaults to ``PASSIVE_OFF``, the function will by default query the database if the value is not present. This is a behavioral change vs. 0.8. [ticket:2787] - Added new method :meth:`.AttributeState.load_history`, works like :attr:`.AttributeState.history` but also fires loader callables.
* - add migration notes for [ticket:2838]Mike Bayer2013-10-242-0/+30
| | | | | - have TypeDecorator use process_bind_param for literal values if no process_literal_param is set
* clarificationsMike Bayer2013-10-231-10/+10
|
* updatedMike Bayer2013-10-231-1/+1
|
* An overhaul of expression handling for special symbols particularlyMike Bayer2013-10-233-4/+85
| | | | | | | | | | with conjunctions, e.g. ``None`` :func:`.expression.null` :func:`.expression.true` :func:`.expression.false`, including consistency in rendering NULL in conjunctions, "short-circuiting" of :func:`.and_` and :func:`.or_` expressions which contain boolean constants, and rendering of boolean constants and expressions as compared to "1" or "0" for backends that don't feature ``true``/``false`` constants. [ticket:2804]
* - The regexp used by the :func:`.url.make_url` function now parsesMike Bayer2013-10-231-0/+8
| | | | ipv6 addresses, e.g. surrounded by brackets. [ticket:2851]
* typosMike Bayer2013-10-212-4/+6
|
* - A :func:`.bindparam` construct with a "null" type (e.g. no typeMike Bayer2013-10-212-0/+69
| | | | | | | | | specified) is now copied when used in a typed expression, and the new copy is assigned the actual type of the compared column. Previously, this logic would occur on the given :func:`.bindparam` in place. Additionally, a similar process now occurs for :func:`.bindparam` constructs passed to :meth:`.ValuesBase.values` for a :class:`.Insert` or :class:`.Update` construct. [ticket:2850]
* - Fixed bug where :func:`.type_coerce` would not interpret ORMMike Bayer2013-10-211-0/+8
| | | | | elements with a ``__clause_element__()`` method properly. [ticket:2849]
* - The typing system now handles the task of rendering "literal bind" values,Mike Bayer2013-10-201-0/+13
| | | | | | | | | | | | | | | e.g. values that are normally bound parameters but due to context must be rendered as strings, typically within DDL constructs such as CHECK constraints and indexes (note that "literal bind" values become used by DDL as of :ticket:`2742`). A new method :meth:`.TypeEngine.literal_processor` serves as the base, and :meth:`.TypeDecorator.process_literal_param` is added to allow wrapping of a native literal rendering method. [ticket:2838] - enhance _get_colparams so that we can send flags like literal_binds into INSERT statements - add support in PG for inspecting standard_conforming_strings - add a new series of roundtrip tests based on INSERT of literal plus SELECT for basic literal rendering in dialect suite
* - add a type_coerce() step within Enum, Boolean to the CHECK constraint,Mike Bayer2013-10-201-1/+13
| | | | | | | | so that the custom type isn't exposed to an operation that is against the "impl" type's constraint, [ticket:2842] - this change showed up as some recursion overflow in pickling with labels, add a __reduce__() there....pickling of expressions is less and less something that's very viable...
* - The :meth:`.Table.tometadata` method now produces copies ofMike Bayer2013-10-181-0/+12
| | | | | | | | | | all :attr:`.SchemaItem.info` dictionaries from all :class:`.SchemaItem` objects within the structure including columns, constraints, foreign keys, etc. As these dictionaries are copies, they are independent of the original dictionary. Previously, only the ``.info`` dictionary of :class:`.Column` was transferred within this operation, and it was only linked in place, not copied. [ticket:2716]
* - add a "limitations of reflection" section, [ticket:2233]Mike Bayer2013-10-182-0/+35
|
* - Removed a 128-character truncation from the reflection of theMike Bayer2013-10-181-0/+9
| | | | | | server default for a column; this code was original from PG system views which truncated the string for readability. [ticket:2844]
* - The change in :ticket:`2721`, which is that the ``deferrable`` keywordMike Bayer2013-10-181-0/+20
| | | | | | | | | | | | | | | | | of :class:`.ForeignKeyConstraint` is silently ignored on the MySQL backend, will be reverted as of 0.9; this keyword will now render again, raising errors on MySQL as it is not understood - the same behavior will also apply to the ``initially`` keyword. In 0.8, the keywords will remain ignored but a warning is emitted. Additionally, the ``match`` keyword now raises a :class:`.CompileError` on 0.9 and emits a warning on 0.8; this keyword is not only silently ignored by MySQL but also breaks the ON UPDATE/ON DELETE options. To use a :class:`.ForeignKeyConstraint` that does not render or renders differently on MySQL, use a custom compilation option. An example of this usage has been added to the documentation, see :ref:`mysql_foreign_keys`. [ticket:2721] [ticket:2839]
* - Added support for rendering ``SMALLSERIAL`` when a :class:`.SmallInteger`Mike Bayer2013-10-151-0/+8
| | | | | | type is used on a primary key autoincrement column, based on server version detection of Postgresql version 9.2 or greater. [ticket:2840]
* The MySQL :class:`.mysql.SET` type now features the same auto-quotingMike Bayer2013-10-141-0/+10
| | | | | | | behavior as that of :class:`.mysql.ENUM`. Quotes are not required when setting up the value, but quotes that are present will be auto-detected along with a warning. This also helps with Alembic where the SET type doesn't render with quotes. [ticket:2817]
* The ``.unique`` flag on :class:`.Index` could be produced as ``None``Mike Bayer2013-10-141-0/+10
| | | | | | if it was generated from a :class:`.Column` that didn't specify ``unique`` (where it defaults to ``None``). The flag will now always be ``True`` or ``False``. [ticket:2825]
* migration guideMike Bayer2013-10-132-0/+45
|
* nameMike Bayer2013-10-131-1/+1
|
* - Added new option to :func:`.relationship` ``distinct_target_key``.Mike Bayer2013-10-131-0/+19
| | | | | | | | | | | | | | | This enables the subquery eager loader strategy to apply a DISTINCT to the innermost SELECT subquery, to assist in the case where duplicate rows are generated by the innermost query which corresponds to this relationship (there's not yet a general solution to the issue of dupe rows within subquery eager loading, however, when joins outside of the innermost subquery produce dupes). When the flag is set to ``True``, the DISTINCT is rendered unconditionally, and when it is set to ``None``, DISTINCT is rendered if the innermost relationship targets columns that do not comprise a full primary key. The option defaults to False in 0.8 (e.g. off by default in all cases), None in 0.9 (e.g. automatic by default). Thanks to Alexander Koval for help with this. [ticket:2836]
View Lorry Controller Status