431eaf6edb
The "MAX" constants in the db api are useful to import without needing to import the rest of the api, so they are moved to a constants.py file in the same package. api.py then imports the symbols from that file for backwards compatibility. The handler and schema for placement inventories (which use the MAX constants) are updated to point to the constants file directly as they do not need the db api. Change-Id: Ifab10e023bcf4389f6514b477755c4cced2d1598
26 lines
1.2 KiB
Python
26 lines
1.2 KiB
Python
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
# not use this file except in compliance with the License. You may obtain
|
|
# a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
"""Useful db-related constants. In their own file so they can be imported
|
|
cleanly."""
|
|
|
|
# The maximum value a signed INT type may have
|
|
MAX_INT = 0x7FFFFFFF
|
|
|
|
# NOTE(dosaboy): This is supposed to represent the maximum value that we can
|
|
# place into a SQL single precision float so that we can check whether values
|
|
# are oversize. Postgres and MySQL both define this as their max whereas Sqlite
|
|
# uses dynamic typing so this would not apply. Different dbs react in different
|
|
# ways to oversize values e.g. postgres will raise an exception while mysql
|
|
# will round off the value. Nevertheless we may still want to know prior to
|
|
# insert whether the value is oversize or not.
|
|
SQL_SP_FLOAT_MAX = 3.40282e+38
|