On Jan 30, 2013, at 7:31 PM, Gerald Thibault wrote:
> I have a user object, and an extended user object which inherits from the
> base user object. I also have a test object, which has a FK to the extended
> user object. When I try this:
>
> res = session.query(Test) \
> .options(joinedloa
I have a user object, and an extended user object which inherits from the
base user object. I also have a test object, which has a FK to the extended
user object. When I try this:
res = session.query(Test) \
.options(joinedload('user')) \
.all()
I see this sql generated:
SELECT test.id
I'm using Sqlalchemy for the first time and am slowly
figuring out most of what I need. However there is one
aspect I would like some advice about.
I have a GUI program that gets some number of items (say
data about movies for example) from a database and lets
the user edit them including forei
Standardization is always necessary, just a question, which tool would you
suggest for converting things to PDF?
Sent from my iBath
On Jan 30, 2013, at 20:16, "Michael Bayer" wrote:
Keep in mind were ideally working with readthedocs standard tools. It really
should be possible for this to al
On Jan 30, 2013, at 17:53 , Michael Bayer wrote:
> I've asked people before about this seemingly ridiculous "generate twice"
> requirement of LaTeX and I get these incredulous answers like "why? what's
> wrong with running it twice?", as though I'm being unreasonable.
It is an artefact if how
Keep in mind were ideally working with readthedocs standard tools. It really
should be possible for this to all work using standard approaches.
Sent from my iPhone
On Jan 30, 2013, at 12:50 PM, Werner wrote:
> On 30/01/2013 17:53, Michael Bayer wrote:
>> On Jan 30, 2013, at 10:10 AM, Vraj Moh
On 30/01/2013 17:53, Michael Bayer wrote:
On Jan 30, 2013, at 10:10 AM, Vraj Mohan wrote:
Is there any interest in having this fixed?
I'd love someone to take it on and fix it, sure.I've been asking around for
help for years, as I still see people publishing entire books with LaTeX.
Wha
I really hate laTex, I never liked it, how about adobe? I can help if it is
needed.
__
Piensa en el medio ambiente - mantenlo en la pantalla. NO lo imprimas si NO es
necesario.
Think green - keep it on the s
On Jan 30, 2013, at 10:10 AM, Vraj Mohan wrote:
> Is there any interest in having this fixed?
I'd love someone to take it on and fix it, sure.I've been asking around for
help for years, as I still see people publishing entire books with LaTeX.
To proceed here, just learn how to do the Sph
Alright, many thanks.
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@goog
Is there any interest in having this fixed? I am new to SQLAlchemy and
am keen to learn both SQLAlchemy and Sphinx, and have some time to
spare. If there's not much interest in the PDFs, I am open to help in
other areas.
--Vraj
On Wed, Jan 30, 2013 at 9:41 AM, Michael Bayer wrote:
> the PDFS hav
On Jan 30, 2013, at 5:43 AM, George Sakkis wrote:
> Hello,
>
> I am in the process of migrating to PyPy and have a handful of unit test
> failing due to the different garbage collector and SQLAlchemy's usage of weak
> references in the Session identity map. Most failures are probably safe to
On Jan 30, 2013, at 5:00 AM, Matteo wrote:
> Hello everybody,
>
> I'm currently using PostgreSQL 8.4.9 and SQLAlchemy 0.7.9, and there's an
> issue I just can't seem to solve.
> There are 2 tables, User and People. The idea behind this is to have User's
> "people_id" column point to that user'
On Jan 30, 2013, at 8:47 AM, Hans Meine wrote:
>
> I am still not sure if this confusion isn't a bug or weakness in SA that
> should be either fixed or handled with a more explicit error message.
the usage pattern as is will likely never be feasible; "SELECT * FROM A, B
JOIN C on ", and then
the PDFS have generated very poorly for quite some time and readthedocs
environment is not able to adapt to the many warnings it generates for
SQLAlchemy's documentation. I've was n the Sphinx list a few years ago at
this point asking for solutions regarding some of these warnings and was not
Hi Michael!
Am Dienstag, 29. Januar 2013, 12:23:01 schrieb Michael Bayer:
> … it's usually going to complicate
> things if you mix implicit and explicit joins together. The issue should
> be solved if you create a clean string of joins:
>
> s.query(results1.id, results2.id).select_from(results1
Hello,
I am in the process of migrating to PyPy and have a handful of unit test
failing due to the different garbage collector and SQLAlchemy's usage of
weak references in the Session identity map. Most failures are probably
safe to ignore and all of them are fixed after manually calling
gc.co
Hello everybody,
I'm currently using PostgreSQL 8.4.9 and SQLAlchemy 0.7.9, and there's an
issue I just can't seem to solve.
There are 2 tables, User and People. The idea behind this is to have User's
"people_id" column point to that user's personal data, and People's
"user_id" point to the use
Oh, sorry, i supposed thaty contains_eager only worked for relationships,
and not for other kind of attributes :D
That's great!
Thanks!
2013/1/28 Michael Bayer
> what additional behaviors are you looking for that the @property approach
> isn't giving you ? Options include turning it into a
19 matches
Mail list logo
