Yes you can do a union. Use the "|" (pipe) operator.
union = queryset1 | queryset2
or you can replace queryset1 with the union as follows:
queryset1 |= queryset2
Nick
On 16/02/10 02:39, rebus_ wrote:
On 16 February 2010 03:28, ydjango wrote:
I have two query sets with two different wher
eason not to store first and last as
separate fields, and join the names when you present them on screen / in
reports? That would save having to make assumptions about the number of
first and surnames people enter (someone could enter 'Barton Hartley' as
a double-barreled surname for
Thank you, that has worked.
On 10/02/10 15:11, Karen Tracey wrote:
On Wed, Feb 10, 2010 at 10:01 AM, Nick Booker mailto:n...@clocksoft.com>> wrote:
Sorry I correct myself -- I meant it always has a from address of
r...@localhost, which the customer's relay rejects.
SERV
I'll try that. I did look at the docs, but obviously not hard enough.
Thanks for your help.
Nick
On Feb 10, 3:11 pm, Karen Tracey wrote:
> On Wed, Feb 10, 2010 at 10:01 AM, Nick Booker wrote:
> > Sorry I correct myself -- I meant it always has a from address of
> > r...@
Sorry I correct myself -- I meant it always has a from address of
r...@localhost, which the customer's relay rejects.
On 10/02/10 14:54, Nick Booker wrote:
Hi all.
Django keeps sending out emails with the subject:
[Django] Error (EXTERNAL IP): /path_to_some_file.css
The problem I ha
st.
This is despite the DEFAULT_FROM_EMAIL being set correctly to a
globally-valid address and working elsewhere.
How do I get Django to use a from address of my choice when sending
these error emails?
Nick Booker
Clockwork Software Systems
these are still getting dropped
you need to set
6 matches
Mail list logo
