wsgi errors lead to 500 launching django on heroku

[Malik Rumi]

I have a wsgi problem I am hoping you can help me with. I am running 
Django1.7 with gunicorn 19.1.1 and wsgiref 0.1.2. I am trying to get this 
to run on Heroku. The last error was that it could not find the template 
home.html and that there was a wsgi error. I added TEMPLATE_DIR to my 
settings and found an article on Google Groups about mod_wsgi. I am not 
running mod_wsgi but it said there that many of the same solutions would 
apply so I decided to try it.

 

However, when I ran the test, much to my surprise, I saw Hello World. I 
checked the logs, and saw 200 OK. I thought maybe somehow the template 
issue had also been a wsgi issue, or perhaps the addition of the wsgi test 
code had somehow fixed a syntax error in my wsgi.py by closing a tag or 
something. Those were my best wild guesses, anyway.

 

So I removed the test code, ran mine again, and sure enough, I was right 
back to the uninformative wsgi errors that led me to seek help in the first 
place. But at least there was no template error this time.

I do not understand how the presence of wsgi debug code could give me 200 
ok and then when I take it out I get 500.

 

I ran it again with the code and debug set to true. I got the same Hello 
World and a 200 ok in the logs. I thought perhaps the code was catching the 
start of the web process but missing the end when it crashed, but no, my 
Heroku dashboard reports the web dyno is up and running fine.

 

I am at a loss as to what to do next here. If you would be so kind as to 
share some insights, I would be most appreciative.  

ps: This is also in the logs but I have been unable to find any useful 
information on it:

gunicorn.http.wsgi.WSGIErrorsWraper object at 0x7f391e254650

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/dab4f3de-bdf8-49bd-9407-53e6abd8e913%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trying out django your first app.

[Collin Anderson]

Hi,

That error means django rendered a page, but the connection to the browser 
was broken.

That could happen because you clicked a link/button more than once, or 
pressed "stop", or somehow canceled the request on the browser end.

Collin

On Thursday, January 1, 2015 3:55:11 AM UTC-5, Siddharth Shah wrote:
>
> Actually I was going through the first app example, 
> https://docs.djangoproject.com/en/1.7/intro/tutorial03/
> On this particular part I am facing problem while executing  
> http://localhost:8000/polls/
>
> Please find the attachment to see the exact error. 
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/a9f7483c-c8dd-4d11-bd86-e43d19322193%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: accessing input tag values(which are created dynamically) from html in backend(python) using post method

[Collin Anderson]

Hi,

It looks like every row will call the same "function9()" when saving? 
Should that be called "function{{result.0}}"?

Ideally, the javascript function itself could figure out which row/form is 
calling it and be able to submit the correct .

Collin

On Wednesday, December 31, 2014 5:55:59 AM UTC-5, Gangadhar Dixit wrote:
>
> Hi guys i am new to html and javascript. my application is to create a 
> table from a list of list went from backend, after creating them 
> dynamically(as length of the list is not known) i need to access some 
> particular values of the table in python backend, when i tried to do this i 
> am able to fetch the value in backend, but the value is not the desired 
> value. The value which it returns is the last element of that table.
>
> given below is my code
>
>  {% for result in list1 %}
>  
> 
>  action = "/fetch_candid/">
> 
>  
>  onclick="document.forms['listOfSearch{{result.0}}'].submit();">{{result.0}}
> 
> 
>
> 
> 
> 
>   value="{{sres}}">
>   
>
>value="{{only_skills}}">
>   
>  
>   
>
> value="{{Date1}}">
> value="{{Date2}}">
>
> 
> 
> 
>  onchange="savestate({{result.0}});" class="select11" id="status8" 
> name="status8" title="Choose Status">
>  {{result.1}}
>  
>  
>  {% if result.1 == "HR_Interview" %}
>  
>   COL
>   
>   
>   {% elif result.1 == "Internal_Interview" %}
>  
>   HR_Interview
>   COL
>   
>   
>   {% elif result.1 == "COL" %}
>  
>   CS
>   
>   
>   {% elif result.1 == "CI" %}
>  
>   CIS
>   
>   
>   {% elif result.1 == "CIS" %}
>  
>   Joining
>   
>  
>  
>  {% elif result.1 == "CS" %}
>  
>   CI
>   
>   
>   {% elif result.1 == "Line_up" %}
>  
>   Internal_Interview
>HR_Interview
>COL
>   
>  {% endif %}
>  
>
> onclick = "function9(this);"> 
>
>
> 
> 
> 
>
>  
>  
>
> {{result.2}}
> 
> {{result.3}}
>  value="{{result.3}}">
> 
> 
> {{result.4}}
> 
> 
> {{result.5}}
> {{result.6}}
> {{result.7}}
> {{result.8}}
> {{result.9}}
> {{result.10}}
> {{result.11}}
> {{result.12}}
> {{result.13}}
> {{result.14}}
> {{result.15}}
> {{result.16}}
> {{result.17}}
> 
> 
>   
> 
> 
> function function9(x)
> {
> var id = $(x).closest("tr").find('td:eq(1)').find("#status8 
> option:selected").text();
> var Client18 = $(x).closest("tr").find('td:eq(3)').text();
> var name18 = $(x).closest("tr").find('td:eq(4)').text();
> console.log("fetched value>>>",id,Client18,name18); 
>  if (id == "COL") 
> {
> var r=confirm("Do you want to generate COL NOW ?");
> if (r == true) 
> {
> alert("before");
> 
> document.getElementById("listOfSearch{{result.0}}").action ="/hrpage/";
> 
> document.getElementById("listOfSearch{{result.0}}").method = 'POST';
> 
> document.getElementById("listOfSearch{{result.0}}").submit();
> alert("after");
> } 
> else 
> {
> 
> document.getElementById("listOfSearch{{result.0}}").submit();
> }
> }
> else
> {
> 
> document.getElementById("listOfSearch{{result.0}}").submit();
> }
> 
> }
>   
>  my application is when i press on the save button i need to get that 
> particular row's client name and candidate name
> kindly help me with this
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/fcbb688a-fed9-4acb-9ff4-84c2e977359f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: django + OAuth2: Sessions

[Collin Anderson]

Hi,

You could try asking on the python-social-auth email list if you haven't.

https://groups.google.com/forum/?fromgroups#!forum/python-social-auth

Collin

On Tuesday, December 30, 2014 7:53:16 AM UTC-5, t.bakogiannis wrote:
>
> Hi everyone,
>
> I am using python-social-auth to implement login via Google, Github, ... 
> The problem I am having is that after the user is redirected to Google or 
> Github the sessionid is reset. I want to preserve the sessionid in order to 
> associate it later with the username. 
>
> I did some research but cannot find something online. The only thing I 
> found was that the sessionid might be reset in the case of changing from 
> http to https which is not the case since my website uses https.
>
> Any help would be very appreciated.
>
> Thanks a lot guys,
> T.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/3770bb13-0dbe-4059-b870-863fa8e5539e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: modelformset question - interspersing extra forms among existing forms

[Collin Anderson]

Hi,

Your case is complicated enough that I'd actually recommend not using 
formsets here and processing a list of plain ModelForms yourself in the 
view. I bet formsets will ending out getting in your way.

Here's a some messy code:

class EntryForm(forms.ModelForm):
race_number = Entry._meta.get_field('race_number').formfield(required=
False)
class Meta:
model = Entry
fields = ['race_number']

def the_view(request, athlete_id):
athlete = get_object_or_404(Athlete, id=athlete_id)
existing = {e.category_id: e for e in athlete.entry_set.all()}
entries = []
for category in Category.objects.order_by('particular'):
entries.append(existing.get(category.pk, Entry(athlete=athlete, 
category=category)))
if request.method = 'POST':
forms = [EntryForm(request.POST, instance=e, prefix=e.category.pk) 
for e in entries]
if all([f.is_valid() for f in forms]):  # be sure to call 
is_valid() on every form
for entry in entries:
if entry.race_number:
entry.save()
if entry.pk and not entry.race_number:
entry.delete()
else:
forms = [EntryForm(instance=e, prefix=e.category.pk) for e in 
entries]
return render(request, 'template.html', {'athlete': athlete, 'forms': 
forms})

{% for form in forms %}
Category: {{ form.instance.category }}
{{ form }}
{% endfor %}

Collin

On Monday, December 29, 2014 6:07:19 PM UTC-5, Richard Brockie wrote:
>
> Hi,
>
> I have the following pseudo model that I will use as the basis of a 
> modelformset:
>
> class Entry:
> athlete = ForeignKey(athlete)
> category = ForeignKey(category)
> race_number = IntegerField
>
> I have a page that displays each athlete's details so the choice of 
> athlete has already been made. I want to add a formset that allows a user 
> to specify a race_number for each of the possible categories available.
>
> An obvious way would be for there to be one Entry for each 
> athlete/category, but in practise this will result in a large entry table 
> that is only ~10% actual data, with the rest being superfluous rows. I'd 
> prefer to avoid this.
>
> Let's assume that an athlete is already entered in 2 categories out of a 
> possible 10. The queryset will return the 2 existing entries, and I can use 
> extra=8 to add in the other possibilities. However, I am not yet done. I 
> want to do the following and would like advice on how to accomplish this:
>
>1. The category for each the 8 possible new entries needs to be 
>assigned before displaying the form - I already know what they are and 
> want 
>to display these categories to the user, leaving the race_number as the 
>only input field.
>2. The categories have a particular (chronological) order that I want 
>respected in displaying the forms to the user, so the 2 existing and 8 
>possible new categories need to be interspersed to follow the correct 
> order.
>3. When it comes time to save the formset, I want only those 
>categories that have been changed by having a race_number assigned or 
>removed to be saved. I want the entries where the race_number has been 
>removed to remain in the entry table. I think I need a way to detect and 
>remove the forms that have not been changed by the user before saving the 
>formset.
>
> Any pointers as to how to do this?
>
> Thanks!
> R.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/522acc71-fa69-4b2d-8b6d-b918a072eaf2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Optimizing admin change view with inlines

[Collin Anderson]

Hi Petros,

I think it's because "value_from_object" only passes the primary key of the 
object and then raw_id_field re-queries it.

https://github.com/django/django/blob/40ccef16/django/contrib/admin/widgets.py#L195
https://github.com/django/django/blob/40ccef16/django/forms/models.py#L151
https://github.com/django/django/blob/40ccef16/django/db/models/fields/__init__.py#L844-L848

Basically, even if you use select_related(), django still queries your 
object again. It looks like a spot where there could be some optimization.

Collin

On Monday, December 29, 2014 1:45:08 PM UTC-5, Ernest0x wrote:
>
>  Hello Collin,
>
> On 12/29/14 07:25, Collin Anderson wrote:
>  
> Hi Petros, 
>
>  I think the raw_id_fields still display the __str__/__unicode__ of the 
> selected object so therefore need to get queried. I wonder if 
> select_related would possibly help?
>
>   
> I do have select_related in the queryset (look at the last version of 
> ExampleBInline in my previous post).
>
> The thing is that if the same fields that are included in raw_id_fields 
> are also included in readonly_fields, the queries are reduced dramatically, 
> despite the fact that the same amount of information is displayed in both 
> cases. __str__()/__unicode__ is still called when the fields are in 
> readonly_fields, so it is really very strange why there is difference 
> between adding and commenting out the readonly_fields line.
>
> Very strange...
>
>  Collin
>
> On Wednesday, December 24, 2014 5:53:02 AM UTC-6, Ernest0x wrote: 
>>
>> On 12/24/14 13:30, 'Petros Moisiadis' via Django users wrote: 
>> > On 12/23/14 19:13, 'Petros Moisiadis' via Django users wrote: 
>> >> Hello people :) 
>> >> 
>> >> I am struggling with optimizing an admin with inlines which causes too 
>> >> many database requests. 
>> >> 
>> >> My model structure is like this: 
>> >> 
>> >> class ExampleA(models.Model): 
>> >> ... 
>> >> 
>> >> class ExampleB(models.Model): 
>> >> aexample = models.ForeignKey('ExampleA', 
>> related_name='bexamples') 
>> >> cexample = models.ForeignKey('ExampleC') 
>> >> dexample = models.ForeignKey('ExampleD') 
>> >> eexample = models.ForeignKey('ExampleE') 
>> >> ... 
>> >> 
>> >> class ExampleC(models.Model): 
>> >> ... 
>> >> 
>> >> class ExampleD(models.Model): 
>> >> ... 
>> >> 
>> >> class ExampleE(models.Model): 
>> >> ... 
>> >> 
>> >> The admin classes: 
>> >> 
>> >> class ExampleBInline(admin.StackedInline): 
>> >> model = ExampleB 
>> >> extra = 0 
>> >> 
>> >> class ExampleAAdmin(admin.ModelAdmin): 
>> >> inlines = [ExampleBInline] 
>> >> 
>> >> admin.site.register(ExampleA, ExampleAAdmin) 
>> >> 
>> >> As I can see with django-debug-toolbar, when rendering the admin 
>> >> template for the inline formset with the forms for ExampleB objects, a 
>> >> new db request is sent to db server for each related field of each 
>> >> ExampleB object. Particularly, I am seeing a lot of queries like 
>> these: 
>> >> 
>> >> SELECT ••• FROM `examplec` WHERE `examplec`.`id` = 1 LIMIT 21 
>> >> SELECT ••• FROM `examplee` WHERE `examplee`.`id` = 2 LIMIT 21 
>> >> SELECT ••• FROM `examplec` WHERE `examplec`.`id` = 2 LIMIT 21 
>> >> SELECT ••• FROM `exampled` WHERE `exampled`.`id` = 2 LIMIT 21 
>> >> SELECT ••• FROM `examplee` WHERE `examplee`.`id` = 3 LIMIT 21 
>> >> 
>> >> The template context is this (I am using grappelli): 
>> >> 
>> >> 21{% if field.is_readonly %} 
>> >> 22{{ 
>> >> field.contents|linebreaksbr }} 
>> >> 23{% else %} 
>> >> the marked line =>  24{{ field.field }} 
>> >> 25{% endif %} 
>> >> 26{% endif %} 
>> >> 27{% if line.fields|length_is:'1' %}{{ 
>> >> line.errors }}{% endif %} 
>> >> 
>> >> 
>> >> I have tried the following optimizations: 
>> >> 
>> >> First try: 
>> >> 
>> >> class ExampleAAdmin(admin.ModelAdmin): 
>> >> inlines = [ExampleBInline] 
>> >> 
>> >> def get_queryset(self, request): 
>> >> qs = super(ExampleAAdmin, self).get_queryset(request) 
>> >> return qs.prefetch_related('bexamples', 
>> >> 'bexamples__cexample', 'bexamples__dexample', 'bexamples__example') 
>> >> 
>> >> Second try: 
>> >> 
>> >> class ExampleBInline(admin.StackedInline): 
>> >> model = ExampleB 
>> >> extra = 0 
>> >>   
>> >> def get_queryset(self, request): 
>> >> qs = super(ExampleInline, self).get_queryset(request) 
>> >> return qs.select_related('cexample', 'dexample', 
>> 'eexample') 
>> >> 
>> >> Third try: 
>> >> 
>> >> class BaseExampleBFormSet(BaseInlineFormSet): 
>> >> def __init__(self, *args, **kwargs): 
>> >> super(BaseExampleBFormSet, 

Re: Trying out django your first app.

[Vijay Khemlani]

For me the development server tends to throw that error at random, but does
render the page correctly

On Thu, Jan 1, 2015 at 2:22 PM, Joel Goldstick 
wrote:

>
>
> On Thu, Jan 1, 2015 at 3:55 AM, Siddharth Shah 
> wrote:
>
>> Actually I was going through the first app example,
>> https://docs.djangoproject.com/en/1.7/intro/tutorial03/
>> On this particular part I am facing problem while executing
>> http://localhost:8000/polls/
>>
>> Please find the attachment to see the exact error.
>>
>> --
>> 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, send email to django-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/django-users.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/208bf155-0295-4818-8e6a-e0d71acf21f5%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> Its much better to copy and paste your traceback in your message.  What
> steps exactly did you do to get this message?  What was the last successful
> part of the tutorial that you were able to perform?
>
> --
> Joel Goldstick
> http://joelgoldstick.com
>
> --
> 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, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAPM-O%2Bxo5D6L21AM4UX8gniKrqU%3Dg6scTiNhTk2_cnHbk8THwQ%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CALn3ei05WkmgbhULT424kz2cvpwUsu0p8G8PTUG-NajFENRAJg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: create unmanaged model to oracle view/synonym

[Edgar Gabaldi]

Fabio,

Django ORM support Oracle Database[1].

If you want connect an existing oracle database, i recomend you see the
inspectdb management command.

[1] https://docs.djangoproject.com/en/1.7/ref/databases/#oracle-notes
[2] https://docs.djangoproject.com/en/1.7/howto/legacy-databases/


On Thu, Jan 1, 2015 at 2:40 PM, Shai  wrote:

> Hi Fábio,
>
> On Wednesday, December 31, 2014 6:05:05 PM UTC+2, Fabio Caritas
> Barrionuevo da Luz wrote:
>>
>> Hello, is possible with Django 1.7 create a unmanaged Django model for
>> Oracle database View?
>>
>>
>>
> Yes. In your model's Meta, set managed to False and db_table to the view
> name:
>
> class MyUnManagedModel(models.Model):
> # ...
> # fields
> # ...
> class Meta:
> managed = False
> db_table = 'view_name'
>
> Have you run into difficulties?
>
> HTH,
> Shai.
>
> --
> 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, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/bf043f16-043a-4f0f-a6bf-2856c405be43%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAGjPPH%3DM8k9MWOKuiqL0ABPiG-G9PwGOeJ_4yLLFifz6rVDoZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: FormSets with arbitary number of forms

[Edgar Gabaldi]

The formset allow you create many instances of an object. What you need is
the inline formset. When you create a Album, you can create one or more
songs.

On Wed, Dec 31, 2014 at 4:59 PM, Some Developer 
wrote:

> I've been reading the documentation on FormSets and must admit that I am a
> bit confused.
>
> I have a model called Album that contains many Songs. But when a user
> creates a new album I have no idea how many songs the Album will contain.
>
> So I want to create a FormSet that has an Album form and many Song forms
> but I need the user to be able to decide how many Song forms there are in
> advance. Is this possible?
>
> I might be misunderstanding the documentation but I couldn't see anything.
>
> --
> 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, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/54A447A2.4010804%40googlemail.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAGjPPHk3xZ3r_ugBLA_crVWe4dym8nd0-q029B_-A2fP%2BYS9Rw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trying out django your first app.

[Joel Goldstick]

On Thu, Jan 1, 2015 at 3:55 AM, Siddharth Shah 
wrote:

> Actually I was going through the first app example,
> https://docs.djangoproject.com/en/1.7/intro/tutorial03/
> On this particular part I am facing problem while executing
> http://localhost:8000/polls/
>
> Please find the attachment to see the exact error.
>
> --
> 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, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/208bf155-0295-4818-8e6a-e0d71acf21f5%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

Its much better to copy and paste your traceback in your message.  What
steps exactly did you do to get this message?  What was the last successful
part of the tutorial that you were able to perform?

-- 
Joel Goldstick
http://joelgoldstick.com

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAPM-O%2Bxo5D6L21AM4UX8gniKrqU%3Dg6scTiNhTk2_cnHbk8THwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: create unmanaged model to oracle view/synonym

[Shai]

Hi Fábio,

On Wednesday, December 31, 2014 6:05:05 PM UTC+2, Fabio Caritas Barrionuevo 
da Luz wrote:
>
> Hello, is possible with Django 1.7 create a unmanaged Django model for 
> Oracle database View?
>
>
>
Yes. In your model's Meta, set managed to False and db_table to the view 
name:

class MyUnManagedModel(models.Model):
# ...
# fields
# ...
class Meta:
managed = False
db_table = 'view_name'

Have you run into difficulties?

HTH,
Shai.

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/bf043f16-043a-4f0f-a6bf-2856c405be43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Trying out django your first app.

[Siddharth Shah]

Actually I was going through the first app example, 
https://docs.djangoproject.com/en/1.7/intro/tutorial03/
On this particular part I am facing problem while executing 
 http://localhost:8000/polls/

Please find the attachment to see the exact error. 

-- 
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, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/208bf155-0295-4818-8e6a-e0d71acf21f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.