Re: Model.add() ?

Thanks for the reply Jacob, But I intentionally posted it here. Reason: I am *not* asking about how to use Django, the document is (mostly) excellent! But I accept any comments on my usage. :-) I actually want to point the Django developers to the implementation of Model.save() and am trying to

OFFTOPIC: Italian translation ready [was: Re: Constraints and MySQL]

Jacob Kaplan-Moss wrote: > Right now #2333 is all that 0.96 is waiting on Please don't forget #1984. Thank you. -- Nicola Larosa - http://www.tekNico.net/ When talking about Security, most people think about something where "they" attack and "we" defend. If they succeed only once, we have los

Re: Constraints and MySQL

On 2/28/07, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: > > Django is, as I have > been told, database independent. And Django is working fine with > MySQL, lets keep it that way. Well, no, MySQL isn't working fine. Like I said, [4610] didn't break MySQL - it just revealed a problem that has alw

^!^ Cake Recipes ^!^ Deewali Cakes

*Deewali Cake Recipes* Make Deewali Cakes [image: Deewali Cakes] Lemon Cakes Pine Cake Recipes Choco Cake Recipes and More Sweet Cakes Recipes

Re: Constraints and MySQL

On Feb 27, 6:38 pm, "Ramiro Morales" <[EMAIL PROTECTED]> wrote: > On 2/27/07, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: > > > > > Because the other Databases have 'limitations' or 'features' or > > 'defects' that MySQL might not have or whatever. Django is, as I have > > been told, database ind

Re: Upcoming Django release, and the future

> If there's a bug that's been annoying the heck out of you and you want > it fixed before the release, this would be the time to speak up about There one tiny bugfix in [3501] regarding the _sqlite_extract function that i'd like to see committed. It breaks the admin date_hierarchy filter for mod

Microsoft Download Center - Download all MS softwares (freeware)

*Microsoft Softwares Heaven* *Download all Microsoft Softwares - Freeware* ** *[image: Microsoft Softwares Heaven] * http://www.awpedia.com/downloads/microsoft-softwares/ ** *Download Windows All* ** *Windows Vista* *Windows XP* *MS Office 2007

Re: Constraints and MySQL

On 2/27/07, Geert Vanderkelen <[EMAIL PROTECTED]> wrote: > > Because the other Databases have 'limitations' or 'features' or > 'defects' that MySQL might not have or whatever. Django is, as I have > been told, database independent. And Django is working fine with > MySQL, lets keep it that way. A

css includes in class Admin like js = ()

Hi Guys, In semi-response to wonderfull things like Upcoming changes to the Django admin :) How about having something similar as the js tuple for css styles ? A usecase could be the admin fields for a model, there u can declare something like: fields = ( (None, { 'fi

Re: Constraints and MySQL

On 2/27/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: [on reverting [4610]]: > I'm -1 on this. Serialization and fixtures are near useless if you > can't do forward references. [4610] introduces a test for forward > references, and fixes a problem with Postgres. [4610] doesn't > introduce an

Re: Constraints and MySQL

Hi, On 2/28/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: [...] > Either way, the problem/limitations > with MySQL needs to be mentioned in the documentation (both > serialization and fixtures). Yes, in really big red letters, we could add a directive for the documentation rst for "thinks y

Re: Model.add() ?

On 2/28/07, Arvind Singh <[EMAIL PROTECTED]> wrote: > > Hi all, > > I wanted to use UUID as primary key in my models. Since Model doesn't > have any add() method, I have to do it like this: For the future - this question should be asked on the users list. The developers list is for discussion of

Re: Constraints and MySQL

On 2/28/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > On 2/27/07, Seattle Daniel <[EMAIL PROTECTED]> wrote: > > As I read it, there is not a way to force InnoDB to check constraints > > at commit. And once there is it will be quite some time before the > > mass of MySQL instances support it

Re: Model.add() ?

Hey Arvind -- This question is really more appropriate for django-users (http://groups.google.com/group/django-users/); django-dev is for discussion of developing Django, not for discussion of using Django. You'll have a lot more luck if you redirect your question to django-users. Thanks! Jacob

Re: Django not thread-safe?

Hi, just for your information, I've reopened the ticket, asking Jacob for details about Django being not thread-safe. http://code.djangoproject.com/ticket/3357#comment:8 Michael --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

Re: Django not thread-safe?

This patch being: * good for local testing that more closely resembles a real hosting environment (eg: with AJAX testing) * for the development server only * and disabled by default you'd think it would be an easy inclusion. I'd like to know more too. -Rob --~--~-~--~~---

Re: multiple-db-support branch

On 2/27/07, Alexander Solovyov <[EMAIL PROTECTED]> wrote: > So I have question - what needs to happen for merging this branch into > trunk? I read page on wiki (MultipleDatabaseSupport) and examined that > all features are completed but the docs absent in all. So writing docs > will cause to mergi

Re: Constraints and MySQL

On 27 Feb 2007, at 19:59, Sandro Dentella wrote: .. >> >> 1. Revert [4610] so that all databases work the same way, and not >> allow forward references in serializers (or elsewhere). >> >> 2. Leave [4610] in, and not allow forward references in MySQL. >> >> I'd suggest #1 for orthogonality, but d

Model.add() ?

Hi all, I wanted to use UUID as primary key in my models. Since Model doesn't have any add() method, I have to do it like this: # override Django's save() def save(self): import uuid while not self.id: # we are adding new ro

Re: Upcoming Django release, and the future

On Feb 27, 10:41 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > I tried it, and it worked for me. Can you provide an example where it fails? I updated the trunk and it works perfectly. It was obviously my fault. Thank you very much. Massimiliano --~--~-~--~~~---

Re: Upcoming Django release, and the future

On Mon, Feb 26, 2007 at 06:16:31PM -, [EMAIL PROTECTED] wrote: > > I would like to see http://code.djangoproject.com/ticket/3297 > implemented before 0.96 if possible. I definitely agree. And more It's a working one! I think that newforms are the true change in this releise. We need to try

Re: Constraints and MySQL

On Tue, Feb 27, 2007 at 11:26:11AM -0600, Jacob Kaplan-Moss wrote: > > On 2/27/07, Seattle Daniel <[EMAIL PROTECTED]> wrote: > > As I read it, there is not a way to force InnoDB to check constraints > > at commit. And once there is it will be quite some time before the > > mass of MySQL instances

Re: Constraints and MySQL

On 2/27/07, Seattle Daniel <[EMAIL PROTECTED]> wrote: > As I read it, there is not a way to force InnoDB to check constraints > at commit. And once there is it will be quite some time before the > mass of MySQL instances support it. So... I think that leaves is with two kinda sucky choices: 1. R

Play Free Games! Win Cool Prizes!

Play Free Games! Win Cool Prizes! - http://surl.in/HLARI238206SVRAKSX-google --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegr

Re: Creating an independent auth/permission-framework, separate the models (Was: Adding support for replacing the auth User model to fit custom needs)

On 2/27/07, David Danier <[EMAIL PROTECTED]> wrote: > > As an enhancement it would be nice to get the generic-auth-branch into > the trunk (slightly changed perhaps). So not only authorization can be > done on an abstract way, but permission-checks, too. I'll probably work on this once the newfor

Play Free Games! Win Cool Prizes!

Play Free Games! Win Cool Prizes! - http://surl.in/HLARI238206SVRAKSX-google --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegr

Re: Constraints and MySQL

>From the MySQL docs: Deviation from SQL standards: Like MySQL in general, in an SQL statement that inserts, deletes, or updates many rows, InnoDB checks UNIQUE and FOREIGN KEY constraints row-by-row. According to the SQL standard, the default behavior should be deferred checking. That is, constr

Re: Constraints and MySQL

Hi Russell, On 27 Feb 2007, at 16:16, Russell Keith-Magee wrote: .. > Postgres has similar behaviour to InnoDB by default, but [4610] > modified the table declarations to disable constraint checking until > the end of a transaction using DEFFERABLE INITIALLY DEFERRED. However, > apparently MySQL

multiple-db-support branch

Hi all. Few minutes ago I drop mail to Jason Pellerin and he tolds me that he can't maintain branch due to lack of time. So I have question - what needs to happen for merging this branch into trunk? I read page on wiki (MultipleDatabaseSupport) and examined that all features are completed but t

Re: geodjango

On 2/26/07, Travis Pinney <[EMAIL PROTECTED]> wrote: > Hi Jeremy, > > I have geometric queries working now. > > Right now I have it set up as > > bbox = "POLYGON((-95.36819458007812 > 30.2184318620219,-95.36819458007812 > 30.084840018486364,-95.55702209472656 > 30.084840018486364,-95.5570220947265

Constraints and MySQL

Hi all, Adrian has finally had a chance to look at, and approve the acceptance of, the test fixtures patch. I sat down tonight to check in the patch, did a last little check, and hit a snag - the trunk model tests break under MySQL. Personally, I'm a Postgres jockey, so I need some guidance from

Re: Creating an independent auth/permission-framework, separate the models (Was: Adding support for replacing the auth User model to fit custom needs)

> I'm much more of the opinion nowadays that Django doesn't necessarily > need an overreaching and generic authentication/authorization > framework. Yes and no. On the one hand it is not needed, besides for the admin (which gets separated somehow, as you said later in your email). On the other ha

Re: Upcoming Django release, and the future

On 27 Feb, 10:41, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > I tried it, and it worked for me. > Can you provide an example where it fails? I'll give it a deeper look tomorrow. I'll let you know. Thank you very much Massimiliano --~--~-~--~~~---~--~~ Y

Re: get_FOO_basename() for FileFields

herbert wrote: > as i said ... i want to use it in my templates I may recommend to create a general-purpose template filter: @register.filter def basename(filename): return os.path.basename(filename) and then use it as: {{ object.file|basename }} To me it feels very Djan

Re: Upcoming Django release, and the future

On 2/27/07, Massimiliano Ravelli <[EMAIL PROTECTED]> wrote: > > On 26 Feb, 13:31, Michael Radziej <[EMAIL PROTECTED]> wrote: > > > #3253 has a working patch with documentation. I've closed yours as > > duplicate of #3253. > > Hi Micheal, Hi Russ > > >From ticket #3253: > "I didn't check whether it

Re: Upcoming Django release, and the future

On 26 Feb, 13:31, Michael Radziej <[EMAIL PROTECTED]> wrote: > #3253 has a working patch with documentation. I've closed yours as > duplicate of #3253. Hi Micheal, Hi Russ >From ticket #3253: "I didn't check whether it actually works for manage.py test"; I made a quick test and it seems that i

Re: get_FOO_basename() for FileFields

as i said ... i want to use it in my templates .. where {{ os.path.basename(object.file) }} would surely not work .. so .. the difference is not just spelling .. it would simply not work .. and creating a function for every FileField in every model which uses it .. seems somehow even more odd to m