On 12/18/06, James Bennett <[EMAIL PROTECTED]> wrote:
> I'll second Jeremy's request for any info you can give us for
> developing tests which will help pinpoint these so we can fix them.
Re-reading my email, I sounded defensive about the existing API. I
am, generally, happy with the Django ORM,
On 12/18/06, Jeffrey Zelt <[EMAIL PROTECTED]> wrote:
> 3. My only serious request involves the DB API. The Django ORM is
> simply too limiting. I was not able to do what I wanted without jumping
> through hoops. I was forced to use the:
Yeah, it's a wart :(
There are definitely some historic
On 12/18/06, Jeffrey Zelt <[EMAIL PROTECTED]> wrote:
> 3. My only serious request involves the DB API. The Django ORM is
> simply too limiting. I was not able to do what I wanted without jumping
> through hoops. I was forced to use the:
>
> extra( where=..., params=..., tables=...)
Hey Je
On 12/18/06, Jeffrey Zelt <[EMAIL PROTECTED]> wrote:
...
> 3. My only serious request involves the DB API. The Django ORM is
> simply too limiting. I was not able to do what I wanted without jumping
> through hoops. I was forced to use the:
>
> extra( where=..., params=..., tables=...)
>
>
Jeffrey Zelt wrote:
> The Django ORM is probably the only piece of Django I am embarrassed
> showing other developers.
Oh really?
> I will not be satisfied if the current ORM is capable of fulfilling 95%
> requirements
You must be inexperienced if you think that an elegant solution to 95%
of
I just wanted to mention that I am wrapping up a new Django site after 7
months of development. It will be used to manage subscriptions for a
magazine published by a Norwegian university. So far it does not have a
public interface so I won't give out the link here (all you would see is
a log
6 matches
Mail list logo
