On Mon, Sep 27, 2010 at 08:37:08PM -0400, Alex Gaynor wrote:
>
> While developing my backend I basically ignored the existing tests
> because it was impossible to learn anything from 700 test failures,
> of which some are "expected and never will pass" (e.g. ones testing
> that we generate only one
On Tue, Sep 28, 2010 at 07:22:11AM +0800, Russell Keith-Magee wrote:
> On Tue, Sep 28, 2010 at 1:51 AM, Mark Bucciarelli wrote:
> >
> > I guess the test suite must not cover all the basees, making it a
> > necessary but not sufficient criteria for inclusion?
> >
>
On Sat, Sep 25, 2010 at 10:21:06PM +0800, Russell Keith-Magee wrote:
>
> The number 4 wasn't actually the important bit - it was that I want
> to see a range of noSQL approaches represented. I don't want to see
> 4 key-value stores; I want to see a key-value store, and a document
> store, and a col
On Mon, Aug 16, 2010 at 10:31:11AM +0800, Russell Keith-Magee wrote:
> On Mon, Aug 16, 2010 at 10:03 AM, Mark Bucciarelli wrote:
>
> > ?- random api lock (people tend towards complacency)
>
> I'm not entirely certain I understand this point -- or, at least,
> how it wo
On Sat, Aug 14, 2010 at 03:03:27PM +0800, Russell Keith-Magee wrote:
>
> If you have suggestions on how we can improve Django's development
> process and address these issues, we're happy to hear them.
>
You may find this interesting:
http://openbsd.org/papers/asiabsdcon2009-release_eng
On Fri, Jul 30, 2010 at 4:13 PM, Hooshyar Naraghi wrote:
>
> anyone who wishes to take _this_ Django and fork
> it into a _new_ Dmango, can do it any time?
>
The devs here _extremely_ patient with whiners [1].
m
[1] People with lots of ideas about how you should
spend your free time, and spend
On Thu, Jul 15, 2010 at 5:57 PM, Ian Kelly wrote:
>
> Er, I'm pretty sure that MySQL does support both ORDER BY and
> LIMIT/OFFSET. At least, it is documented as supporting them.
>
Right you are.
There are few restrictions on the type of statements in which
subqueries can be used. A subquery ca
On Thu, Jul 15, 2010 at 2:18 PM, Alex Gaynor wrote:
>
> And yes, if what you say about the SQL spec is true, then Django will
> emit semantically invalid SQL. It's also emitting SQL that can be
> perfectly understood by a lot of databases. Despite SQL being a spec
> most DBs implement it slightl
On Thu, Jul 15, 2010 at 2:04 PM, Alex Gaynor wrote:
>
> It may be that they aren't allowed by the spec, but the only database
> (that Django includes an adapter for) that doesn't support them
> (AFAIK) is MySQL.
>
Cool, so that adapter has a workaround?
>
> Further, Event.objects.all()[:1] doesn
Hi,
I've just been informed by a MonetDB developer
that LIMIT and ORDER BY clauses are not
allowed by the SQL spec in sub-selects.
I filied a bug with them because the Django
code:
Event.objects.all()[:1]
was failing because of invalid SQL.
I don't have access to the SQL spec so I
can't quo
On Wed, Jun 30, 2010 at 7:14 PM, Russell Keith-Magee
wrote:
>
> It appears that MonetDB is behaving the same way as PostgreSQL. The
> right approach in the test is to catch the exception and roll back the
> cursor.
>
In 1.2 I see full_clean() and ValidationError let's
me handle this in applicatio
On Wed, Jun 30, 2010 at 2:19 PM, Mark Bucciarelli wrote:
>
> So what is the correct Django backend behavior?
>
I'm going with backend-dependent for
pre-1.2 Django.
In 1.2 full_clean() + ValidationError is
to the rescue.
Thanks,
m
--
You received this message because you are
On Wed, Jun 30, 2010 at 7:56 AM, Mark Bucciarelli wrote:
> On Wed, Jun 30, 2010 at 7:14 AM, Mark Bucciarelli wrote:
>>
>> Is this test look correct?
>>
>
> It passes when using SQLite ...
>
It fails with a postgresql_pschopg2 backend.
So what is the correct Django
On Wed, Jun 30, 2010 at 7:14 AM, Mark Bucciarelli wrote:
>
> Is this test look correct?
>
It passes when using SQLite backend, so I
think the test is good.
>
> Currently it fails on the get() with the error
>
> current transaction is aborted
> (please ROLLBACK
Hi,
I've been working on a Django backend for MonetDB.
I'm trying to write a unit test that verifieds I curently
have a bug in how transactions are handled.
I have a couple questions about the unit test.
Here, Simple is a model with a single field "name"
that has a unique index.
15 matches
Mail list logo
