JezK
Edit File: sqltypes.pyc
� 1��fc @ s d Z d d l Z d d l Z d d l Z d d l Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m Z d d l m! Z! d d l m" Z" d d l" m# Z# d d l" m$ Z$ d d l" m% Z% d d! l" m& Z& d" e' f d# � � YZ( d$ e' f d% � � YZ) d& e' f d' � � YZ* d( e) e f d) � � YZ+ d* e+ f d+ � � YZ, d, e+ f d- � � YZ- d. e, f d/ � � YZ. d0 e( e f d1 � � YZ/ d2 e/ f d3 � � YZ0 d4 e/ f d5 � � YZ1 d6 e( e f d7 � � YZ2 d8 e2 f d9 � � YZ3 d: e( e f d; � � YZ4 d< e( e f d= � � YZ5 d> e( e f d? � � YZ6 d@ e f dA � � YZ7 dB e7 f dC � � YZ8 dD e f dE � � YZ9 dF e e+ e9 f dG � � YZ: dH e f dI � � YZ; dJ e e e9 f dK � � YZ< dL e( e f dM � � YZ= dN e e= e f dO � � YZ> dP e* e f dQ � � YZ? dR e e* e) e f dS � � YZ@ dT e f dU � � YZA dV e3 f dW � � YZB dX e3 f dY � � YZC dZ e2 f d[ � � YZD d\ e2 f d] � � YZE d^ e/ f d_ � � YZF eF ZG d` e0 f da � � YZH db e1 f dc � � YZI dd e4 f de � � YZJ df e4 f dg � � YZK dh e5 f di � � YZL dj e6 f dk � � YZM dl e, f dm � � YZN dn e, f do � � YZO dp e+ f dq � � YZP dr e- f ds � � YZQ dt e+ f du � � YZR dv e- f dw � � YZS dx e8 f dy � � YZT dz e7 f d{ � � YZU d| e7 f d} � � YZV d~ e< f d � � YZW d� e f d� � � YZX d� e e f d� � � YZY d� e< f d� � � YZZ eX � Z[ e< � Z\ e+ � Z] e/ � Z^ e2 � Z_ eZ � Z` eY � Za e4 d� eb � Zc e6 d� eb � Zd i e/ � ee 6e3 � ef 6e\ eg 6e2 � e jh 6e5 � e ji 6e4 � e j 6e6 � e jj 6e> � e jk 6e[ e" jl 6Zm e" jn r}e8 � em eo <e- � em ep <n e- � em eq <e+ � em ep <em jr Zs d� � Zt e\ e _\ e] e _] e^ e _^ e[ e _[ e_ e __ e` e _` e* e _u ea e _a et e _t e\ e jv _\ d S(� s SQL specific types. i����Ni ( t coercions( t elements( t operators( t roles( t type_api( t _bind_or_error( t NO_ARG( t SchemaEventTarget( t _NONE_NAME( t quoted_name( t Slice( t TypeCoerce( t HasCacheKey( t InternalTraversal( t Emulated( t NativeForEmulated( t to_instance( t TypeDecorator( t TypeEngine( t Varianti ( t event( t exc( t inspection( t processors( t util( t compat( t langhelpers( t OrderedDict( t picklet _LookupExpressionAdapterc B s< e Z d Z e d � � Z d e j f d � � YZ e Z RS( s� Mixin expression adaptations based on lookup tables. These rules are currently used by the numeric, integer and date types which have detailed cross-expression coercion rules. c C s t � � d S( N( t NotImplementedError( t self( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _expression_adaptations9 s t Comparatorc B s e Z e j � Z d � Z RS( c C s� | j j } | j j j | | j � j | | j � } | | k rO | | j f S| | j j k rn | | j f S| t | � f Sd S( N( t typet _type_affinityR t gett _blank_dictR ( R t opt other_comparatort othertypet lookup( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _adapt_expression@ s ( t __name__t __module__R t immutabledictR% R* ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR! = s ( R+ R, t __doc__t propertyR R R! t comparator_factory( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR 0 s t Concatenablec B s- e Z d Z d e j f d � � YZ e Z RS( sO A mixin that marks a type as supporting 'concatenation', typically strings.R! c B s e Z d � Z RS( c C s] | t j k r= t | t j t j f � r= t j | j j f St t j | � j | | � Sd S( N( R t addt isinstanceR1 R! t NullTypet concat_opt exprR" t superR* ( R R& R' ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR* U s ( R+ R, R* ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR! T s ( R+ R, R. R R! R0 ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR1 O s t Indexablec B s- e Z d Z d e j f d � � YZ e Z RS( s� A mixin that marks a type as supporting indexing operations, such as array or JSON structures. .. versionadded:: 1.1.0 R! c B s e Z d � Z d � Z RS( c C s t � � d S( N( R ( R t index( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _setup_getitemn s c C s. | j | � \ } } } | j | | d | �S( Nt result_type( R: t operate( R R9 t adjusted_opt adjusted_right_exprR; ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt __getitem__q s ( R+ R, R: R? ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR! m s ( R+ R, R. R R! R0 ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR8 c s t Stringc B s� e Z d Z d Z e j d d � Z e j d d � Z e j d d � Z e j d d � Z e j d d d d � d d e d e e d � � Z d � Z d � Z d � Z e d � � Z d � Z e d � � Z RS( s� The base for all string and character types. In SQL, corresponds to VARCHAR. Can also take Python unicode objects and encode to the database's encoding in bind params (and the reverse for result sets.) The `length` field is usually required when the `String` type is used within a CREATE TABLE statement, as VARCHAR requires a length on most databases. t stringt RETURNS_UNICODEs Indicates that the DBAPI returns Python Unicode for VARCHAR, NVARCHAR, and other character-based datatypes in all cases. This is the default value for :attr:`.DefaultDialect.returns_unicode_strings` under Python 3. .. versionadded:: 1.4 t RETURNS_BYTESsR Indicates that the DBAPI returns byte objects under Python 3 or non-Unicode string objects under Python 2 for VARCHAR, NVARCHAR, and other character-based datatypes in all cases. This may be applied to the :attr:`.DefaultDialect.returns_unicode_strings` attribute. .. versionadded:: 1.4 t RETURNS_CONDITIONALs� Indicates that the DBAPI may return Unicode or bytestrings for VARCHAR, NVARCHAR, and other character-based datatypes, and that SQLAlchemy's default String datatype will need to test on a per-row basis for Unicode or bytes. This may be applied to the :attr:`.DefaultDialect.returns_unicode_strings` attribute. .. versionadded:: 1.4 t RETURNS_UNKNOWNs Indicates that the dialect should test on first connect what the string-returning behavior of character-based datatypes is. This is the default value for DefaultDialect.unicode_returns under Python 2. This may be applied to the :attr:`.DefaultDialect.returns_unicode_strings` attribute under Python 2 only. The value is disallowed under Python 3. .. versionadded:: 1.4 .. deprecated:: 1.4 This value will be removed in SQLAlchemy 2.0. t convert_unicodes 1.3s� The :paramref:`.String.convert_unicode` parameter is deprecated and will be removed in a future release. All modern DBAPIs now support Python Unicode directly and this parameter is unnecessary.t unicode_errors� The :paramref:`.String.unicode_errors` parameter is deprecated and will be removed in a future release. This parameter is unnecessary for modern Python DBAPIs and degrades performance significantly.c C sa | d k r* | d k r* t j d � � n | | _ | | _ | pE | | _ | | _ | | _ d S( sL Create a string-holding type. :param length: optional, a length for the column for use in DDL and CAST expressions. May be safely omitted if no ``CREATE TABLE`` will be issued. Certain databases may require a ``length`` for use in DDL, and will raise an exception when the ``CREATE TABLE`` DDL is issued if a ``VARCHAR`` with no length is included. Whether the value is interpreted as bytes or characters is database specific. :param collation: Optional, a column-level collation for use in DDL and CAST expressions. Renders using the COLLATE keyword supported by SQLite, MySQL, and PostgreSQL. E.g.:: >>> from sqlalchemy import cast, select, String >>> print(select(cast('some string', String(collation='utf8')))) SELECT CAST(:param_1 AS VARCHAR COLLATE utf8) AS anon_1 :param convert_unicode: When set to ``True``, the :class:`.String` type will assume that input is to be passed as Python Unicode objects under Python 2, and results returned as Python Unicode objects. In the rare circumstance that the DBAPI does not support Python unicode under Python 2, SQLAlchemy will use its own encoder/decoder functionality on strings, referring to the value of the :paramref:`_sa.create_engine.encoding` parameter parameter passed to :func:`_sa.create_engine` as the encoding. For the extremely rare case that Python Unicode is to be encoded/decoded by SQLAlchemy on a backend that *does* natively support Python Unicode, the string value ``"force"`` can be passed here which will cause SQLAlchemy's encode/decode services to be used unconditionally. .. note:: SQLAlchemy's unicode-conversion flags and features only apply to Python 2; in Python 3, all string objects are Unicode objects. For this reason, as well as the fact that virtually all modern DBAPIs now support Unicode natively even under Python 2, the :paramref:`.String.convert_unicode` flag is inherently a legacy feature. .. note:: In the vast majority of cases, the :class:`.Unicode` or :class:`.UnicodeText` datatypes should be used for a :class:`_schema.Column` that expects to store non-ascii data. These datatypes will ensure that the correct types are used on the database side as well as set up the correct Unicode behaviors under Python 2. .. seealso:: :paramref:`_sa.create_engine.convert_unicode` - :class:`_engine.Engine`-wide parameter :param unicode_error: Optional, a method to use to handle Unicode conversion errors. Behaves like the ``errors`` keyword argument to the standard library's ``string.decode()`` functions, requires that :paramref:`.String.convert_unicode` is set to ``"force"`` t forces: convert_unicode must be 'force' when unicode_error is set.N( t NoneR t ArgumentErrort lengtht collationt _expect_unicodet _expect_unicode_errort _warn_on_bytestring( R RK RL RF RG RO RM ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt __init__� s ] c s � f d � } | S( Nc s; | j d d � } � j j r3 | j d d � } n d | S( Nt 's ''t %s %%s '%s'( t replacet identifier_preparert _double_percents( t value( t dialect( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt process5 s ( ( R RW RX ( ( RW sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt literal_processor4 s c s� � j s | j r{ | j rG � j d k rG � j r@ d � } | Sd Sn0 t j | j � � � j � � � � f d � } | Sd Sd S( NRH c S s5 t | t j � r1 t j d t j | � f � n | S( Ns6 Unicode type received non-unicode bind param value %r.( R3 R t binary_typet warn_limitedt ellipses_string( RV ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX G s c s[ t | t j � r& � | � j � d S� rW | d k rW t j d t j | � f � n | S( Ni s6 Unicode type received non-unicode bind param value %r.( R3 R t text_typeRN RI R[ R\ ( RV ( t encoderR t warn_on_bytestring( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX W s ( RM RF t supports_unicode_bindsRO RI t codecst getencodert encoding( R RW RX ( ( R^ R R_ sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt bind_processor? s c C s� | j p | j } | o6 | j t j k p6 | j d k } | of | j t j t j f k of | j d k } | r� | r� t j | j | j � St j | j | j � Sn d Sd S( NRH t force_nocheck( RH Re ( RM RF t returns_unicode_stringsR@ RB RD R t( to_conditional_unicode_processor_factoryRc RN t to_unicode_processor_factoryRI ( R RW t coltypet wants_unicodet needs_convertt needs_isinstance( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt result_processorf s c C s | j r t j St Sd S( N( RM R R] t str( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt python_type� s c C s | j S( N( t STRING( R t dbapi( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt get_dbapi_type� s c C s t j d d d �d S( Ns The convert_unicode on Engine and String as well as the unicode_error flag on String are deprecated. All modern DBAPIs now support Python Unicode natively under Python 2, and under Python 3 all strings are inherently Unicode. These flags will be removed in a future release.t versions 1.3( R t warn_deprecated( t cls( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _warn_deprecated_unicode� s ( s 1.3s� The :paramref:`.String.convert_unicode` parameter is deprecated and will be removed in a future release. All modern DBAPIs now support Python Unicode directly and this parameter is unnecessary.( s 1.3s� The :paramref:`.String.unicode_errors` parameter is deprecated and will be removed in a future release. This parameter is unnecessary for modern Python DBAPIs and degrades performance significantly.N( R+ R, R. t __visit_name__R t symbolRB RC RD RE t deprecated_paramsRI t FalseRP RY Rd Rm R/ Ro Rr t classmethodRv ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR@ ~ s> R ' t Textc B s e Z d Z d Z RS( sj A variably sized string type. In SQL, usually corresponds to CLOB or TEXT. Can also take Python unicode objects and encode to the database's encoding in bind params (and the reverse for result sets.) In general, TEXT objects do not have a length; while some databases will accept a length argument here, it will be rejected by others. t text( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR| � s t Unicodec B s e Z d Z d Z d d � Z RS( s" A variable length Unicode string type. The :class:`.Unicode` type is a :class:`.String` subclass that assumes input and output strings that may contain non-ASCII characters, and for some backends implies an underlying column type that is explicitly supporting of non-ASCII data, such as ``NVARCHAR`` on Oracle and SQL Server. This will impact the output of ``CREATE TABLE`` statements and ``CAST`` functions at the dialect level, and also in some cases will indicate different behavior in the DBAPI itself in how it handles bound parameters. The character encoding used by the :class:`.Unicode` type that is used to transmit and receive data to the database is usually determined by the DBAPI itself. All modern DBAPIs accommodate non-ASCII strings but may have different methods of managing database encodings; if necessary, this encoding should be configured as detailed in the notes for the target DBAPI in the :ref:`dialect_toplevel` section. In modern SQLAlchemy, use of the :class:`.Unicode` datatype does not typically imply any encoding/decoding behavior within SQLAlchemy itself. Historically, when DBAPIs did not support Python ``unicode`` objects under Python 2, SQLAlchemy handled unicode encoding/decoding services itself which would be controlled by the flag :paramref:`.String.convert_unicode`; this flag is deprecated as it is no longer needed for Python 3. When using Python 2, data that is passed to columns that use the :class:`.Unicode` datatype must be of type ``unicode``, and not ``str`` which in Python 2 is equivalent to ``bytes``. In Python 3, all data passed to columns that use the :class:`.Unicode` datatype should be of type ``str``. See the flag :paramref:`.String.convert_unicode` for more discussion of unicode encode/decode behavior under Python 2. .. warning:: Some database backends, particularly SQL Server with pyodbc, are known to have undesirable behaviors regarding data that is noted as being of ``NVARCHAR`` type as opposed to ``VARCHAR``, including datatype mismatch errors and non-use of indexes. See the section on :meth:`.DialectEvents.do_setinputsizes` for background on working around unicode character issues for backends like SQL Server with pyodbc as well as cx_Oracle. .. seealso:: :class:`.UnicodeText` - unlengthed textual counterpart to :class:`.Unicode`. :paramref:`.String.convert_unicode` :meth:`.DialectEvents.do_setinputsizes` t unicodec K s@ | j d t � | j d t � t t | � j d | | � d S( s� Create a :class:`.Unicode` object. Parameters are the same as that of :class:`.String`, with the exception that ``convert_unicode`` defaults to ``True``. RM RO RK N( t setdefaultt TrueR7 R~ RP ( R RK t kwargs( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP � s N( R+ R, R. Rw RI RP ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR~ � s 4t UnicodeTextc B s) e Z d Z d Z d d � Z d � Z RS( s# An unbounded-length Unicode string type. See :class:`.Unicode` for details on the unicode behavior of this object. Like :class:`.Unicode`, usage the :class:`.UnicodeText` type implies a unicode-capable type being used on the backend, such as ``NCLOB``, ``NTEXT``. t unicode_textc K s@ | j d t � | j d t � t t | � j d | | � d S( s� Create a Unicode-converting Text type. Parameters are the same as that of :class:`_expression.TextClause`, with the exception that ``convert_unicode`` defaults to ``True``. RM RO RK N( R� R� R7 R� RP ( R RK R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP � s c C s d S( N( ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRv s N( R+ R, R. Rw RI RP Rv ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t Integerc B sG e Z d Z d Z d � Z e d � � Z d � Z e j d � � Z RS( s A type for ``int`` integers.t integerc C s | j S( N( t NUMBER( R Rq ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRr s c C s t S( N( t int( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo s c C s d � } | S( Nc S s t t | � � S( N( Rn R� ( RV ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX s ( ( R RW RX ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRY s c C s� i i t t 6| j t 6t t 6t j 6i t t 6| j t 6t t 6t j 6i | j t 6t t 6t j 6i | j t 6t t 6t j 6i | j t 6t t 6t j 6S( N( t Datet __class__R� t NumericR R2 t Intervalt mult divt truedivt sub( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR s ( R+ R, R. Rw Rr R/ Ro RY R t memoized_propertyR ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� s t SmallIntegerc B s e Z d Z d Z RS( s� A type for smaller ``int`` integers. Typically generates a ``SMALLINT`` in DDL, and otherwise acts like a normal :class:`.Integer` on the Python side. t small_integer( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� 4 s t BigIntegerc B s e Z d Z d Z RS( s� A type for bigger ``int`` integers. Typically generates a ``BIGINT`` in DDL, and otherwise acts like a normal :class:`.Integer` on the Python side. t big_integer( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� @ s R� c B s� e Z d Z d Z d Z d d d e d � Z e d � � Z d � Z d � Z e d � � Z d � Z d � Z e j d � � Z RS( s� Base for non-integer numeric types, such as ``NUMERIC``, ``FLOAT``, ``DECIMAL``, and other variants. The :class:`.Numeric` datatype when used directly will render DDL corresponding to precision numerics if available, such as ``NUMERIC(precision, scale)``. The :class:`.Float` subclass will attempt to render a floating-point datatype such as ``FLOAT(precision)``. :class:`.Numeric` returns Python ``decimal.Decimal`` objects by default, based on the default value of ``True`` for the :paramref:`.Numeric.asdecimal` parameter. If this parameter is set to False, returned values are coerced to Python ``float`` objects. The :class:`.Float` subtype, being more specific to floating point, defaults the :paramref:`.Float.asdecimal` flag to False so that the default Python datatype is ``float``. .. note:: When using a :class:`.Numeric` datatype against a database type that returns Python floating point values to the driver, the accuracy of the decimal conversion indicated by :paramref:`.Numeric.asdecimal` may be limited. The behavior of specific numeric/floating point datatypes is a product of the SQL datatype in use, the Python :term:`DBAPI` in use, as well as strategies that may be present within the SQLAlchemy dialect in use. Users requiring specific precision/ scale are encouraged to experiment with the available datatypes in order to determine the best results. t numerici c C s( | | _ | | _ | | _ | | _ d S( sw Construct a Numeric. :param precision: the numeric precision for use in DDL ``CREATE TABLE``. :param scale: the numeric scale for use in DDL ``CREATE TABLE``. :param asdecimal: default True. Return whether or not values should be sent as Python Decimal objects, or as floats. Different DBAPIs send one or the other based on datatypes - the Numeric type will ensure that return values are one or the other across DBAPIs consistently. :param decimal_return_scale: Default scale to use when converting from floats to Python decimals. Floating point values will typically be much longer due to decimal inaccuracy, and most floating point database types don't have a notion of "scale", so by default the float type looks for the first ten decimal places when converting. Specifying this value will override that length. Types which do include an explicit ".scale" value, such as the base :class:`.Numeric` as well as the MySQL float types, will use the value of ".scale" as the default for decimal_return_scale, if not otherwise specified. When using the ``Numeric`` type, care should be taken to ensure that the asdecimal setting is appropriate for the DBAPI in use - when Numeric applies a conversion from Decimal->float or float-> Decimal, this conversion incurs an additional performance overhead for all result columns received. DBAPIs that return Decimal natively (e.g. psycopg2) will have better accuracy and higher performance with a setting of ``True``, as the native translation to Decimal reduces the amount of floating- point issues at play, and the Numeric type itself doesn't need to apply any further conversions. However, another DBAPI which returns floats natively *will* incur an additional conversion overhead, and is still subject to floating point data loss - in which case ``asdecimal=False`` will at least remove the extra conversion overhead. N( t precisiont scalet decimal_return_scalet asdecimal( R R� R� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP q s 1 c C s@ | j d k r | j St | d d � d k r5 | j S| j Sd S( NR� ( R� RI t getattrR� t _default_decimal_return_scale( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _effective_decimal_return_scale� s c C s | j S( N( R� ( R Rq ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRr � s c C s d � } | S( Nc S s t | � S( N( Rn ( RV ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( ( R RW RX ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRY � s c C s | j r t j St Sd S( N( R� t decimalt Decimalt float( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo � s c C s | j r d St j Sd S( N( t supports_native_decimalRI R t to_float( R RW ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRd � s c C s| | j rd | j r d St j d | j | j f � t j t j | j d k rW | j n | j � Sn | j rt t j Sd Sd S( Ns� Dialect %s+%s does *not* support Decimal objects natively, and SQLAlchemy must convert from floating point - rounding errors and other issues may occur. Please consider storing Decimal numbers as strings or integers on this platform for lossless storage.( R� R� RI R t warnt namet driverR t to_decimal_processor_factoryR� R� R� R� R� ( R RW Ri ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm � s c C s� i i t t 6| j t 6| j t 6t j 6i | j t 6| j t 6t j 6i | j t 6| j t 6t j 6i | j t 6| j t 6t j 6i | j t 6| j t 6t j 6S( N( R� R� R� R� R R� R� R� R2 R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR � s N( R+ R, R. Rw R� RI R� RP R/ R� Rr RY Ro Rd Rm R R� R ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� L s 1 t Floatc B s5 e Z d Z d Z d Z d e d d � Z d � Z RS( s Type representing floating point types, such as ``FLOAT`` or ``REAL``. This type returns Python ``float`` objects by default, unless the :paramref:`.Float.asdecimal` flag is set to True, in which case they are coerced to ``decimal.Decimal`` objects. R� c C s | | _ | | _ | | _ d S( s� Construct a Float. :param precision: the numeric precision for use in DDL ``CREATE TABLE``. :param asdecimal: the same flag as that of :class:`.Numeric`, but defaults to ``False``. Note that setting this flag to ``True`` results in floating point conversion. :param decimal_return_scale: Default scale to use when converting from floats to Python decimals. Floating point values will typically be much longer due to decimal inaccuracy, and most floating point database types don't have a notion of "scale", so by default the float type looks for the first ten decimal places when converting. Specifying this value will override that length. Note that the MySQL float types, which do include "scale", will use "scale" as the default for decimal_return_scale, if not otherwise specified. .. versionadded:: 0.9.0 N( R� R� R� ( R R� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP s c C s7 | j r t j t j | j � S| j r/ t j Sd Sd S( N( R� R R� R� R� R� R� R� RI ( R RW Ri ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm ! s N( R+ R, R. Rw RI R� Rz RP Rm ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t DateTimec B sS e Z d Z d Z e d � Z d � Z d � Z e d � � Z e j d � � Z RS( s� A type for ``datetime.datetime()`` objects. Date and time types return objects from the Python ``datetime`` module. Most DBAPIs have built in support for the datetime module, with the noted exception of SQLite. In the case of SQLite, date and time types are stored as strings which are then converted back to datetime objects when rows are returned. For the time representation within the datetime type, some backends include additional options, such as timezone support and fractional seconds support. For fractional seconds, use the dialect-specific datatype, such as :class:`.mysql.TIME`. For timezone support, use at least the :class:`_types.TIMESTAMP` datatype, if not the dialect-specific datatype object. t datetimec C s | | _ d S( s� Construct a new :class:`.DateTime`. :param timezone: boolean. Indicates that the datetime type should enable timezone support, if available on the **base date/time-holding type only**. It is recommended to make use of the :class:`_types.TIMESTAMP` datatype directly when using this flag, as some databases include separate generic date/time-holding types distinct from the timezone-capable TIMESTAMP datatype, such as Oracle. N( t timezone( R R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP A s c C s | j S( N( t DATETIME( R Rq ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRr P s c C s+ | j d k } | r# | j r# t S| Sd S( N( t tzinfoRI R� t DATETIME_TIMEZONE( R RV t with_timezone( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _resolve_for_literalS s c C s t j S( N( t dtR� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo Z s c C s3 i i | j t 6t j 6i | j t 6t t 6t j 6S( N( R� R� R R2 R� R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR ^ s ( R+ R, R. Rw Rz RP Rr R� R/ Ro R R� R ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� , s R� c B s> e Z d Z d Z d � Z e d � � Z e j d � � Z RS( s' A type for ``datetime.date()`` objects.t datec C s | j S( N( R� ( R Rq ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRr p s c C s t j S( N( R� R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo s s c C sO i i | j t 6t t 6t t 6t j 6i | j t 6t t 6t t 6t t 6t j 6S( N( R� R� R� R� t TimeR R2 R� R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR w s ( R+ R, R. Rw Rr R/ Ro R R� R ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� j s R� c B sS e Z d Z d Z e d � Z d � Z e d � � Z d � Z e j d � � Z RS( s' A type for ``datetime.time()`` objects.t timec C s | | _ d S( N( R� ( R R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP � s c C s | j S( N( R� ( R Rq ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRr � s c C s t j S( N( R� R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo � s c C s+ | j d k } | r# | j r# t S| Sd S( N( R� RI R� t TIME_TIMEZONE( R RV R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s c C s: i i t t 6| j t 6t j 6i t t 6| j t 6t j 6S( N( R� R� R� R� R R2 R� R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR � s ( R+ R, R. Rw Rz RP Rr R/ Ro R� R R� R ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t _Binaryc B sk e Z d Z d d � Z d � Z e d � � Z d � Z e j rN d � Z n d � Z d � Z d � Z RS( s& Define base behavior for binary types.c C s | | _ d S( N( RK ( R RK ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP � s c s � f d � } | S( Nc s& | j � j � j d d � } d | S( NRQ s ''s '%s'( t decodeRc RS ( RV ( RW ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( ( R RW RX ( ( RW sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRY � s c C s t j S( N( R RZ ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo � s c s2 | j d k r d S| j j � � f d � } | S( Nc s | d k r � | � Sd Sd S( N( RI ( RV ( t DBAPIBinary( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( Rq RI t Binary( R RW RX ( ( R� sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRd � s c C s t j S( N( R t to_str( R RW Ri ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm � s c C s d � } | S( Nc S s | d k r t | � } n | S( N( RI t bytes( RV ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( ( R RW Ri RX ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm � s c C s3 t | t j � r | St t | � j | | � Sd S( s@ See :meth:`.TypeEngine.coerce_compared_value` for a description.N( R3 R t string_typesR7 R� t coerce_compared_value( R R& RV ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s c C s | j S( N( t BINARY( R Rq ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRr � s N( R+ R, R. RI RP RY R/ Ro Rd R t py2kRm R� Rr ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t LargeBinaryc B s e Z d Z d Z d d � Z RS( s A type for large binary byte data. The :class:`.LargeBinary` type corresponds to a large and/or unlengthed binary type for the target platform, such as BLOB on MySQL and BYTEA for PostgreSQL. It also handles the necessary conversions for the DBAPI. t large_binaryc C s t j | d | �d S( s� Construct a LargeBinary type. :param length: optional, a length for the column for use in DDL statements, for those binary types that accept a length, such as the MySQL BLOB type. RK N( R� RP ( R RK ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP � s N( R+ R, R. Rw RI RP ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t SchemaTypec B s� e Z d Z e Z d d d e d e d � Z d � Z d � Z d � Z d � Z d � Z e d � � Z d e d � Z d e d � Z d � Z d � Z d � Z d � Z d � Z RS( sb Mark a type as possibly requiring schema-level DDL for usage. Supports types that must be explicitly created/dropped (i.e. PG ENUM type) as well as types that are complimented by table or schema level constraints, triggers, and other rules. :class:`.SchemaType` classes can also be targets for the :meth:`.DDLEvents.before_parent_attach` and :meth:`.DDLEvents.after_parent_attach` events, where the events fire off surrounding the association of the type object with a parent :class:`_schema.Column`. .. seealso:: :class:`.Enum` :class:`.Boolean` c C s� | d k r! t | | � | _ n d | _ | | _ | | _ | | _ | | _ | r� | j r� t j | j d t j | j � � t j | j d t j | j � � n d S( Nt before_createt after_drop( RI R R� t schemat metadatat inherit_schemat _create_eventsR t listenR t portable_instancemethodt _on_metadata_createt _on_metadata_drop( R R� R� R� R� t quoteR� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP # s c K s | j t j | j � � d S( N( t _on_table_attachR R� t _set_table( R t columnt kw( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _set_parentA s c C sA t | j t � r7 | j j j � } | j j | d <n d } | S( Nt _default( R3 R" R t mappingt copyt implRI ( R R� t variant_mapping( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _variant_mapping_for_set_tableD s c C s* | j r | j | _ n6 | j rN | j d k rN | j j rN | j j | _ n | j s[ d S| j | � } t j | d t j | j i | d 6� � t j | d t j | j i | d 6� � | j d k r&t j | j d t j | j i | d 6� � t j | j d t j | j i | d 6� � n d S( NR� R� R� ( R� R� R� RI R� R� R R� R R� t _on_table_createt _on_table_dropR� R� ( R R� t tableR� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� L s< $ c K s | j | j d t �S( NR� ( t adaptR� R� ( R R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� y s c K sj | j d | j � } | j d | j � } | j d t � } | d | j d | d | j d | d | | � S( NR� R� R� R� R� ( t popR� R� Rz R� R� ( R t impltypeR� R� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� | s c C s | j r | j j p d S( N( R� t bindRI ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s c C sk | d k r t | � } n | j | j � } | j | j k rg t | t � rg | j d | d | � n d S( s. Issue CREATE DDL for this type, if applicable.R� t checkfirstN( RI R t dialect_implRW R� R3 R� t create( R R� R� t t( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s !c C sk | d k r t | � } n | j | j � } | j | j k rg t | t � rg | j d | d | � n d S( s, Issue DROP DDL for this type, if applicable.R� R� N( RI R R� RW R� R3 R� t drop( R R� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s !c K sf | j | j | � s d S| j | j � } | j | j k rb t | t � rb | j | | | � n d S( N( t _is_impl_for_variantRW R� R� R3 R� R� ( R t targetR� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s !c K sf | j | j | � s d S| j | j � } | j | j k rb t | t � rb | j | | | � n d S( N( R� RW R� R� R3 R� R� ( R R� R� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s !c K sf | j | j | � s d S| j | j � } | j | j k rb t | t � rb | j | | | � n d S( N( R� RW R� R� R3 R� R� ( R R� R� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s !c K sf | j | j | � s d S| j | j � } | j | j k rb t | t � rb | j | | | � n d S( N( R� RW R� R� R3 R� R� ( R R� R� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s !c sx | j d d � } | d k r" t S� f d � } | j | k rW | | | j � rW t S| j | k rt | | d � Sd S( NR� c s( | � k p' t | t � o' | j � k S( N( R3 t ARRAYt item_type( t typ( R ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _we_are_the_impl� s R� ( R� RI R� R� ( R RW R� R� R� ( ( R sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s N( R+ R, R. R� t _use_schema_mapRI Rz RP R� R� R� R� R� R/ R� R� R� R� R� R� R� R� ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� s* - t Enumc B s# e Z d Z d Z e j d d � d � � Z e d � � Z d � Z d � Z d � Z e d � � Z e d � � Z d � Z d e j f d � � YZ e Z d � Z d � Z e d � Z d � Z d � Z d � Z e j d � d � � Z d � Z d � Z d � Z d � Z e d � � Z RS( s7 Generic Enum Type. The :class:`.Enum` type provides a set of possible string values which the column is constrained towards. The :class:`.Enum` type will make use of the backend's native "ENUM" type if one is available; otherwise, it uses a VARCHAR datatype. An option also exists to automatically produce a CHECK constraint when the VARCHAR (so called "non-native") variant is produced; see the :paramref:`.Enum.create_constraint` flag. The :class:`.Enum` type also provides in-Python validation of string values during both read and write operations. When reading a value from the database in a result set, the string value is always checked against the list of possible values and a ``LookupError`` is raised if no match is found. When passing a value to the database as a plain string within a SQL statement, if the :paramref:`.Enum.validate_strings` parameter is set to True, a ``LookupError`` is raised for any string value that's not located in the given list of possible values; note that this impacts usage of LIKE expressions with enumerated values (an unusual use case). .. versionchanged:: 1.1 the :class:`.Enum` type now provides in-Python validation of input values as well as on data being returned by the database. The source of enumerated values may be a list of string values, or alternatively a PEP-435-compliant enumerated class. For the purposes of the :class:`.Enum` datatype, this class need only provide a ``__members__`` method. When using an enumerated class, the enumerated objects are used both for input and output, rather than strings as is the case with a plain-string enumerated type:: import enum from sqlalchemy import Enum class MyEnum(enum.Enum): one = 1 two = 2 three = 3 t = Table( 'data', MetaData(), Column('value', Enum(MyEnum)) ) connection.execute(t.insert(), {"value": MyEnum.two}) assert connection.scalar(t.select()) is MyEnum.two Above, the string names of each element, e.g. "one", "two", "three", are persisted to the database; the values of the Python Enum, here indicated as integers, are **not** used; the value of each enum can therefore be any kind of Python object whether or not it is persistable. In order to persist the values and not the names, the :paramref:`.Enum.values_callable` parameter may be used. The value of this parameter is a user-supplied callable, which is intended to be used with a PEP-435-compliant enumerated class and returns a list of string values to be persisted. For a simple enumeration that uses string values, a callable such as ``lambda x: [e.value for e in x]`` is sufficient. .. versionadded:: 1.1 - support for PEP-435-style enumerated classes. .. seealso:: :class:`_postgresql.ENUM` - PostgreSQL-specific type, which has additional functionality. :class:`.mysql.ENUM` - MySQL-specific type t enumRF s 1.3s� The :paramref:`.Enum.convert_unicode` parameter is deprecated and will be removed in a future release. All modern DBAPIs now support Python Unicode directly and this parameter is unnecessary.c O s | j | | � d S( s2 Construct an enum. Keyword arguments which don't apply to a specific backend are ignored by that backend. :param \*enums: either exactly one PEP-435 compliant enumerated type or one or more string labels. .. versionadded:: 1.1 a PEP-435 style enumerated class may be passed. :param convert_unicode: Enable unicode-aware bind parameter and result-set processing for this Enum's data under Python 2 only. Under Python 2, this is set automatically based on the presence of unicode label strings. This flag will be removed in SQLAlchemy 2.0. :param create_constraint: defaults to False. When creating a non-native enumerated type, also build a CHECK constraint on the database against the valid values. .. note:: it is strongly recommended that the CHECK constraint have an explicit name in order to support schema-management concerns. This can be established either by setting the :paramref:`.Enum.name` parameter or by setting up an appropriate naming convention; see :ref:`constraint_naming_conventions` for background. .. versionchanged:: 1.4 - this flag now defaults to False, meaning no CHECK constraint is generated for a non-native enumerated type. :param metadata: Associate this type directly with a ``MetaData`` object. For types that exist on the target database as an independent schema construct (PostgreSQL), this type will be created and dropped within ``create_all()`` and ``drop_all()`` operations. If the type is not associated with any ``MetaData`` object, it will associate itself with each ``Table`` in which it is used, and will be created when any of those individual tables are created, after a check is performed for its existence. The type is only dropped when ``drop_all()`` is called for that ``Table`` object's metadata, however. The value of the :paramref:`_schema.MetaData.schema` parameter of the :class:`_schema.MetaData` object, if set, will be used as the default value of the :paramref:`_types.Enum.schema` on this object if an explicit value is not otherwise supplied. .. versionchanged:: 1.4.12 :class:`_types.Enum` inherits the :paramref:`_schema.MetaData.schema` parameter of the :class:`_schema.MetaData` object if present, when passed using the :paramref:`_types.Enum.metadata` parameter. :param name: The name of this type. This is required for PostgreSQL and any future supported database which requires an explicitly named type, or an explicitly named constraint in order to generate the type and/or a table that uses it. If a PEP-435 enumerated class was used, its name (converted to lower case) is used by default. :param native_enum: Use the database's native ENUM type when available. Defaults to True. When False, uses VARCHAR + check constraint for all backends. When False, the VARCHAR length can be controlled with :paramref:`.Enum.length`; currently "length" is ignored if native_enum=True. :param length: Allows specifying a custom length for the VARCHAR when :paramref:`.Enum.native_enum` is False. By default it uses the length of the longest value. .. versionadded:: 1.3.16 :param schema: Schema name of this type. For types that exist on the target database as an independent schema construct (PostgreSQL), this parameter specifies the named schema in which the type is present. If not present, the schema name will be taken from the :class:`_schema.MetaData` collection if passed as :paramref:`_types.Enum.metadata`, for a :class:`_schema.MetaData` that includes the :paramref:`_schema.MetaData.schema` parameter. .. versionchanged:: 1.4.12 :class:`_types.Enum` inherits the :paramref:`_schema.MetaData.schema` parameter of the :class:`_schema.MetaData` object if present, when passed using the :paramref:`_types.Enum.metadata` parameter. Otherwise, if the :paramref:`_types.Enum.inherit_schema` flag is set to ``True``, the schema will be inherited from the associated :class:`_schema.Table` object if any; when :paramref:`_types.Enum.inherit_schema` is at its default of ``False``, the owning table's schema is **not** used. :param quote: Set explicit quoting preferences for the type's name. :param inherit_schema: When ``True``, the "schema" from the owning :class:`_schema.Table` will be copied to the "schema" attribute of this :class:`.Enum`, replacing whatever value was passed for the ``schema`` attribute. This also takes effect when using the :meth:`_schema.Table.to_metadata` operation. :param validate_strings: when True, string values that are being passed to the database in a SQL statement will be checked for validity against the list of enumerated values. Unrecognized values will result in a ``LookupError`` being raised. .. versionadded:: 1.1.0b2 :param values_callable: A callable which will be passed the PEP-435 compliant enumerated type, which should then return a list of string values to be persisted. This allows for alternate usages such as using the string value of an enum to be persisted to the database instead of its name. .. versionadded:: 1.2.3 :param sort_key_function: a Python callable which may be used as the "key" argument in the Python ``sorted()`` built-in. The SQLAlchemy ORM requires that primary key columns which are mapped must be sortable in some way. When using an unsortable enumeration object such as a Python 3 ``Enum`` object, this parameter may be used to set a default sort key function for the objects. By default, the database value of the enumeration is used as the sorting function. .. versionadded:: 1.3.8 :param omit_aliases: A boolean that when true will remove aliases from pep 435 enums. For backward compatibility it defaults to ``False``. A deprecation warning is raised if the enum has aliases and this flag was not set. .. versionadded:: 1.4.5 .. deprecated:: 1.4 The default will be changed to ``True`` in SQLAlchemy 2.0. N( t _enum_init( R t enumsR� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP # s �c C s$ | j d k r | j g S| j Sd S( N( t enum_classRI R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _enums_argument� s c C s� | j d t � | _ | j d t � | _ | j d d � | _ | j d t � | _ | j d t � } | j d t � | _ | j d t � } | j | | � \ } } | j | | | � | j d d � } | j d t � | _ | d k r$x< | j D]" } t | t j � r� t } Pq� q� Wt } n | } | j rVt d � | j D� � | _ } n d | _ } | t k r�| j r�| s�t j d � q�q�| r�| | k r�t d | | f � � n | } n d | j d <| j d <t t | � j d | d | � | j r%| j d | j j j � � n t j | d | j d d � d | j d d � d | j d d � d | j d t � d | j d d � d | j d t � �d S( s� internal init for :class:`.Enum` and subclasses. friendly init helper used by subclasses to remove all the Enum-specific keyword arguments from kw. Allows all other arguments in kw to pass through. t native_enumt create_constraintt values_callablet sort_key_functionRK t omit_aliasest _disable_warningsRF t validate_stringsc s s | ] } t | � Vq d S( N( t len( t .0t x( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pys <genexpr>� s i s� Enum 'length' argument is currently ignored unless native_enum is specified as False, including for DDL that renders VARCHAR in any case. This may change in a future release.s` When provided, length must be larger or equal than the length of the longest enum value. %s < %sRM R� R� R� R� R� R� N( R� R� R� Rz R� RI R� R t _sort_key_functiont _omit_aliasest _parse_into_valuest _setup_for_valuesR� R� R3 R R] t maxt _default_lengthR� t ValueErrort _valid_lookupt _object_lookupR7 R� RP R� R� R+ t lowerR� ( R R� R� t length_argR� t valuest objectsRF t eRM RK ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � sX # c C sh | r% d | k r% | j d � } n t | � d k rQt | d d � rQ| d | _ | j j } g | j � D]! \ } } | j | k rp | ^ qp } | j t k r� | r� t j d | j j | f � n | j t k r� t d � | j � D� � } n | } | j r | j | j � } n t | � } g | D] } | | ^ q1} | | f Sd | _ | | f Sd S( Nt _enumsi i t __members__s� The provided enum %s contains the aliases %s. The ``omit_aliases`` will default to ``True`` in SQLAlchemy 2.0. Specify a value to silence this warning.c s s0 | ]& \ } } | j | k r | | f Vq d S( N( R� ( R� t nt v( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pys <genexpr> s ( R� R� t hasattrR� R t itemsR� R� R R t warn_deprecated_20R+ R� R R� t listRI ( R R� R� t _membersR R t aliasest membersR t kR ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� s* % 4 c C s� t | � | _ t t t | � t | � � � | _ t t | | � � | _ | j j g | D] } | | j | j | f ^ q[ � d S( N( R R� t dictt zipt reversedR R t update( R R R R� RV ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� - s $ c C s! | j t k r | j S| j Sd S( N( R� R t _db_value_for_elem( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� ; s c C s | j S( N( R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt nativeB s c C s~ y | j | SWnh t k ry } | j rA t | t j � rA | St j t d | | j t j | j � f � d | �n Xd S( NsM '%s' is not among the defined enum values. Enum name: %s. Possible values: %st replace_context( R t KeyErrorR� R3 R R� R t raise_t LookupErrorR� R t repr_tuple_namesR� ( R t elemt err( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR F s R! c B s e Z d � Z RS( c C s^ t t j | � j | | � \ } } | t j k rT t | j j d | j j �} n | | f S( NRM ( R7 R� R! R* R R5 R@ R" RK RM ( R R& R' R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR* e s ( R+ R, R* ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR! d s c C s^ y | j | SWnH t k rY } t j t d | | j t j | j � f � d | �n Xd S( NsM '%s' is not among the defined enum values. Enum name: %s. Possible values: %sR ( R R R R R R� R R R� ( R R R! ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _object_value_for_elemq s c C s= t j | d d t f d t f d | j f g d t t g �S( Nt additional_kwR� R� RK t to_inspect( R t generic_reprR� Rz R R� R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt __repr__� s c C sC t | d � r | j } n t d � � t j | | j d t | �S( NR� sp TypeEngine.as_generic() heuristic is undefined for types that inherit Enum but do not have an `enums` attribute.R� ( R R� R R t constructor_copyt _generic_type_affinityR� ( R t allow_nulltypet args( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt as_generic� s c K s | j d | j � | j d | j � | j d | j � t | d <| j d | j � | j d | j � | j d | j � | j d t � | j d | j � | j d | j � | j d | j � | j d | j � | j d | j � d | k s� t � | | � S( NRM R� R� R� R� R� R� R� R� R� R� RK R� R ( R� RM R� R� R� R� R� R� Rz R� R� R� RK R� t AssertionError( R R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt adapt_to_emulated� s c K s0 | j | d <t | d <t t | � j | | � S( NR R� ( R� R� R7 R� R� ( R R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s c K s. | j | j | � s t S| j p- | j j S( N( R� RW Rz R� t supports_native_enum( R t compilerR� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _should_create_constraint� s s sqlalchemy.sql.schemac C s� t j j } t j | | | � | j s, d S| j | � } | j t | t � � j | j � d | j d k rt t n | j d t j | j i | d 6� d t �} | j | k s� t � d S( NR� t _create_ruleR� t _type_bound( R t preloadedt sql_schemaR� R� R� R� t CheckConstraintt type_coerceR@ t in_R� R� RI R R� R0 R� R� R, ( R R� R� R� R� R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s c s. t t � � j | � � � � f d � } | S( Nc s( � j | � } � r$ � | � } n | S( N( R ( RV ( t parent_processorR ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( R7 R� RY ( R RW RX ( ( R8 R sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRY � s c s. t t � � j | � � � � f d � } | S( Nc s( � j | � } � r$ � | � } n | S( N( R ( RV ( R8 R ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( R7 R� Rd ( R RW RX ( ( R8 R sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRd � s c s1 t t � � j | | � � � � f d � } | S( Nc s( � r � | � } n � j | � } | S( N( R" ( RV ( R8 R ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( R7 R� Rm ( R RW Ri RX ( ( R8 R sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm � s c K s t j | | � S( N( R� R� ( R R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s c C s$ | j r | j St t | � j Sd S( N( R� R7 R� Ro ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo � s ( s 1.3s� The :paramref:`.Enum.convert_unicode` parameter is deprecated and will be removed in a future release. All modern DBAPIs now support Python Unicode directly and this parameter is unnecessary.( R+ R, R. Rw R Ry RP R/ R� R� R� R� R� R R R@ R! R0 R" R& Rz R+ R- R� R0 t preload_moduleR� RY Rd Rm R� Ro ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s4 L � J " t PickleTypec B sV e Z d Z e Z e Z e j d d d d � Z d � Z d � Z d � Z d � Z RS( s� Holds Python objects, which are serialized using pickle. PickleType builds upon the Binary type to apply Python's ``pickle.dumps()`` to incoming objects, and ``pickle.loads()`` on the way out, allowing any pickleable Python object to be stored as a serialized binary field. To allow ORM change events to propagate for elements associated with :class:`.PickleType`, see :ref:`mutable_toplevel`. c C sP | | _ | p t | _ | | _ t t | � j � | rL t | � | _ n d S( s Construct a PickleType. :param protocol: defaults to ``pickle.HIGHEST_PROTOCOL``. :param pickler: defaults to cPickle.pickle or pickle.pickle if cPickle is not available. May be any object with pickle-compatible ``dumps`` and ``loads`` methods. :param comparator: a 2-arg callable predicate used to compare values of this type. If left as ``None``, the Python "equals" operator is used to compare values. :param impl: A binary-storing :class:`_types.TypeEngine` class or instance to use in place of the default :class:`_types.LargeBinary`. For example the :class: `_mysql.LONGBLOB` class may be more effective when using MySQL. .. versionadded:: 1.4.20 N( t protocolR t picklert comparatorR7 R: RP R R� ( R R; R< R= R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP s c C s t | j d | j f f S( N( R: R; RI R= ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt __reduce__. s c s[ | j j | � � | j j � | j � � rE � � � f d � } n � � f d � } | S( Nc s( | d k r � | � � } n � | � S( N( RI ( RV ( t dumpst impl_processorR; ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX 7 s c s" | d k r � | � � } n | S( N( RI ( RV ( R? R; ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX > s ( R� Rd R< R? R; ( R RW RX ( ( R? R@ R; sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRd 1 s c sO | j j | | � � | j j � � r< � � f d � } n � f d � } | S( Nc s& � | � } | d k r d S� | � S( N( RI ( RV ( R@ t loads( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX J s c s | d k r d S� | � S( N( RI ( RV ( RA ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX R s ( R� Rm R< RA ( R RW Ri RX ( ( R@ RA sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm E s c C s' | j r | j | | � S| | k Sd S( N( R= ( R R� t y( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt compare_valuesY s N( R+ R, R. R� R� R� t cache_okR t HIGHEST_PROTOCOLRI RP R> Rd Rm RC ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR: � s t Booleanc B s� e Z d Z d Z e Z e d e d � Z d � Z e j d � d � � Z e d � � Z e d e e g � Z d � Z d � Z d � Z d � Z RS( s� A bool datatype. :class:`.Boolean` typically uses BOOLEAN or SMALLINT on the DDL side, and on the Python side deals in ``True`` or ``False``. The :class:`.Boolean` datatype currently has two levels of assertion that the values persisted are simple true/false values. For all backends, only the Python values ``None``, ``True``, ``False``, ``1`` or ``0`` are accepted as parameter values. For those backends that don't support a "native boolean" datatype, an option exists to also create a CHECK constraint on the target column .. versionchanged:: 1.2 the :class:`.Boolean` datatype now asserts that incoming Python values are already in pure boolean form. t booleanc C s | | _ | | _ | | _ d S( s� Construct a Boolean. :param create_constraint: defaults to False. If the boolean is generated as an int/smallint, also create a CHECK constraint on the table that ensures 1 or 0 as a value. .. note:: it is strongly recommended that the CHECK constraint have an explicit name in order to support schema-management concerns. This can be established either by setting the :paramref:`.Boolean.name` parameter or by setting up an appropriate naming convention; see :ref:`constraint_naming_conventions` for background. .. versionchanged:: 1.4 - this flag now defaults to False, meaning no CHECK constraint is generated for a non-native enumerated type. :param name: if a CHECK constraint is generated, specify the name of the constraint. N( R� R� R� ( R R� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP w s c K s0 | j | j | � s t S| j j o/ | j j S( N( R� RW Rz t supports_native_booleant# non_native_boolean_check_constraint( R R/ R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR0 � s s sqlalchemy.sql.schemac C s� t j j } | j s d S| j | � } | j t | | � j d d g � d | j d k ra t n | j d t j | j i | d 6� d t �} | j | k s� t � d S( Ni i R� R1 R� R2 ( R R3 R4 R� R� R5 R6 R7 R� RI R R� R0 R� R� R, ( R R� R� R� R� R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s c C s t S( N( t bool( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo � s c C sN | | j k rJ t | t � s4 t d | f � � qJ t d | f � � n | S( Ns Not a boolean value: %rs$ Value %r is not None, True, or False( t _strict_boolsR3 R� t TypeErrorR ( R RV ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _strict_as_bool� s c sI | j | d � } | j d � � | j d � � � � � f d � } | S( Nc s � j | � r � S� S( N( RM ( RV ( t falseR t true( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( t statement_compilerRI t visit_truet visit_false( R RW R/ RX ( ( RN R RO sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRY � s c s7 | j � | j r t � n t � � � f d � } | S( Nc s+ � | � } | d k r' � | � } n | S( N( RI ( RV ( t _coerceRM ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( RM RH RJ R� ( R RW RX ( ( RS RM sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRd � s c C s | j r d St j Sd S( N( RH RI R t int_to_boolean( R RW Ri ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm � s N( R+ R, R. Rw R� R Rz RI RP R0 R R9 R� R/ Ro t frozensetRK RM RY Rd Rm ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRF ` s t _AbstractIntervalc B s2 e Z e j d � � Z e d � � Z d � Z RS( c C s} i i t t 6| j t 6t t 6t t 6t j 6i | j t 6t j 6i | j t 6t j 6i | j t 6t j 6i | j t 6t j 6S( N( R� R� R� R� R� R R2 R� R� R� R� R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR � s c C s t S( N( R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR# � s c C s | j j | | � S( s@ See :meth:`.TypeEngine.coerce_compared_value` for a description.( R� R� ( R R& RV ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s ( R+ R, R R� R R/ R# R� ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRV � s R� c B s� e Z d Z e Z e j r0 e j j d � Z n' e j j d e j j � j d d � Z e Z e d d d � Z e d � � Z d � Z d � Z d � Z RS( s� A type for ``datetime.timedelta()`` objects. The Interval type deals with ``datetime.timedelta`` objects. In PostgreSQL, the native ``INTERVAL`` type is used; for others, the value is stored as a date which is relative to the "epoch" (Jan. 1, 1970). Note that the ``Interval`` type does not currently provide date arithmetic operations on platforms which do not support interval types natively. Such operations usually require transformation of both sides of the expression (such as, conversion of both sides into integer epoch values first) which currently is a manual procedure (such as via :attr:`~sqlalchemy.sql.expression.func`). i R� c C s2 t t | � j � | | _ | | _ | | _ d S( s; Construct an Interval object. :param native: when True, use the actual INTERVAL type provided by the database, if supported (currently PostgreSQL, Oracle). Otherwise, represent the interval data as an epoch value regardless. :param second_precision: For native interval types which support a "fractional seconds precision" parameter, i.e. Oracle and PostgreSQL :param day_precision: for native interval types which support a "day precision" parameter, i.e. Oracle. N( R7 R� RP R t second_precisiont day_precision( R R RW RX ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP s c C s t j S( N( R� t timedelta( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo + s c K s t j | | | � S( N( RV R� ( R R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR- / s c sI | j j | � � | j � � r6 � � f d � } n � f d � } | S( Nc s# | d k r � | } n � | � S( N( RI ( RV ( t epochR@ ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX 7 s c s | d k r � | } n | S( N( RI ( RV ( RZ ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX > s ( R� Rd RZ ( R RW RX ( ( RZ R@ sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRd 2 s c sL | j j | | � � | j � � r9 � � f d � } n � f d � } | S( Nc s$ � | � } | d k r d S| � S( N( RI ( RV ( RZ R@ ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX J s c s | d k r d S| � S( N( RI ( RV ( RZ ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX R s ( R� Rm RZ ( R RW Ri RX ( ( RZ R@ sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm E s N( R+ R, R. R� R� R R� R� R� t utcfromtimestampRZ t fromtimestampR� t utcRS RI R� RD RP R/ Ro R- Rd Rm ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t JSONc B s e Z d Z d Z e Z e j d � Z e d � Z d e f d � � YZ d e f d � � YZ d e f d � � YZ d e f d � � YZ d e f d � � YZ d e j e j f d � � YZ e Z e d � � Z e d � � Z e j d � � Z e j d � � Z d � Z d � Z RS( s� Represent a SQL JSON type. .. note:: :class:`_types.JSON` is provided as a facade for vendor-specific JSON types. Since it supports JSON SQL operations, it only works on backends that have an actual JSON type, currently: * PostgreSQL - see :class:`sqlalchemy.dialects.postgresql.JSON` and :class:`sqlalchemy.dialects.postgresql.JSONB` for backend-specific notes * MySQL - see :class:`sqlalchemy.dialects.mysql.JSON` for backend-specific notes * SQLite as of version 3.9 - see :class:`sqlalchemy.dialects.sqlite.JSON` for backend-specific notes * Microsoft SQL Server 2016 and later - see :class:`sqlalchemy.dialects.mssql.JSON` for backend-specific notes :class:`_types.JSON` is part of the Core in support of the growing popularity of native JSON datatypes. The :class:`_types.JSON` type stores arbitrary JSON format data, e.g.:: data_table = Table('data_table', metadata, Column('id', Integer, primary_key=True), Column('data', JSON) ) with engine.connect() as conn: conn.execute( data_table.insert(), {"data": {"key1": "value1", "key2": "value2"}} ) **JSON-Specific Expression Operators** The :class:`_types.JSON` datatype provides these additional SQL operations: * Keyed index operations:: data_table.c.data['some key'] * Integer index operations:: data_table.c.data[3] * Path index operations:: data_table.c.data[('key_1', 'key_2', 5, ..., 'key_n')] * Data casters for specific JSON element types, subsequent to an index or path operation being invoked:: data_table.c.data["some key"].as_integer() .. versionadded:: 1.3.11 Additional operations may be available from the dialect-specific versions of :class:`_types.JSON`, such as :class:`sqlalchemy.dialects.postgresql.JSON` and :class:`sqlalchemy.dialects.postgresql.JSONB` which both offer additional PostgreSQL-specific operations. **Casting JSON Elements to Other Types** Index operations, i.e. those invoked by calling upon the expression using the Python bracket operator as in ``some_column['some key']``, return an expression object whose type defaults to :class:`_types.JSON` by default, so that further JSON-oriented instructions may be called upon the result type. However, it is likely more common that an index operation is expected to return a specific scalar element, such as a string or integer. In order to provide access to these elements in a backend-agnostic way, a series of data casters are provided: * :meth:`.JSON.Comparator.as_string` - return the element as a string * :meth:`.JSON.Comparator.as_boolean` - return the element as a boolean * :meth:`.JSON.Comparator.as_float` - return the element as a float * :meth:`.JSON.Comparator.as_integer` - return the element as an integer These data casters are implemented by supporting dialects in order to assure that comparisons to the above types will work as expected, such as:: # integer comparison data_table.c.data["some_integer_key"].as_integer() == 5 # boolean comparison data_table.c.data["some_boolean"].as_boolean() == True .. versionadded:: 1.3.11 Added type-specific casters for the basic JSON data element types. .. note:: The data caster functions are new in version 1.3.11, and supersede the previous documented approaches of using CAST; for reference, this looked like:: from sqlalchemy import cast, type_coerce from sqlalchemy import String, JSON cast( data_table.c.data['some_key'], String ) == type_coerce(55, JSON) The above case now works directly as:: data_table.c.data['some_key'].as_integer() == 5 For details on the previous comparison approach within the 1.3.x series, see the documentation for SQLAlchemy 1.2 or the included HTML files in the doc/ directory of the version's distribution. **Detecting Changes in JSON columns when using the ORM** The :class:`_types.JSON` type, when used with the SQLAlchemy ORM, does not detect in-place mutations to the structure. In order to detect these, the :mod:`sqlalchemy.ext.mutable` extension must be used, most typically using the :class:`.MutableDict` class. This extension will allow "in-place" changes to the datastructure to produce events which will be detected by the unit of work. See the example at :class:`.HSTORE` for a simple example involving a dictionary. Alternatively, assigning a JSON structure to an ORM element that replaces the old one will always trigger a change event. **Support for JSON null vs. SQL NULL** When working with NULL values, the :class:`_types.JSON` type recommends the use of two specific constants in order to differentiate between a column that evaluates to SQL NULL, e.g. no value, vs. the JSON-encoded string of ``"null"``. To insert or select against a value that is SQL NULL, use the constant :func:`.null`. This symbol may be passed as a parameter value specifically when using the :class:`_types.JSON` datatype, which contains special logic that interprets this symbol to mean that the column value should be SQL NULL as opposed to JSON ``"null"``:: from sqlalchemy import null conn.execute(table.insert(), {"json_value": null()}) To insert or select against a value that is JSON ``"null"``, use the constant :attr:`_types.JSON.NULL`:: conn.execute(table.insert(), {"json_value": JSON.NULL}) The :class:`_types.JSON` type supports a flag :paramref:`_types.JSON.none_as_null` which when set to True will result in the Python constant ``None`` evaluating to the value of SQL NULL, and when set to False results in the Python constant ``None`` evaluating to the value of JSON ``"null"``. The Python value ``None`` may be used in conjunction with either :attr:`_types.JSON.NULL` and :func:`.null` in order to indicate NULL values, but care must be taken as to the value of the :paramref:`_types.JSON.none_as_null` in these cases. **Customizing the JSON Serializer** The JSON serializer and deserializer used by :class:`_types.JSON` defaults to Python's ``json.dumps`` and ``json.loads`` functions; in the case of the psycopg2 dialect, psycopg2 may be using its own custom loader function. In order to affect the serializer / deserializer, they are currently configurable at the :func:`_sa.create_engine` level via the :paramref:`_sa.create_engine.json_serializer` and :paramref:`_sa.create_engine.json_deserializer` parameters. For example, to turn off ``ensure_ascii``:: engine = create_engine( "sqlite://", json_serializer=lambda obj: json.dumps(obj, ensure_ascii=False)) .. versionchanged:: 1.3.7 SQLite dialect's ``json_serializer`` and ``json_deserializer`` parameters renamed from ``_json_serializer`` and ``_json_deserializer``. .. seealso:: :class:`sqlalchemy.dialects.postgresql.JSON` :class:`sqlalchemy.dialects.postgresql.JSONB` :class:`sqlalchemy.dialects.mysql.JSON` :class:`sqlalchemy.dialects.sqlite.JSON` .. versionadded:: 1.1 R^ t JSON_NULLc C s | | _ d S( s� Construct a :class:`_types.JSON` type. :param none_as_null=False: if True, persist the value ``None`` as a SQL NULL value, not the JSON encoding of ``null``. Note that when this flag is False, the :func:`.null` construct can still be used to persist a NULL value, which may be passed directly as a parameter value that is specially interpreted by the :class:`_types.JSON` type as SQL NULL:: from sqlalchemy import null conn.execute(table.insert(), {"data": null()}) .. note:: :paramref:`_types.JSON.none_as_null` does **not** apply to the values passed to :paramref:`_schema.Column.default` and :paramref:`_schema.Column.server_default`; a value of ``None`` passed for these parameters means "no default present". Additionally, when used in SQL comparison expressions, the Python value ``None`` continues to refer to SQL null, and not JSON NULL. The :paramref:`_types.JSON.none_as_null` flag refers explicitly to the **persistence** of the value within an INSERT or UPDATE statement. The :attr:`_types.JSON.NULL` value should be used for SQL expressions that wish to compare to JSON null. .. seealso:: :attr:`.types.JSON.NULL` N( t none_as_null( R R` ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP P s !t JSONElementTypec B sD e Z d Z e � Z e � Z d � Z d � Z d � Z d � Z RS( s? Common function for index / path elements in a JSON expression.c C s | j j | � S( N( t _stringt _cached_bind_processor( R RW ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt string_bind_processory s c C s | j j | � S( N( Rb t _cached_literal_processor( R RW ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt string_literal_processor| s c s7 | j j | � � | j | � � � � f d � } | S( Nc sO � r$ t | t � r$ � | � } n' � rK t | t j � rK � | � } n | S( N( R3 R� R R� ( RV ( t int_processort string_processor( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( t _integerRc Rd ( R RW RX ( ( Rg Rh sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRd s c s7 | j j | � � | j | � � � � f d � } | S( Nc sO � r$ t | t � r$ � | � } n' � rK t | t j � rK � | � } n | S( N( R3 R� R R� ( RV ( Rg Rh ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX � s ( Ri Re Rf ( R RW RX ( ( Rg Rh sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRY � s ( R+ R, R. R� Ri R@ Rb Rd Rf Rd RY ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRa s s t JSONIndexTypec B s e Z d Z RS( s� Placeholder for the datatype of a JSON index value. This allows execution-time processing of JSON index values for special syntaxes. ( R+ R, R. ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRj � s t JSONIntIndexTypec B s e Z d Z RS( s� Placeholder for the datatype of a JSON index value. This allows execution-time processing of JSON index values for special syntaxes. ( R+ R, R. ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRk � s t JSONStrIndexTypec B s e Z d Z RS( s� Placeholder for the datatype of a JSON index value. This allows execution-time processing of JSON index values for special syntaxes. ( R+ R, R. ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRl � s t JSONPathTypec B s e Z d Z RS( s� Placeholder type for JSON path operations. This allows execution-time processing of a path-based index value into a specific SQL syntax. ( R+ R, R. ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm � s R! c B sY e Z d Z d � Z d � Z d � Z d � Z d � Z e d � Z d � Z d � Z RS( s6 Define comparison operations for :class:`_types.JSON`.c C s� t | t j � rd t | t j j � rd t j t j | d | j d t j d t j �} t j } nQ t j t j | d | j d t j d t | t � r� t j n t j �} t j } | | | j f S( NR6 t operatort bindparam_type( R3 R R� R t collections_abct SequenceR t expectR t BinaryElementRoleR6 R t json_path_getitem_opR^ Rm t json_getitem_opR� Rk Rl R" ( R R9 Rn ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR: � s$ c C s | j t � d � S( sD Cast an indexed value as boolean. e.g.:: stmt = select( mytable.c.json_column['some_data'].as_boolean() ).where( mytable.c.json_column['some_data'].as_boolean() == True ) .. versionadded:: 1.3.11 t as_boolean( t _binary_w_typeRF ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRv � s c C s | j t � d � S( s^ Cast an indexed value as string. e.g.:: stmt = select( mytable.c.json_column['some_data'].as_string() ).where( mytable.c.json_column['some_data'].as_string() == 'some string' ) .. versionadded:: 1.3.11 t as_string( Rw R@ ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRx � s c C s | j t � d � S( sA Cast an indexed value as integer. e.g.:: stmt = select( mytable.c.json_column['some_data'].as_integer() ).where( mytable.c.json_column['some_data'].as_integer() == 5 ) .. versionadded:: 1.3.11 t as_integer( Rw R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRy � s c C s | j t � d � S( s? Cast an indexed value as float. e.g.:: stmt = select( mytable.c.json_column['some_data'].as_float() ).where( mytable.c.json_column['some_data'].as_float() == 29.75 ) .. versionadded:: 1.3.11 t as_float( Rw R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRz s c C s | j t | | d | �d � S( sm Cast an indexed value as numeric/decimal. e.g.:: stmt = select( mytable.c.json_column['some_data'].as_numeric(10, 6) ).where( mytable.c. json_column['some_data'].as_numeric(10, 6) == 29.75 ) .. versionadded:: 1.4.0b2 R� t as_numeric( Rw R� ( R R� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR{ s c C s | j S( s� Cast an indexed value as JSON. e.g.:: stmt = select(mytable.c.json_column['some_data'].as_json()) This is typically the default behavior of indexed elements in any case. Note that comparison of full JSON structures may not be supported by all backends. .. versionadded:: 1.3.11 ( R6 ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt as_json+ s c C sl t | j t j � s4 | j j t j t j f k rP t j d | | f � � n | j j � } | | _ | S( Ns[ The JSON cast operator JSON.%s() only works with a JSON index expression e.g. col['q'].%s()( R3 R6 R t BinaryExpressionRn R Ru Rt R t InvalidRequestErrort _cloneR" ( R R� t method_nameR6 ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRw = s ( R+ R, R. R: Rv Rx Ry Rz R� R{ R| Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR! � s c C s t S( N( R ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo O s c C s | j S( s) Alias of :attr:`_types.JSON.none_as_null`( R` ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt should_evaluate_noneS s c C s | | _ d S( N( R` ( R RV ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� X s c C s t d t � S( NRM ( R@ R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _str_impl\ s c s= � j j | � � | j p! t j � � � � f d � } | S( Nc sh | � j k r d } n+ t | t j � s? | d k rC � j rC d S� | � } � rd � | � } n | S( N( t NULLRI R3 R t NullR` ( RV t serialized( t json_serializerR t string_process( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX e s ( R� Rd t _json_serializert jsonR? ( R RW RX ( ( R� R R� sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRd ` s c s= | j j | | � � | j p$ t j � � � f d � } | S( Nc s/ | d k r d S� r% � | � } n � | � S( N( RI ( RV ( t json_deserializerR� ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRX x s ( R� Rm t _json_deserializerR� RA ( R RW Ri RX ( ( R� R� sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm t s ( R+ R, R. Rw Rz t hashableR Rx R� RP R Ra Rj Rk Rl Rm R8 R! R1 R0 R/ Ro R� t setterR� R� Rd Rm ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR^ Z s$ �, #& � R� c B s� e Z d Z d Z e Z e Z d e j e j f d � � YZ e Z e d e d � Z e d � � Z e d � � Z d � Z e d � Z d � Z RS( s Represent a SQL Array type. .. note:: This type serves as the basis for all ARRAY operations. However, currently **only the PostgreSQL backend has support for SQL arrays in SQLAlchemy**. It is recommended to use the PostgreSQL-specific :class:`sqlalchemy.dialects.postgresql.ARRAY` type directly when using ARRAY types with PostgreSQL, as it provides additional operators specific to that backend. :class:`_types.ARRAY` is part of the Core in support of various SQL standard functions such as :class:`_functions.array_agg` which explicitly involve arrays; however, with the exception of the PostgreSQL backend and possibly some third-party dialects, no other SQLAlchemy built-in dialect has support for this type. An :class:`_types.ARRAY` type is constructed given the "type" of element:: mytable = Table("mytable", metadata, Column("data", ARRAY(Integer)) ) The above type represents an N-dimensional array, meaning a supporting backend such as PostgreSQL will interpret values with any number of dimensions automatically. To produce an INSERT construct that passes in a 1-dimensional array of integers:: connection.execute( mytable.insert(), {"data": [1,2,3]} ) The :class:`_types.ARRAY` type can be constructed given a fixed number of dimensions:: mytable = Table("mytable", metadata, Column("data", ARRAY(Integer, dimensions=2)) ) Sending a number of dimensions is optional, but recommended if the datatype is to represent arrays of more than one dimension. This number is used: * When emitting the type declaration itself to the database, e.g. ``INTEGER[][]`` * When translating Python values to database values, and vice versa, e.g. an ARRAY of :class:`.Unicode` objects uses this number to efficiently access the string values inside of array structures without resorting to per-row type inspection * When used with the Python ``getitem`` accessor, the number of dimensions serves to define the kind of type that the ``[]`` operator should return, e.g. for an ARRAY of INTEGER with two dimensions:: >>> expr = table.c.column[5] # returns ARRAY(Integer, dimensions=1) >>> expr = expr[6] # returns Integer For 1-dimensional arrays, an :class:`_types.ARRAY` instance with no dimension parameter will generally assume single-dimensional behaviors. SQL expressions of type :class:`_types.ARRAY` have support for "index" and "slice" behavior. The Python ``[]`` operator works normally here, given integer indexes or slices. Arrays default to 1-based indexing. The operator produces binary expression constructs which will produce the appropriate SQL, both for SELECT statements:: select(mytable.c.data[5], mytable.c.data[2:7]) as well as UPDATE statements when the :meth:`_expression.Update.values` method is used:: mytable.update().values({ mytable.c.data[5]: 7, mytable.c.data[2:7]: [1, 2, 3] }) The :class:`_types.ARRAY` type also provides for the operators :meth:`.types.ARRAY.Comparator.any` and :meth:`.types.ARRAY.Comparator.all`. The PostgreSQL-specific version of :class:`_types.ARRAY` also provides additional operators. .. container:: topic **Detecting Changes in ARRAY columns when using the ORM** The :class:`_sqltypes.ARRAY` type, when used with the SQLAlchemy ORM, does not detect in-place mutations to the array. In order to detect these, the :mod:`sqlalchemy.ext.mutable` extension must be used, using the :class:`.MutableList` class:: from sqlalchemy import ARRAY from sqlalchemy.ext.mutable import MutableList class SomeOrmClass(Base): # ... data = Column(MutableList.as_mutable(ARRAY(Integer))) This extension will allow "in-place" changes such to the array such as ``.append()`` to produce events which will be detected by the unit of work. Note that changes to elements **inside** the array, including subarrays that are mutated in place, are **not** detected. Alternatively, assigning a new array value to an ORM element that replaces the old one will always trigger a change event. .. versionadded:: 1.1.0 .. seealso:: :class:`sqlalchemy.dialects.postgresql.ARRAY` R� R! c B sV e Z d Z d � Z d � Z e j d � d d � � Z e j d � d d � � Z RS( s� Define comparison operations for :class:`_types.ARRAY`. More operators are available on the dialect-specific form of this type. See :class:`.postgresql.ARRAY.Comparator`. c C s t | t � r� | j } | j j rJ t | j d | j d | j � } n t | j | j | j d | j j �} t j | | f S| j j r� | d 7} n | j j d k s� | j j d k r� | j j } n2 i | j j d d 6} | j j | j j | � } t j | | f Sd S( Ni t _namet dimensions( R3 t sliceR" t zero_indexest startt stopt stepR R6 t keyR t getitemR� RI R� R� R� ( R R9 t return_typet slice_t adapt_kw( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR: s &$ $ c O s t d � � d S( s� ``ARRAY.contains()`` not implemented for the base ARRAY type. Use the dialect-specific ARRAY type. .. seealso:: :class:`_postgresql.ARRAY` - PostgreSQL specific version. sd ARRAY.contains() not implemented for the base ARRAY type; please use the dialect-specific ARRAY typeN( R ( R t argR� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt contains s s sqlalchemy.sql.elementsc C sv t j j } | r | n t j } | j } | j t j t j d | d | d | j d | j �| j j | j � | � S( sS Return ``other operator ANY (array)`` clause. .. note:: This method is an :class:`_types.ARRAY` - specific construct that is now superseded by the :func:`_sql.any_` function, which features a different calling style. The :func:`_sql.any_` function is also mirrored at the method level via the :meth:`_sql.ColumnOperators.any_` method. Usage of array-specific :meth:`_types.ARRAY.Comparator.any` is as follows:: from sqlalchemy.sql import operators conn.execute( select(table.c.data).where( table.c.data.any(7, operator=operators.lt) ) ) :param other: expression to be compared :param operator: an operator object from the :mod:`sqlalchemy.sql.operators` package, defaults to :func:`.operators.eq`. .. seealso:: :func:`_expression.any_` :meth:`.types.ARRAY.Comparator.all` t elementRn R6 Ro ( R R3 t sql_elementsR t eqR" R} R Rr R Rs R6 R� t CollectionAggregatet _create_any( R t otherRn R t arr_type( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt any- s ! c C sv t j j } | r | n t j } | j } | j t j t j d | d | d | j d | j �| j j | j � | � S( sS Return ``other operator ALL (array)`` clause. .. note:: This method is an :class:`_types.ARRAY` - specific construct that is now superseded by the :func:`_sql.any_` function, which features a different calling style. The :func:`_sql.any_` function is also mirrored at the method level via the :meth:`_sql.ColumnOperators.any_` method. Usage of array-specific :meth:`_types.ARRAY.Comparator.all` is as follows:: from sqlalchemy.sql import operators conn.execute( select(table.c.data).where( table.c.data.all(7, operator=operators.lt) ) ) :param other: expression to be compared :param operator: an operator object from the :mod:`sqlalchemy.sql.operators` package, defaults to :func:`.operators.eq`. .. seealso:: :func:`_expression.all_` :meth:`.types.ARRAY.Comparator.any` R� Rn R6 Ro ( R R3 R� R R� R" R} R Rr R Rs R6 R� R� t _create_all( R R� Rn R R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt alla s ! N( R+ R, R. R: R� R R9 RI R� R� ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR! s 3 c C sa t | t � r t d � � n t | t � r9 | � } n | | _ | | _ | | _ | | _ d S( s� Construct an :class:`_types.ARRAY`. E.g.:: Column('myarray', ARRAY(Integer)) Arguments are: :param item_type: The data type of items of this array. Note that dimensionality is irrelevant here, so multi-dimensional arrays like ``INTEGER[][]``, are constructed as ``ARRAY(Integer)``, not as ``ARRAY(ARRAY(Integer))`` or such. :param as_tuple=False: Specify whether return results should be converted to tuples from lists. This parameter is not generally needed as a Python list corresponds well to a SQL array. :param dimensions: if non-None, the ARRAY will assume a fixed number of dimensions. This impacts how the array is declared on the database, how it goes about interpreting Python and result values, as well as how expression behavior in conjunction with the "getitem" operator works. See the description at :class:`_types.ARRAY` for additional detail. :param zero_indexes=False: when True, index values will be converted between Python zero-based and SQL one-based indexes, e.g. a value of one will be added to all index values before passing to the database. sU Do not nest ARRAY types; ARRAY(basetype) handles multi-dimensional arrays of basetypeN( R3 R� R R" R� t as_tupleR� R� ( R R� R� R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP � s " c C s | j S( N( R� ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s c C s t S( N( R ( R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRo � s c C s | | k S( N( ( R R� RB ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRC � s c K s3 | r/ t | j t � r/ | j j | | � n d S( s Support SchemaEventTargetN( R3 R� R R� ( R R� t outerR� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s c C sE t t | � j | d t �t | j t � rA | j j | � n d S( s Support SchemaEventTargetR� N( R7 R� t _set_parent_with_dispatchR� R3 R� R ( R t parent( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s N( R+ R, R. Rw R� t _is_arrayRz R� R8 R! R1 R0 RI RP R/ R� Ro RC R� R� ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s u �- t TupleTypec B s/ e Z d Z e Z d � Z d � Z d � Z RS( s( represent the composite type of a Tuple.c G sG t | k | _ g | D]$ } t | t � r4 | � n | ^ q | _ d S( N( t NULLTYPEt _fully_typedR3 R" t types( R R� R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP � s c C sX | j r | St g t | j | � D]* \ } } | t k rG t | � n | ^ q# � Sd S( N( R� R� R R� R� t _resolve_value_to_type( R RV R� R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt _resolve_values_to_types� s c C s t d � � d S( NsJ The tuple type does not support being fetched as a column in a result row.( R ( R RW Ri ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRm � s ( R+ R, R. R� t _is_tuple_typeRP R� Rm ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t REALc B s e Z d Z d Z RS( s The SQL REAL type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t FLOATc B s e Z d Z d Z RS( s The SQL FLOAT type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� s t NUMERICc B s e Z d Z d Z RS( s The SQL NUMERIC type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� s t DECIMALc B s e Z d Z d Z RS( s The SQL DECIMAL type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� s t INTEGERc B s e Z d Z d Z RS( s The SQL INT or INTEGER type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� s t SMALLINTc B s e Z d Z d Z RS( s The SQL SMALLINT type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� # s t BIGINTc B s e Z d Z d Z RS( s The SQL BIGINT type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� * s t TIMESTAMPc B s) e Z d Z d Z e d � Z d � Z RS( s The SQL TIMESTAMP type. :class:`_types.TIMESTAMP` datatypes have support for timezone storage on some backends, such as PostgreSQL and Oracle. Use the :paramref:`~types.TIMESTAMP.timezone` argument in order to enable "TIMESTAMP WITH TIMEZONE" for these backends. R� c C s t t | � j d | � d S( sm Construct a new :class:`_types.TIMESTAMP`. :param timezone: boolean. Indicates that the TIMESTAMP type should enable timezone support, if available on the target database. On a per-dialect basis is similar to "TIMESTAMP WITH TIMEZONE". If the target database does not support timezones, this flag is ignored. R� N( R7 R� RP ( R R� ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP > s c C s | j S( N( R� ( R Rq ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRr K s ( R+ R, R. Rw Rz RP Rr ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� 1 s R� c B s e Z d Z d Z RS( s The SQL DATETIME type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� O s t DATEc B s e Z d Z d Z RS( s The SQL DATE type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� V s t TIMEc B s e Z d Z d Z RS( s The SQL TIME type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� ] s t TEXTc B s e Z d Z d Z RS( s The SQL TEXT type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� d s t CLOBc B s e Z d Z d Z RS( sC The CLOB type. This type is found in Oracle and Informix. R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� k s t VARCHARc B s e Z d Z d Z RS( s The SQL VARCHAR type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� u s t NVARCHARc B s e Z d Z d Z RS( s The SQL NVARCHAR type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� | s t CHARc B s e Z d Z d Z RS( s The SQL CHAR type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t NCHARc B s e Z d Z d Z RS( s The SQL NCHAR type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t BLOBc B s e Z d Z d Z RS( s The SQL BLOB type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s R� c B s e Z d Z d Z RS( s The SQL BINARY type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t VARBINARYc B s e Z d Z d Z RS( s The SQL VARBINARY type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t BOOLEANc B s e Z d Z d Z RS( s The SQL BOOLEAN type.R� ( R+ R, R. Rw ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s R4 c B sB e Z d Z d Z e Z d � Z d e j f d � � YZ e Z RS( s An unknown type. :class:`.NullType` is used as a default type for those cases where a type cannot be determined, including: * During table reflection, when the type of a column is not recognized by the :class:`.Dialect` * When constructing SQL expressions using plain Python objects of unknown types (e.g. ``somecolumn == my_special_object``) * When a new :class:`_schema.Column` is created, and the given type is passed as ``None`` or is not passed at all. The :class:`.NullType` can be used within SQL expression invocation without issue, it just has no behavior either at the expression construction level or at the bind-parameter/result processing level. :class:`.NullType` will result in a :exc:`.CompileError` if the compiler is asked to render the type itself, such as if it is used in a :func:`.cast` operation or within a schema creation operation such as that invoked by :meth:`_schema.MetaData.create_all` or the :class:`.CreateTable` construct. t nullc C s d S( N( RI ( R RW ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRY � s R! c B s e Z d � Z RS( c C sF t | t j � s" t j | � r2 | | j j f S| j | | � Sd S( N( R3 R4 R! R t is_commutativeR6 R" R* ( R R& R' ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR* � s ( R+ R, R* ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR! � s ( R+ R, R. Rw R� t _isnullRY R R! R0 ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR4 � s t TableValueTypec B s/ e Z d Z e Z d e j f g Z d � Z RS( s Refers to a table value type.t _elementsc G s/ g | D] } t j t j | � ^ q | _ d S( N( R Rr R t StrAsPlainColumnRoleR� ( R R R ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyRP � s ( R+ R, R. R� t _is_table_valueR t dp_clauseelement_listt _traverse_internalsRP ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s t MatchTypec B s e Z d Z RS( sD Refers to the return type of the MATCH operator. As the :meth:`.ColumnOperators.match` is probably the most open-ended operator in generic SQLAlchemy Core, we can't assume the return type at SQL evaluation time, as MySQL returns a floating point, not a boolean, and other backends might do something different. So this type acts as a placeholder, currently subclassing :class:`.Boolean`. The type allows dialects to inject result-processing functionality if needed, and on MySQL will return floating-point values. .. versionadded:: 1.0.0 ( R+ R, R. ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� � s R� c C s t t | � t � } | t k rn t j | t � } | d k rj | j t j k rj t j d | f � � n t S| j | � Sd S( Ns- Object %r is not legal as a SQL literal value( t _type_map_getR" Rz R t inspectRI R� t _registrarsR RJ R� R� ( RV t _result_typet insp( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyR� s (w R. Ra R� R� R� R� t R R R R R t baseR R R R R R R R6 t traversalsR R R R R R R R R R R R R R R R R t objectR R1 R8 R@ R| R~ R� R� R� R� R� R� R� R� R� R� R� R� R� R: RF RV R� R^ R� R� R� R� R� R� R� t INTR� R� R� R� R� R� R� R� R� R� R� R� R� R� R� R� R4 R� R� R� t BOOLEANTYPEt STRINGTYPEt INTEGERTYPEt NUMERICTYPEt MATCHTYPEt TABLEVALUER� R� R� R� R� RJ R� R� R� RY t NoneTypet _type_mapt py3kR� Rn R R$ R� R� t INDEXABLER! ( ( ( sJ /opt/alt/python27/lib64/python2.7/site-packages/sqlalchemy/sql/sqltypes.pyt <module> s� � F ( �7>&"@� � � )f ~ `� � * � ^ .