Not quite sure I get that - do you mean have a constant like

USERTABLE = foo
And then define the object like

Sqlalchemy stuff....
  Table=USERTABLE

?

Paul Brian
07540 456 115
paul@mikadosoftware.com
Guiding you towards Continuous Delivery of software and business value.

On 18 Mar 2013, at 19:55, Philip Schatz <notifications@github.com> wrote:

In rhaptos2/repo/foldermodel.py:

> +from sqlalchemy.orm import relationship
> +from sqlalchemy.dialects.postgresql import ARRAY
> +import uuid
> +from cnxbase import CNXBase
> +from rhaptos2.repo.backend import Base, db_session
> +from err import Rhaptos2Error  # Rhaptos2SecurityError
> +# XXX - replace with catchall err handler - conflict5s with debug
> +from flask import abort
> +
> +################## COLLECTIONS #############################
> +
> +
> +class UserRoleCollection(Base, CNXBase):
> +    """The roles and users assigned for a given folder
> +    """
> +    __tablename__ = 'userrole_collection'

Would it be worth refactoring the names of tables and fields out as
constants on top of the file? That may make it easier to read/reason about
the code.

—
Reply to this email directly or view it on
GitHub<https://github.com/Connexions/rhaptos2.repo/pull/91/files#r3419376>
.

-- 


www.mikadosoftware.com

See your software improve with every change.