On Sun, 2007-08-19 at 23:01 -0500, Adrian Holovaty wrote:
[...]
> I haven't yet made DatabaseError, IntegrityError and the introspection
> and creation functionality accessible via the django.db.connection
> object. Those changes can happen in the near future, if they need to
> be made.
If we do
On 8/13/07, Brian Harring <[EMAIL PROTECTED]> wrote:
> As hinted at earlier on the ml, have started doing some work on
> refactoring the actual db backend; ticket 5106 holds the current
> version (http://code.djangoproject.com/ticket/5106).
I've implemented pretty much all of this in a flurry of
Resumes and CV's examples written by people in the industry. They are
the ones who know best what to write in a resume for that industry.
High Tech people writing technical resumes and CV examples, and
Teachers writing and advising teaching resumes examples and CV
examples. Do you really want a
Russell Keith-Magee wrote:
> On 8/13/07, George Vilches <[EMAIL PROTECTED]> wrote:
>> Russell Keith-Magee wrote:
>>> The configuration option will need to be a little more generic - i.e.,
>>> putting the entire backend into a record mode - not just a single
>>> cursor call.
>> Second, we could
> To be fair (to us), this
> threadhttp://groups.google.com/group/django-developers/browse_frm/thread/4f...was
> all about exactly that. It mentioned management.py in the title, so that
> counts as a clear warning in Open Source mailing list terms (sometimes
> threads veer wildly off course
2007/8/19, Andreas Stuhlmüller <[EMAIL PROTECTED]>:
>
> On 8/17/07, David Larlet <[EMAIL PROTECTED]> wrote:
> > Just one (latest?) thought, it's a bit hard to debug because
> > 400 errors are not really verbose, is it possible to find a
> > way to make debug easier? For the moment, I have: if
> >
On Aug 17, 12:00 pm, Gary Wilson <[EMAIL PROTECTED]> wrote:
> Yes, I do not like the idea of adding a new order_by parameter
> either. However, there is a bit of an issue involving the
> archive_index view though because it also uses a num_latest parameter,
> IMHO implying that the items will be
On Sun, 2007-08-19 at 15:25 +, Thejaswi Puthraya wrote:
> Hello Django Developers,
>
> On August 20th ie tomorrow, Google Summer of Code 2007 will officially
> close and all students are required to commit the code written over
> the past two odd months. As I was preparing to commit my code
Hello Django Developers,
On August 20th ie tomorrow, Google Summer of Code 2007 will officially
close and all students are required to commit the code written over
the past two odd months. As I was preparing to commit my code I was
stumped to see that my project's code broke post revision 5923.
On 8/17/07, David Larlet <[EMAIL PROTECTED]> wrote:
> Just one (latest?) thought, it's a bit hard to debug because
> 400 errors are not really verbose, is it possible to find a
> way to make debug easier? For the moment, I have: if
> settings.DEBUG: print i.errors but I'm sure it can be better.
On Sun, 2007-08-19 at 05:19 -0700, ludvig.ericson wrote:
> Well actually, I see implementation leakage in the API here.
>
> Does it make sense that the Django ORM raises SQLite3 exceptions? I
> wouldn't want _to try to try to_ catch either of all integrity
> exceptions.
>
> Perhaps something
Well actually, I see implementation leakage in the API here.
Does it make sense that the Django ORM raises SQLite3 exceptions? I
wouldn't want _to try to try to_ catch either of all integrity
exceptions.
Perhaps something like 'django.db.IntegrityError' or so.
Ludvig Ericson
12 matches
Mail list logo
