On Sat, Dec 19, 2009 at 9:17 AM, Leaf wrote:
> Okay, I can live with that. The "alternate template loader" system in
> #6262 looks pretty nice. Unfortunately, I have already put a lot of
> effort into writing a Jinja2 layer for Django (named, cleverly enough,
> Djinja2) using the current, 1.1 temp
Okay, I can live with that. The "alternate template loader" system in
#6262 looks pretty nice. Unfortunately, I have already put a lot of
effort into writing a Jinja2 layer for Django (named, cleverly enough,
Djinja2) using the current, 1.1 template semantics that operates
without involving Django'
On Fri, Dec 18, 2009 at 5:44 PM, Ian Kelly wrote:
> We just changed our test database to Oracle 11gR2 and discovered that
> the unicode test case in the basic test is now failing. This may just
> be something wrong with our installation, because we're seeing the
> same problem performing the sam
We just changed our test database to Oracle 11gR2 and discovered that
the unicode test case in the basic test is now failing. This may just
be something wrong with our installation, because we're seeing the
same problem performing the same test through sqlplus, whereas it
works agains Oracle 10g X
Patch and ticket done. Any comments?
http://code.djangoproject.com/ticket/12403
Thanks,
Ben
On 17 Dec 2009, at 10:06, Ben Firshman wrote:
> I've made a few more changes, added many more tests and written
> documentation. This now fixes #6188, #6304, #6618, #6969, #8758,
> #8989, #10334, #1
On Dec 18, 9:50 am, Alex Gaynor wrote:
> I'm wondering if perhaps the most prudent thing to do would be to
> simply remove this check. The end result will be you'll get an
> integrity error on Postgres/Oracle when you try to save (and SQLite
> and MySQL will just let you do whatever).
That would
On Fri, Dec 18, 2009 at 12:41 PM, Brett Hoerner wrote:
> I'm not sure if 1.2 intended to fully support read-slaves, but I'll
> post this quick anyway as we've just run into it while trying to
> upgrade at DISQUS.
>
> You might think that having support for multiple databases implies
> that using a
I'm not sure if 1.2 intended to fully support read-slaves, but I'll
post this quick anyway as we've just run into it while trying to
upgrade at DISQUS.
You might think that having support for multiple databases implies
that using a read-slave would Just Work, and that's mostly true.
There's one ed
On Fri, Dec 18, 2009 at 9:00 AM, Peter Herndon wrote:
> Hi all,
>
> I've run into a situation where syncdb produces an error on one of my models
> against Oracle, but not against Postgres. Using Postgres, one can mark a
> TextField as unique=True, and syncdb works just fine. Using Oracle, you
Hi all,
I've run into a situation where syncdb produces an error on one of my models
against Oracle, but not against Postgres. Using Postgres, one can mark a
TextField as unique=True, and syncdb works just fine. Using Oracle, you get an
error:
> cx_Oracle.DatabaseError: ORA-02329: column of
On Friday 18 December 2009 01:44:05 Jeremy Dunck wrote:
> On Thu, Dec 17, 2009 at 6:47 PM, Luke Plant
> wrote: ...
>
> > The problem with signals is that they don't return values, and so
> > the mechanism can't interact with the actual login process. It
> > can only notice that something is goi
11 matches
Mail list logo
