Account for new psycopg2 exception classes mapping From psycopg2 >= 2.8, specific exceptions are raised corresponding to postgresql errors. E.g. a CheckViolation exception is raised instead of a generic IntegrityError previously when a constraint violation occurs. The way we intercept database errors, especially for constraint violation, is not compliant with that because we do not catch subclasses of IntegrityError in native source's doexec() method. We fix this by checking for the presence of IntegrityError error in exception class's mro. This is still overcomplicated and clumsy, because we still use string comparison, but this is the best we can do as far as I know. (A better fix would be 'isinstance(ex, IntegrityError)' but we have no engine-independent error classes, so this is not possible. Something like sqlalchemy's DBAPI Errors [1] might help: https://docs.sqlalchemy.org/en/latest/errors.html#dbapi-errors)

     1

Javascript Coding Standards

     2

---------------------------

     3

     4

(Draft, to be continued)

     5

     6

:Naming: camelCase, except for CONSTANTS

     7

     8

Indentation rules

     9

~~~~~~~~~~~~~~~~~

    10

    11

- one space before an opening curly bracket ({)

    12

    13

- line break after a closing curly bracket (}) (possibly no line break if

    14

  everything is on the same line)

    15

    16

- no tabs

    17

    18

    19

Documentation

    20

~~~~~~~~~~~~~

    21

XXX explain comment format for documentation generation

    22

    23

    24

Coding

    25

~~~~~~

    26

- Don't forget 'var' before variable definition, and semi-colon (';') after **each** statement.

    27

- Check the firebug console for deprecation warnings

    28

    29

    30

API usage

    31

~~~~~~~~~

    32

- unless intended, use jQuery('container') rather than jqNode('container')

    33

    34

    35

See also

    36

~~~~~~~~

    37

http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml