Re: django models

Hi Mr. Akumbo, The options for Model Fields that come with django in the django.db library and are listed and explained here: https://docs.djangoproject.com/en/dev/ref/models/fields/#model-field-types Each corresponds to a different type of data. For example name =

Re: django models

On Sunday, June 1, 2014 7:42:13 PM UTC+1, Thomas wrote: > > > On 2014-05-31, at 4:41 AM, ngangsia akumbo > wrote: > > please i need some legit answer please > > > Please give one or two specific examples of functionality you need. There > are parameters for fields which

Re: The Django 1.7 tees!

Hi Lloyd, The card won't be debited until the campaign completes, which was over the weekend; I'm guessing that means the bank wouldn't have processed anything until Monday, and as with all bank things, it might take a day or two to show up in statements. The actual shirts should have gone into

Re: Django Macros Url. Routing must be simple!

On Mon, Jun 2, 2014 at 7:49 PM, Alexandr Shurigin wrote: > Hi all! > > Yestarday i released beta version of new django routing helper component. > > Routing must be simple. Now we talking with django core team about making > django routing simpler by default. > > If

InterfaceError: connection already closed

It seems that after updating to 1.6, we are running into an InterfaceError on different views at random times. I found the some older tickets below where the issues is apparently resolved, but it's not in my case. Could this be related to the ATOMIC setting for postgres? What could I be doing

Django Macros Url. Routing must be simple!

Hi all! Yestarday i released beta version of new django routing helper component. Routing must be simple. Now we talking with django core team about making django routing simpler by default. If anybody is interested about it, you can use right now my component to make your routes simple,

Re: Registration extend nightmare

I did my own extend and in the end I just created a one-to-one table for a user profile. When I extended Django-reg, I ended up overriding the user registration views for transactional processing of the additional table. On Monday, June 2, 2014 6:40:13 AM UTC-6, Matt Guy wrote: > > Thanks for

Re: Registration extend nightmare

Thanks for your answer. The prospect of dumping all of this and putting together a patchwork of my own code alongside registration is somewhat daunting at this stage. It also seems as though so many people use and recommend registration, including those successfully tackling this problem, that

Re: The Django 1.7 tees!

Hey Russell, I placed an order for a small tee, but I see my card has not been debited in my bank statement? When do they get charged/ shipped? Thanks, Lloyd On Wed, May 21, 2014 at 2:17 PM, Sithembewena Lloyd Dube wrote: > Hi Russell, > > Thank you! I really appreciate

Re: InlineFormSet validation

Hi, Russell, thanks for answering :-) Your answer helps me, but not completely. I can add the error with this: self._errors.append({'formula': self.error_class([msg])}) # self._errors in a BaseInlineFormSet is a list of dictionaries, not a dictionary, like you say. But I don't know how