You get all of the columns from __table__.columns: myTable.__table__.columns or myTable.__table__.c The columns would be in format myTable.col1 (table name is included). If you want just column names, get the .key for each column: [column.key for column in myTable.__table__.columns]
Pyramid has a much more flexible authentication system. And yes, if you want something simple like Django’s user/group/permission concept, then flexible might be scary. Pyramid does not have a “User” object, as it makes no assumptions about how you store your data or what ORM you use, therefore there isn’t something for you like contrib.auth. … Read more
not happy with myself since it’s such a dumb mistake but here is my culprit: report_type = relationship(‘tReportType’, uselist=False, backref=backref(‘report’)) should be: report_type = relationship(‘TReportType’, uselist=False, backref=backref(‘report’)) capital T instead of t, I should be referencing the class, not my actual table name: ‘tReportType’ -> ‘TReportType’
Because Gunicorn is starting with 8 workers (in your example), this forks the app 8 times into 8 processes. These 8 processes are forked from the Master process, which monitors each of their status & has the ability to add/remove workers. Each process gets a copy of your APScheduler object, which initially is an exact … Read more
Pylons isn’t being “cancelled”, and it will continue to receive updates. That said, the “future” per se is in Pyramid. On the mailing list is has been referred to as Pylons 2.0. It is fully tested and better documented than Pylons 1.0, so you might as well jump aboard if you’re fresh. Pyramid is essentially … Read more
You have to set a default value otherwise None/NULL is used: is_active = Column(Boolean, unique=False, default=True) You wanted to do this in __init__ but you used is_active = True (a local variable) instead of self.is_active = True.
You seem to have an impression that SQLAlchemy can only work with a database structure created by SQLAlchemy (probably using MetaData.create_all()) – this is not correct. SQLAlchemy can work perfectly with a pre-existing database, you just need to define your models to match database tables. One way to do that is to use reflection, as … Read more
This all turned out to be because of the way I’ve set SQLAlchemy up in Pyramid. Essentially you need to follow this section to the letter and make sure you use the same declarative_base instance as the base class for each model. I was also not binding a database engine to my DBSession which doesn’t … Read more
You can do something similar to Foo Stack’s answer without resorting to private fields by doing: conn.execute(query).keys()
All of the tables are collected in the tables attribute of the SQLAlchemy MetaData object. To get a list of the names of those tables: >>> metadata.tables.keys() [‘posts’, ‘comments’, ‘users’] If you’re using the declarative extension, then you probably aren’t managing the metadata yourself. Fortunately, the metadata is still present on the baseclass, >>> Base … Read more