Splitting models.py won't install models

I have been trying to split my models.py file into several smaller more manageable files. I have created a folder named models, an in there, created a __init__.py file which contains: from other import * from streams import * from units import * I have then split my models into the three files m

Re: Splitting models.py won't install models

On Oct 28, 1:43 pm, patrickk <[EMAIL PROTECTED]> wrote: > you could try changing the import in __init__.py to someting like > this: > from app_name.models.model_file import Model1, Model2, ... > e.g. > from library.models.material import Material, MaterialImage > > ... might work. > Thanks for you

Re: Splitting models.py won't install models

Ok, perhaps this is a pinax issue? I would not have thought that it would have made a difference but I'll try asking on the pinax list. Thanks for your help --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django us

Re: Splitting models.py won't install models

Right I managed to fix it and feel really stupid at the same time but I thought I would post here in case anyone else has the same issue my mistake was using class meta: and not class Meta: doh! got to love case sensitivity. Thanks to all that offered suggestions Alistair --- Alistair

model inheritance - getting data from child objects

Using the example in the django writing models documentation [1] I wish to get a list of all the places, then calculate a value that depends on what the type of place it is. Say in my restraunt I have a function get_workforce() which returns a list of all the people that work in the restaraunt. T

Re: model inheritance - getting data from child objects

On Nov 6, 2:22 pm, Thomas Guettler <[EMAIL PROTECTED]> wrote: > If all worker classes (cook, waiter, ...) are subclassed from Worker, > something like this should work: Worker.objects.filter(workplace=...) > Unfortunately the function that each child will run is a bit more complicated than just l

Re: model inheritance - getting data from child objects

cts.get(id=self.id) except: return self class SubItem(Item): #----- Thanks Alistair -- Alistair Marshall www.thatscottishengineer.co.uk --~--~-~--~~~---~--~~ You received this message because yo

Combine model form with a formset

I have been hunting around but can't find a solution to this problem: It is probably best described with an example Example: class Author(models.Model): name= models.CharField() location = models.CharField() class Book(models.Model): name= models.CharField()

Re: inlineformset_factory KeyError after updating

t, but updating an old one gives the error mentioned in my first email. What other information is needed? thanks -- Alistair Marshall www.thatscottishengineer.co.uk --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: inlineformset_factory KeyError after updating

2009/1/5 Alistair Marshall : Upgraded to 1.0.2 I'll try and create a cut down version-that may take some time (it is getting to be a large project) Thanks -- Alistair Marshall www.thatscottishengineer.co.uk --~--~-~--~~~---~--~~ You received this me

inlineformset_factory KeyError after updating

I appear to be having the same trouble as explained in a previous thread [1] (and for some reason cant find the button to reply to the last thread ???) The other thread points to a bug that was fixed before django 1.0 (which is what I am running) I am not (intentionally) doing anything funny wit

Re: inlineformset_factory KeyError after updating

feed unit the system works fine. However if you go and edit an existing feed unit, an error gets thrown when saving the form. I think that's covered most things - any suggestions/comments welcome Thanks Alistair [1] http://www.thatscottishengineer.co.uk/code/impress.zip -- Alistai

Re: inlineformset_factory KeyError after updating

d to neaten the form. Silly really. Thanks for that Alistair -- Alistair Marshall www.thatscottishengineer.co.uk --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group,

drawing diagrams in django?

hi folks, I am currently trying to create an app which allows the user to generate flowsheets (of a chemical plant) So far I have created all the basics and allow the user to enter information about the individual unitsw chemicals etc and the user can even run a simulation. what I now want to d

move/change database type

Hi folks, I have been developing a project on my desktop using sqlite, I have just attempted to move it onto a 'proper' server and was hoping to use mysql. The thing is I have some data in the database from some beta users and was hoping to take the data over with the move. I had planned on usi

Re: move/change database type

On Jan 21, 7:54 pm, joshuajonah wrote: > A normal manage.py dump to fixture doesn't work? > I had missed that one, didn't know it was an option. my bad Thanks Alistair --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Group

raise ValidationError has no effect

I have been trying to create a custom field that allows the user to enter a flowrate and clean the data back to kg/s or mol/s. I though I had everything sorted, when I type '10 tones/year', it correctly did the conversion however when I type something that does not validate such as 'twenty' or '5

Re: raise ValidationError has no effect

On Feb 15, 12:06 am, Karen Tracey wrote: > The previous paragraph means that if you are overriding Form.clean(), you > should iterate through self.cleaned_data.items(), possibly considering the > _errors dictionary attribute on the form as well. In this way, you will > already know which fields h

Re: raise ValidationError has no effect

2009/4/8 brian : > > I think I'm having the same issue.  Did you ever find a solution? > Yea, Karen Tracey was right in my case: > On Feb 14, 5:06 pm, Karen Tracey wrote: >> On Sat, Feb 14, 2009 at 11:07 AM, Alistair Marshall < >> this is covered here: >&g