Re: Different Database object behavior on Production and Development servers.

2009-03-10 Thread NoviceSortOf
Alex: I tried another custom widget method earlier today without any effect, then I tried yours as outlined in your blog, there are no errors but there is no change in how the field is displayed. It makes me wonder if there is another step involved (CSS?) with this, or if there is something I mu

Re: Different Database object behavior on Production and Development servers.

2009-03-10 Thread NoviceSortOf
> and when I try changing it to > {% for field in formsets %} > i get an error message saying formset is not iterable I was able to get closer the results I want by simply changing the html template from > {% for field in forms %} to {% for form in formset.forms %} {{ form.selected }}{{ form

Re: Different Database object behavior on Production and Development servers.

2009-03-10 Thread Malcolm Tredinnick
On Tue, 2009-03-10 at 04:07 -0700, NoviceSortOf wrote: > Thanks Malcom, > > I re-read the links you sent along on forms and formsets. > > I'm now working with a form but instead of > ___ > > > [ ] Stevenson Collected Works > > > [ ] Stevens

Re: Different Database object behavior on Production and Development servers.

2009-03-10 Thread NoviceSortOf
Thanks Malcom, I re-read the links you sent along on forms and formsets. I'm now working with a form but instead of ___ > > [ ] Stevenson Collected Works > > [ ] Stevenson Treasure Island > > [ ] Stevenson Wild West Stories > > [Submit] I

Re: Different Database object behavior on Production and Development servers.

2009-03-10 Thread Malcolm Tredinnick
So this is the first time you've explained the real problem you're trying to solve. It certainly helps explain, a little bit, at least, which direction to point you for solutions. On Tue, 2009-03-10 at 02:28 -0700, NoviceSortOf wrote: > > It's clear now that __str__(self) or __unicode__ > return

Re: Different Database object behavior on Production and Development servers.

2009-03-10 Thread NoviceSortOf
It's clear now that __str__(self) or __unicode__ return a usable string to the view. But this does not on the surface appear to be a workable instance of the model itself, that would return fields that I can work with in the template...and/or i haven't figured how to get a handle on it. ie... t

Re: Different Database object behavior on Production and Development servers.

2009-03-10 Thread NoviceSortOf
It's clear now that __str__(self) or __unicode__ return a usable string to the view. But this does not on the surface appear to be a workable instance of the model itself, that would return fields that I can work with in the template...and/or i haven't figured how to get a handle on it. ie... t

Re: Different Database object behavior on Production and Development servers.

2009-03-09 Thread NoviceSortOf
Ramiro: You put me onto something, the only model that returns coherent data on the command line has str defined for model ie. class Book(models.Model): title = models.CharField(max_length=100) authors = models.ManyToManyField(Author) publisher = models.ForeignKey(Publisher)

Re: Different Database object behavior on Production and Development servers.

2009-03-09 Thread Ramiro Morales
On Mon, Mar 9, 2009 at 12:03 PM, NoviceSortOf wrote: > > > On the command line I'm unable to get a coherent return on my data > object filters or fetches, > > Instead of getting any detail I get a dictionary with nothing but the > words UserProfile, > UserProfile object where Field name and value

Re: Different Database object behavior on Production and Development servers.

2009-03-09 Thread Alex Gaynor
On Mon, Mar 9, 2009 at 9:03 AM, NoviceSortOf wrote: > > > On the command line I'm unable to get a coherent return on my data > object filters or fetches, > > Instead of getting any detail I get a dictionary with nothing but the > words UserProfile, > UserProfile object where Field name and value s

Different Database object behavior on Production and Development servers.

2009-03-09 Thread NoviceSortOf
On the command line I'm unable to get a coherent return on my data object filters or fetches, Instead of getting any detail I get a dictionary with nothing but the words UserProfile, UserProfile object where Field name and value should be. ie. >>>g = UserProfile.objects.filter(email = "dljonss