Re: Desired: Field behavior like AutoField + unique_with

Because sequence number was running number per "tenant" (in my case it was invoice type) that started from zero (0) at the beginning of the every year. You could use max+1 as well but you should be aware that there is a slim chance that there is race condition and you may end up having two

Re: do migrations (Django 1.7+) handle production data?

On Wed, Jan 14, 2015 at 3:03 PM, Abraham Varricatt < abraham.varric...@googlemail.com> wrote: > Hello everyone, > > One of the biggest features introduced in Django 1.7 are migrations. They > can broadly be classified into 2 types - > * schema migrations > * data migrations > > Schema migrations

do migrations (Django 1.7+) handle production data?

Hello everyone, One of the biggest features introduced in Django 1.7 are migrations. They can broadly be classified into 2 types - * schema migrations * data migrations Schema migrations deal with changes to the database schema. eg - changing max_digits of a DecimalField. Data migrations

Re: python with django orm code , after exits, the entry from db revert backs

no sir , im really sorry actually there was some bug from my side. but thank you sir for response, at i know some concept about autocommit. On Mon, Jan 12, 2015 at 2:12 PM, Sergiy Khohlov wrote: > Have you enabled autocommit to yes? > > -- > You received this message

need help to configure new domain

hello i need urgent help to configure django, i had site on django cms then i loose my old domaind now i need to add new domain name but i see - http://joxi.ru/82QDVneI8o3amd so i realy need help to configure my website with fee -- You received this message because you are subscribed to the

hello need help to configure django

I had worked site @ webfaction hosting but i loose old domain names and trying to configure new domain name, here what i see on screenshot: http://joxi.ru/Y2LyjZecxPeOA6 realy need urgent help -- You received this message because you are subscribed to the Google Groups "Django users" group.

[ANNOUNCE] Security releases issued (1.4.18, 1.6.10, 1.7.3)

Today the Django team is issuing multiple releases -- Django 1.4.18, Django 1.6.10, and Django 1.7.3 -- as part of our security process. These releases address several security issues, and we encourage all users to upgrade as soon as possible. More details can be found on our blog:

Re: segmentation fault

> Le 13 janv. 2015 à 19:25, Django User a écrit : > > hello > i keep getting the following error messages that state mod_wsgi was already > loaded and segmentation faults. pls. see an example: > > [Tue Jan 13 23:46:11 2015] [error] >

segmentation fault

hello i keep getting the following error messages that state mod_wsgi was already loaded and segmentation faults. pls. see an example: [Tue Jan 13 23:46:11 2015] [error] /usr/local/lib/python2.7/dist-packages/pytz/__init__.py:29: UserWarning: Module mod_wsgi was already imported from None, but

Re: passing variables

On Monday, January 12, 2015 at 5:29:08 PM UTC-8, suabiut wrote: > > How to you pass variable from one template to another template? > You haven't provided any information about your problem, but it sounds like you might want to read the docs on template inheritance:

Re: ImportError: No module named check_constraints

I don't think you are going to get any helpful replies with that kind of statement? On 13 Jan 2015 13:04, "Jenefa Jeyaraj" wrote: > ImportError: No module named check_constraints > > -- > You received this message because you are subscribed to the Google Groups > "Django

Re: Desired: Field behavior like AutoField + unique_with

Thanks Jani, good to hear someone has gone down this road before. Since you did it in code, is there a reason you kept a sequence value on Tenant rather than using Widget.objects.aggregate(Max(Widget.sequence_value)) ? I ask because for my app, Widget is actually just one of several cases where

object has no attribute 'new_objects' error when saving related objects

I am working on a simple application to store sets of collected datapoints into a dataset. I am using the admin interface to handle CRUD management of the dataset objects. I would like to be able to add additional datapoints to an existing dataset instance by importing model data from a file.

Re: Desired: Field behavior like AutoField + unique_with

I've done something similiar. Only way to do that is that you need to upkeep that tenant sequence_id manually, So doing something like: class Tenant(models.Model): name = models.CharField(max_length=50) sequence_value = models.IntegerField() and in a code: tenant =

ImportError: No module named check_constraints

ImportError: No module named check_constraints -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group,

Desired: Field behavior like AutoField + unique_with

I'm building a multi-tenant application with a data model that simplifies to: class Tenant(models.Model): name = models.CharField(max_length=50) class Widget(models.Model): owner = models.ForeignKey(Tenant) sequence_id = I want Widget.sequence_id to work like an AutoField (that