sticky_pi_api.database package¶
Submodules¶
sticky_pi_api.database.images_table module¶
-
class
sticky_pi_api.database.images_table.
Images
(file)[source]¶ Bases:
sqlalchemy.ext.declarative.api.Base
,sticky_pi_api.database.utils.BaseCustomisations
-
alt
¶
-
api_version
¶
-
datetime
¶
-
datetime_created
¶
-
device
¶
-
device_version
¶
-
property
file_blob
¶
-
property
filename
¶
-
height
¶
-
hum
¶
-
id
¶
-
lat
¶
-
lng
¶
-
md5
¶
-
no_flash_bv
¶
-
no_flash_exposure_time
¶
-
no_flash_iso
¶
-
no_flash_shutter_speed
¶
-
temp
¶
-
property
thumbnail
¶
-
property
thumbnail_mini
¶
-
uploader
¶
-
width
¶
-
sticky_pi_api.database.uid_annotations_table module¶
sticky_pi_api.database.users_tables module¶
sticky_pi_api.database.utils module¶
-
class
sticky_pi_api.database.utils.
DescribedColumn
(col_type, description='', *args, **kwargs)[source]¶ Bases:
sqlalchemy.sql.schema.Column
Construct a new
Column
object.- Parameters
name –
The name of this column as represented in the database. This argument may be the first positional argument, or specified via keyword.
Names which contain no upper case characters will be treated as case insensitive names, and will not be quoted unless they are a reserved word. Names with any number of upper case characters will be quoted and sent exactly. Note that this behavior applies even for databases which standardize upper case names as case insensitive such as Oracle.
The name field may be omitted at construction time and applied later, at any time before the Column is associated with a
_schema.Table
. This is to support convenient usage within thedeclarative
extension.type_ –
The column’s type, indicated using an instance which subclasses
TypeEngine
. If no arguments are required for the type, the class of the type can be sent as well, e.g.:# use a type with arguments Column('data', String(50)) # use no arguments Column('level', Integer)
The
type
argument may be the second positional argument or specified by keyword.If the
type
isNone
or is omitted, it will first default to the special typeNullType
. If and when this_schema.Column
is made to refer to another column using_schema.ForeignKey
and/or_schema.ForeignKeyConstraint
, the type of the remote-referenced column will be copied to this column as well, at the moment that the foreign key is resolved against that remote_schema.Column
object.Changed in version 0.9.0: Support for propagation of type to a
_schema.Column
from its_schema.ForeignKey
object has been improved and should be more reliable and timely.*args – Additional positional arguments include various
SchemaItem
derived constructs which will be applied as options to the column. These include instances ofConstraint
,_schema.ForeignKey
,ColumnDefault
,Sequence
,Computed
. In some cases an equivalent keyword argument is available such asserver_default
,default
andunique
.autoincrement –
Set up “auto increment” semantics for an integer primary key column. The default value is the string
"auto"
which indicates that a single-column primary key that is of an INTEGER type with no stated client-side or python-side defaults should receive auto increment semantics automatically; all other varieties of primary key columns will not. This includes that DDL such as PostgreSQL SERIAL or MySQL AUTO_INCREMENT will be emitted for this column during a table create, as well as that the column is assumed to generate new integer primary key values when an INSERT statement invokes which will be retrieved by the dialect.The flag may be set to
True
to indicate that a column which is part of a composite (e.g. multi-column) primary key should have autoincrement semantics, though note that only one column within a primary key may have this setting. It can also be set toTrue
to indicate autoincrement semantics on a column that has a client-side or server-side default configured, however note that not all dialects can accommodate all styles of default as an “autoincrement”. It can also be set toFalse
on a single-column primary key that has a datatype of INTEGER in order to disable auto increment semantics for that column.Changed in version 1.1: The autoincrement flag now defaults to
"auto"
which indicates autoincrement semantics by default for single-column integer primary keys only; for composite (multi-column) primary keys, autoincrement is never implicitly enabled; as always,autoincrement=True
will allow for at most one of those columns to be an “autoincrement” column.autoincrement=True
may also be set on a_schema.Column
that has an explicit client-side or server-side default, subject to limitations of the backend database and dialect.The setting only has an effect for columns which are:
Integer derived (i.e. INT, SMALLINT, BIGINT).
Part of the primary key
Not referring to another column via
_schema.ForeignKey
, unless the value is specified as'ignore_fk'
:# turn on autoincrement for this column despite # the ForeignKey() Column('id', ForeignKey('other.id'), primary_key=True, autoincrement='ignore_fk')
It is typically not desirable to have “autoincrement” enabled on a column that refers to another via foreign key, as such a column is required to refer to a value that originates from elsewhere.
The setting has these two effects on columns that meet the above criteria:
DDL issued for the column will include database-specific keywords intended to signify this column as an “autoincrement” column, such as AUTO INCREMENT on MySQL, SERIAL on PostgreSQL, and IDENTITY on MS-SQL. It does not issue AUTOINCREMENT for SQLite since this is a special SQLite flag that is not required for autoincrementing behavior.
See also
The column will be considered to be available using an “autoincrement” method specific to the backend database, such as calling upon
cursor.lastrowid
, using RETURNING in an INSERT statement to get at a sequence-generated value, or using special functions such as “SELECT scope_identity()”. These methods are highly specific to the DBAPIs and databases in use and vary greatly, so care should be taken when associatingautoincrement=True
with a custom default generation function.
default –
A scalar, Python callable, or
_expression.ColumnElement
expression representing the default value for this column, which will be invoked upon insert if this column is otherwise not specified in the VALUES clause of the insert. This is a shortcut to usingColumnDefault
as a positional argument; see that class for full detail on the structure of the argument.Contrast this argument to :paramref:`_schema.Column.server_default` which creates a default generator on the database side.
See also
doc – optional String that can be used by the ORM or similar to document attributes on the Python side. This attribute does not render SQL comments; use the :paramref:`_schema.Column.comment` parameter for this purpose.
key – An optional string identifier which will identify this
Column
object on the_schema.Table
. When a key is provided, this is the only identifier referencing theColumn
within the application, including ORM attribute mapping; thename
field is used only when rendering SQL.index – When
True
, indicates that the column is indexed. This is a shortcut for using aIndex
construct on the table. To specify indexes with explicit names or indexes that contain multiple columns, use theIndex
construct instead.info – Optional data dictionary which will be populated into the
SchemaItem.info
attribute of this object.nullable – When set to
False
, will cause the “NOT NULL” phrase to be added when generating DDL for the column. WhenTrue
, will normally generate nothing (in SQL this defaults to “NULL”), except in some very specific backend-specific edge cases where “NULL” may render explicitly. Defaults toTrue
unless :paramref:`_schema.Column.primary_key` is alsoTrue
, in which case it defaults toFalse
. This parameter is only used when issuing CREATE TABLE statements.onupdate –
A scalar, Python callable, or
ClauseElement
representing a default value to be applied to the column within UPDATE statements, which will be invoked upon update if this column is not present in the SET clause of the update. This is a shortcut to usingColumnDefault
as a positional argument withfor_update=True
.See also
Column INSERT/UPDATE Defaults - complete discussion of onupdate
primary_key – If
True
, marks this column as a primary key column. Multiple columns can have this flag set to specify composite primary keys. As an alternative, the primary key of a_schema.Table
can be specified via an explicitPrimaryKeyConstraint
object.server_default –
A
FetchedValue
instance, str, Unicode ortext()
construct representing the DDL DEFAULT value for the column.String types will be emitted as-is, surrounded by single quotes:
Column('x', Text, server_default="val") x TEXT DEFAULT 'val'
A
text()
expression will be rendered as-is, without quotes:Column('y', DateTime, server_default=text('NOW()')) y DATETIME DEFAULT NOW()
Strings and text() will be converted into a
DefaultClause
object upon initialization.Use
FetchedValue
to indicate that an already-existing column will generate a default value on the database side which will be available to SQLAlchemy for post-fetch after inserts. This construct does not specify any DDL and the implementation is left to the database, such as via a trigger.See also
Server-invoked DDL-Explicit Default Expressions - complete discussion of server side defaults
server_onupdate –
A
FetchedValue
instance representing a database-side default generation function, such as a trigger. This indicates to SQLAlchemy that a newly generated value will be available after updates. This construct does not actually implement any kind of generation function within the database, which instead must be specified separately.Warning
This directive does not currently produce MySQL’s “ON UPDATE CURRENT_TIMESTAMP()” clause. See Rendering ON UPDATE CURRENT TIMESTAMP for MySQL / MariaDB’s explicit_defaults_for_timestamp for background on how to produce this clause.
quote – Force quoting of this column’s name on or off, corresponding to
True
orFalse
. When left at its default ofNone
, the column identifier will be quoted according to whether the name is case sensitive (identifiers with at least one upper case character are treated as case sensitive), or if it’s a reserved word. This flag is only needed to force quoting of a reserved word which is not known by the SQLAlchemy dialect.unique – When
True
, indicates that this column contains a unique constraint, or ifindex
isTrue
as well, indicates that theIndex
should be created with the unique flag. To specify multiple columns in the constraint/index or to specify an explicit name, use theUniqueConstraint
orIndex
constructs explicitly.system –
When
True
, indicates this is a “system” column, that is a column which is automatically made available by the database, and should not be included in the columns list for aCREATE TABLE
statement.For more elaborate scenarios where columns should be conditionally rendered differently on different backends, consider custom compilation rules for
CreateColumn
.comment –
Optional string that will render an SQL comment on table creation.
New in version 1.2: Added the :paramref:`_schema.Column.comment` parameter to
_schema.Column
.