Seems to work great. Thanks so much!
On Wednesday, November 7, 2018 at 11:33:11 AM UTC-8, Mike Bayer wrote:
>
> On Wed, Nov 7, 2018 at 1:05 PM >
> wrote:
> >
> > I need help with structuring the query too. I can implement a query with
> raw SQL, but it involves subqueries, and I'm not sure
I need help with structuring the query too. I can implement a query with
raw SQL, but it involves subqueries, and I'm not sure how to translate it
to a column property (or if there's a better way which would avoid the need
for a subquery entirely)
On Wednesday, November 7, 2018 at 9:54:15 AM
I have the following two models
class Dataset(db.Model):
__tablename__ = 'datasets'
id = db.Column(db.Integer, primary_key=True)
creation_datetime = db.Column(db.DateTime(timezone=False), nullable=
False)
sample_id = db.Column(db.Integer, db.ForeignKey('samples.id'), nullable=
Thanks for the detailed explanation. I'll try out some of those techniques.
On Saturday, October 27, 2018 at 7:54:22 AM UTC-7, Mike Bayer wrote:
>
> On Fri, Oct 26, 2018 at 7:49 PM >
> wrote:
> >
> > I see, thanks for the clarification about noload.
> >
> > Setting aside my specific issue,
I see, thanks for the clarification about noload.
Setting aside my specific issue, if using the session in
before_insert/before_update events is not a good idea, what is generally
the best way to perform validation across multiple models? Is it to just
read the relationships from the model
That didn't fix it.
Why should noload not be used? We use it quite often to have more granular
control over which tables get joined. Otherwise, some queries can become
unnecessarily slow
On Friday, October 26, 2018 at 11:45:29 AM UTC-7, Mike Bayer wrote:
>
> please remove those "noload"
I have the following three models (with other columns omitted):
class ContainerSlot(db.Model):
__tablename__ = 'container_slots'
id = db.Column(db.Integer, primary_key=True)
tube_id = db.Column(db.Integer, db.ForeignKey('tubes.id'), unique=True,
index=True)
container_id =
Hello,
I'm encountering an issue where loading a model in a text fixture causes
the load options to be ignored when I load the same model in a Flask
endpoint
I have these two models
class Plate(db.Model):
container_id = db.Column(db.Integer, db.ForeignKey('containers.id'))
container
To solve this problem, you should open a new db session at the beginning of
the web request, and close the session at the end of the request.
See the pattern here:
http://docs.sqlalchemy.org/en/latest/orm/session.html#using-thread-local-scope-with-web-applications
On Monday, October 31, 2011
to the SQL compiler has the joins defined flat, not
hierarchically (i.e. the INNER JOIN of runways and airports is not an
AST node under the RHS of the toplevel OUTER JOIN).
Using SQLAlchemy 0.6.3 (from Debian stable... yeah, I know Debian is
behind the current version) with MySQL 5.1.49.
-Phil
--
You
Works perfectly. Thanks again Michael.
On 29 Jan, 20:13, Phil Coombs [EMAIL PROTECTED] wrote:
Brilliant. Thanks for that lightning response, workaround and fix.
I'll give the code a spin.
On 28 Jan, 23:19, Michael Bayer [EMAIL PROTECTED] wrote:
hi there -
the bug is fixed in r4103
, at 4:03 PM, Phil Coombs wrote:
Hi
I'm a Python and SA newbie investigating SA for a project using
Postgres. I have a database schema that I want to point SA at then be
able to write my Python code.
I'm working with a version of the basic_association example to keep
things simple
?
Thanks in advance
Phil
Postgress DDL
--
create table orders (
order_id Serial ,
o_customer_nametextnot null,
o_order_date timestamp not null,
primary key (o_customer_name, o_order_date) using index ,unique
(order_id);
create table
13 matches
Mail list logo
