Re: Question about the send of file versus the django server

2014-02-18 Thread simone monteleone 
Hi Russ,

:) +1 for your example.

I read the Django documentation and I find the Middleware chapter. 

It's possible using the Middleware layer to intercept the HTTP requests.

The "script solution" remain the simplest solution.

My goal is the implementation of system, composed by two devices:

- a data logger

- a web service

The data logger have to send the registered data to the web server.

I think to use an https comunication between the two devices.

So on the same machine, where I install the web server,  I need another web 
server to handle the 
data logger requests.

This is a possible solution.

SM



Il giorno lunedì 17 febbraio 2014 00:27:15 UTC+1, Russell Keith-Magee ha 
scritto:
>
>
> On Sun, Feb 16, 2014 at 10:20 PM, simone monteleone 
> 
> > wrote:
>
>> Hi Russ,
>>
>> The script is now running in a normal bash shell, where I import the 
>> DJANGO_SETTINGS_MODULE.
>>
>> So it's correct to run the script on the machine where the server goes?
>>
>> Or it's possible (and better) runs the commands inside Django?
>>
>> You're missing my point - there's no such thing as "inside Django". 
> Logging onto the server and running the script is the right way to do what 
> you are describing.
>
> A running Django web server isn't a "place" you can run code - it's 
> essentially just a way to turn http://myservice.com into a function call 
> that returns a web page. Requests is just a tool for using a Python script 
> to generate HTTP requests. 
>
> Yes, you can use requests to connect to a Django web server. However, if 
> you're in control of the web server, using requests to do what you 
> describe, instead of just logging onto the server and running a script 
> directly is a bit like saying "I'm going to pick up the cup that is sitting 
> on that table using a fishing rod". Yes, you can probably do it, but unless 
> you've got a good reason, it's much easier to just walk over and pick up 
> the cup with your hand.:-)
>
> Yours,
> Russ Magee %-)
>
>  
>

-- 
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/b955652d-bcc1-483c-b014-5e44c33f162c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Question about the send of file versus the django server

2014-02-18 Thread Russell Keith-Magee 
On Tue, Feb 18, 2014 at 4:10 PM, simone monteleone wrote:

> Hi Russ,
>
> :) +1 for your example.
>
> I read the Django documentation and I find the Middleware chapter.
>
> It's possible using the Middleware layer to intercept the HTTP requests.
>
> The "script solution" remain the simplest solution.
>
> My goal is the implementation of system, composed by two devices:
>
> - a data logger
>
> - a web service
>
> The data logger have to send the registered data to the web server.
>
> I think to use an https comunication between the two devices.
>
> So on the same machine, where I install the web server,  I need another
> web server to handle the
> data logger requests.
>
> This is a possible solution.
>

Ok - this is why you need to provide all the details when you ask a
question. What you've described here is a completely different problem to
the one you've described so far, and one that *would* be well suited to
receiving a file via URL, rather than using a script on the server.

So, yes - you write a view on the server that accepts a file upload, and
when that file is uploaded, you read it and process it. The data logger
itself can absolutely use requests to push this data; you could also use
curl, or any other HTTP tool.

However, a bigger question -- how many "rows" of data will each CSV file
contain?

If it's only one - perhaps you should consider using a HTTP POST, rather
than sending a file with one line in it.

If it's a small number - maybe you should consider modifying your data
logger so that it can send just one record at a time

If it's a *large* number of rows, consider the performance of your web
server. Web servers are designed to respond quickly. They don't behave well
with long lived processes. You may need to investigate handing the uploaded
data using a background queue.

Yours,
Russ Magee %-)

-- 
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/CAJxq8482iy%2BAW2Vr7%3Di_Q7uqf5UVYsL0FObqmjGoPXgfA2rrWg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: python path in webpage error message not virtual environment's

2014-02-18 Thread Russell Keith-Magee 
On Tue, Feb 18, 2014 at 1:11 PM, knowledge_seeker <
sanjivchristop...@gmail.com> wrote:

> I understand the importance of doing projects in virtual environments, but
> I am hitting one snag.
>
> When I have an error in django, and I get the generated webpage with an
> error message, it shows the 'normal' python path, site packages installed,
> etc. For example, I have jinja on my main installation, but not in the
> virtual environment. Yet, jinja shows up in this message as one of the site
> packages; similarly with the other python packages. Is there any way to
> show the python version (and location) and correct site-packages that are
> in the virtual environment in these error messages?
>

It sounds like you've built a virtualenv with --system-site-packages
enabled. If you've got an earlier version of virtualenv (IIRC, version 1.4
or earlier), this was the default option when you created a virtualenv.
When you construct a virtualenv in this way, it's an extension of your
system - so anything in your system PYTHONPATH will also show up in your
virtualenv.

If, on the other hand, you create your virtualenv with --no-site-packages
(which is the default on more recent versions of virtualenv), the
virtualenv is completely isolated. If you don't install a package in your
virtualenv, it won't be available.

To check what version of virtualenv you have, the usual --version flag
works; if you run --help, the description for --no-site-packages will tell
you whether it's the default or not.

As for checking where a package has come from -- if you're in a Python
shell, you can ask Python itself where it got a module. For example:

>>> import django
>>> django.__file__
'/Users/rkm/.virtualenvs/sample/lib/python2.7/site-packages/django/__init__.pyc'

tells you that I'm getting Django from the version installed in my "sample"
virtualenv.

I hope that helps.

Yours,
Russ Magee %-)

-- 
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/CAJxq84-p3DhEGOBxTbfxSw1kN_AvUG%3DyUTf8bO0UZ10cpp5sNg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Digging Up Django Class-based Views

2014-02-18 Thread alois . guillope 
Seems great ! I am looking forward reading it.

I have a question about class-based views (hope it's clear enough) :
I wanted to know when the views are instanciated and when there are garbage 
collected In Django.

Thanks,

Alois




On Friday, February 14, 2014 2:11:43 PM UTC+1, Leo wrote:
>
> Hi all,
>
> the third issue of the small series "Digging Up Django Class-based Views" 
> is out.
> This latest post is about form views.
>
> You find the whole series here
>
> http://lgiordani.github.io/blog/categories/django/
>
> I hope you will find it interesting and useful.
>
> Cheers,
>
> Leo
>
>
> Leonardo Giordani
> Author of The Digital Cat 
> My profile on About.me  - My GitHub 
> page  - My Coderwall 
> profile
>  

-- 
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/53152464-8998-4f95-aa4b-32dd9ec4bdd2%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Digging Up Django Class-based Views

2014-02-18 Thread Tom Evans 
On Tue, Feb 18, 2014 at 11:03 AM,   wrote:
> Seems great ! I am looking forward reading it.
>
> I have a question about class-based views (hope it's clear enough) :
> I wanted to know when the views are instanciated and when there are garbage
> collected In Django.

The class is instantiated at the start of the request, and destroyed
at the end of the request. Each request has its own instance of the
class.

Cheers

Tom

-- 
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/CAFHbX1LpXG%2BaikDBpaJ1LMMvj%3DL5FoHAnZoPQsFbVRa0ydBPVA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Digging Up Django Class-based Views

2014-02-18 Thread alois . guillope 
Ok thanks!


On Friday, February 14, 2014 2:11:43 PM UTC+1, Leo wrote:
>
> Hi all,
>
> the third issue of the small series "Digging Up Django Class-based Views" 
> is out.
> This latest post is about form views.
>
> You find the whole series here
>
> http://lgiordani.github.io/blog/categories/django/
>
> I hope you will find it interesting and useful.
>
> Cheers,
>
> Leo
>
>
> Leonardo Giordani
> Author of The Digital Cat 
> My profile on About.me  - My GitHub 
> page  - My Coderwall 
> profile
>  

-- 
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/fb33df8b-7a94-4ce3-a328-6c4001e8cd8a%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: when I pip-installed django-debug-toolbar, the latest version of Django was installed automatically.

2014-02-18 Thread donarb 


On Monday, February 17, 2014 9:56:09 PM UTC-8, jmin...@gmail.com wrote:
>
> hi Frank,
>
> I appreciate it but seem that this situation is so unusual  that people do 
> not understand. 
> I have done those already.
>
>
> So I do 
> 1) pip uninstall django
> 3) pip uninstall django-debug-toolbar
>
> 2) pip install django==1.3
>
>
>
> then it says:
>
>
> Downloading/unpacking django==1.3
>   Running setup.py egg_info for package django
>
> warning: no previously-included files matching '__pycache__' found 
> under directory '*'
> warning: no previously-included files matching '*.py[co]' found under 
> directory '*'
>   Requested django==1.3, but installing version 1.6.2
> Installing collected packages: django
>   Running setup.py install for django
>
> then the version 1.6 is installed. Any solution?  
>
>
>
>
>
> 2014年2月18日火曜日 9時17分13秒 UTC+9 Frank Bieniek:
>>
>>  Hi Jun,
>> to get your old django back
>> 1) pip uninstall django
>> 2) pip install django==1.3
>> 3) pip uninstall django-debug-toolbar
>> 4) pip install --no-deps django-debug-toolbar
>>
>> line 1 - remove existing django whatever version
>> line 2 - install django 1.3
>> line 3 - remove the django toolbar
>> line 4 says: install django-debug-toolbar but ignore all dependencies of 
>> this package.
>>
>> This should cleanup your environment
>> Cheers
>> Frank
>>
>>
>>
>>
>> Am 17.02.14 21:21, schrieb jmin...@gmail.com:
>>  
>> Hi Frank, 
>>
>>  Thank you for your advice but the version is still 1.6. I straggle with 
>> getting it back to the version 1.3.
>> pip install --no-deps django-debug-toolbar 
>> may help when the version become 1.6, right?
>>
>>  
>>  by the way, I tried
>> pip install --no-deps django==1.3
>>  did not help
>>
>>  Jun
>>
>> 2014年2月18日火曜日 5時01分53秒 UTC+9 Frank Bieniek: 
>>>
>>> Hi, 
>>>
>>> pip install --no-deps django-debug-toolbar 
>>> might help. --no-deps = no dependencies 
>>>
>>> I highly recommend you pip freeze 
>>> your current environement and then just do a pip install --no-deps 
>>> new_component_name, 
>>> thisway you know what is in your environment and no component can seek 
>>> stuff in... 
>>>
>>> hope this helps 
>>> Frank 
>>>
>>> http://pip.readthedocs.org/en/latest/user_guide.html#configuration 
>>>
>>> Am 17.02.2014 20:41, schrieb jmin...@gmail.com: 
>>> > Hello, 
>>> > 
>>> > when I pip-installed django-debug-toolbar, the latest version of 
>>> > Django was installed automatically. Not my intention. I got warning as 
>>> > below. 
>>> > 
>>> > 
>>> >  
>>> > WARNING! 
>>> >  
>>> > 
>>> > You have just installed Django over top of an existing 
>>> > installation, without removing it first. Because of this, 
>>> > your install may now include extraneous files from a 
>>> > previous version that have since been removed from 
>>> > Django. This is known to cause a variety of problems. You 
>>> > should manually remove the 
>>> > 
>>> > /usr/local/lib/python2.7/site-packages/django 
>>> > 
>>> > directory and re-install Django. 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > but never asked if it is OK to do so. So, I tried to uninstall it and 
>>> > reinstall it. Wehn I do 
>>> > rm -rf django 
>>> > pip install django==1.3 
>>> > somehow, it says, 
>>> > 
>>> > 
>>> > Requested django==1.3, but installing version 1.6.2 
>>> > Installing collected packages: django 
>>> >   Running setup.py install for django 
>>> > 
>>> > 
>>> > Again version 1.6 was installed. Does anyone know the solution to it. 
>>> > Please. 
>>> > 
>>> > 
>>> > Jun 
>>> > -- 
>>> > 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...@googlegroups.com. 
>>> > To post to this group, send email to django...@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/a571e1ed-88e1-4263-b288-b34837fd9a80%40googlegroups.com.
>>>  
>>>
>>> > For more options, visit https://groups.google.com/groups/opt_out. 
>>>
>>>   -- 
>> 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...@googlegroups.com.
>> To post to this group, send email to django...@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/02c62809-796b-4871-a7e2-de39f7ace459%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>

What is your version of python? Django 1.3 needs Python 2.4 to work. I'm 
guessing, but maybe a newer version of Python triggers a higher Django 
dependency.

If you really need to run D

Re: when I pip-installed django-debug-toolbar, the latest version of Django was installed automatically.

2014-02-18 Thread donarb 


On Monday, February 17, 2014 9:56:09 PM UTC-8, jmin...@gmail.com wrote:
>
> hi Frank,
>
> I appreciate it but seem that this situation is so unusual  that people do 
> not understand. 
> I have done those already.
>
>
> So I do 
> 1) pip uninstall django
> 3) pip uninstall django-debug-toolbar
>
> 2) pip install django==1.3
>
>
>
> then it says:
>
>
> Downloading/unpacking django==1.3
>   Running setup.py egg_info for package django
>
> warning: no previously-included files matching '__pycache__' found 
> under directory '*'
> warning: no previously-included files matching '*.py[co]' found under 
> directory '*'
>   Requested django==1.3, but installing version 1.6.2
> Installing collected packages: django
>   Running setup.py install for django
>
> then the version 1.6 is installed. Any solution?  
>
>
>
>
>
> 2014年2月18日火曜日 9時17分13秒 UTC+9 Frank Bieniek:
>>
>>  Hi Jun,
>> to get your old django back
>> 1) pip uninstall django
>> 2) pip install django==1.3
>> 3) pip uninstall django-debug-toolbar
>> 4) pip install --no-deps django-debug-toolbar
>>
>> line 1 - remove existing django whatever version
>> line 2 - install django 1.3
>> line 3 - remove the django toolbar
>> line 4 says: install django-debug-toolbar but ignore all dependencies of 
>> this package.
>>
>> This should cleanup your environment
>> Cheers
>> Frank
>>
>>
>>
>>
>> Am 17.02.14 21:21, schrieb jmin...@gmail.com:
>>  
>> Hi Frank, 
>>
>>  Thank you for your advice but the version is still 1.6. I straggle with 
>> getting it back to the version 1.3.
>> pip install --no-deps django-debug-toolbar 
>> may help when the version become 1.6, right?
>>
>>  
>>  by the way, I tried
>> pip install --no-deps django==1.3
>>  did not help
>>
>>  Jun
>>
>> 2014年2月18日火曜日 5時01分53秒 UTC+9 Frank Bieniek: 
>>>
>>> Hi, 
>>>
>>> pip install --no-deps django-debug-toolbar 
>>> might help. --no-deps = no dependencies 
>>>
>>> I highly recommend you pip freeze 
>>> your current environement and then just do a pip install --no-deps 
>>> new_component_name, 
>>> thisway you know what is in your environment and no component can seek 
>>> stuff in... 
>>>
>>> hope this helps 
>>> Frank 
>>>
>>> http://pip.readthedocs.org/en/latest/user_guide.html#configuration 
>>>
>>> Am 17.02.2014 20:41, schrieb jmin...@gmail.com: 
>>> > Hello, 
>>> > 
>>> > when I pip-installed django-debug-toolbar, the latest version of 
>>> > Django was installed automatically. Not my intention. I got warning as 
>>> > below. 
>>> > 
>>> > 
>>> >  
>>> > WARNING! 
>>> >  
>>> > 
>>> > You have just installed Django over top of an existing 
>>> > installation, without removing it first. Because of this, 
>>> > your install may now include extraneous files from a 
>>> > previous version that have since been removed from 
>>> > Django. This is known to cause a variety of problems. You 
>>> > should manually remove the 
>>> > 
>>> > /usr/local/lib/python2.7/site-packages/django 
>>> > 
>>> > directory and re-install Django. 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > but never asked if it is OK to do so. So, I tried to uninstall it and 
>>> > reinstall it. Wehn I do 
>>> > rm -rf django 
>>> > pip install django==1.3 
>>> > somehow, it says, 
>>> > 
>>> > 
>>> > Requested django==1.3, but installing version 1.6.2 
>>> > Installing collected packages: django 
>>> >   Running setup.py install for django 
>>> > 
>>> > 
>>> > Again version 1.6 was installed. Does anyone know the solution to it. 
>>> > Please. 
>>> > 
>>> > 
>>> > Jun 
>>> > -- 
>>> > 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...@googlegroups.com. 
>>> > To post to this group, send email to django...@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/a571e1ed-88e1-4263-b288-b34837fd9a80%40googlegroups.com.
>>>  
>>>
>>> > For more options, visit https://groups.google.com/groups/opt_out. 
>>>
>>>   -- 
>> 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...@googlegroups.com.
>> To post to this group, send email to django...@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/02c62809-796b-4871-a7e2-de39f7ace459%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
What version of Python are you running? Django 1.3 runs with Python 2.4. 
I'm not sure, but maybe a higher version of Python is triggering a higher 
version dependency of Django.

If you

Re: when I pip-installed django-debug-toolbar, the latest version of Django was installed automatically.

2014-02-18 Thread Xavier Ordoquy 

> On Monday, February 17, 2014 9:56:09 PM UTC-8, jmin...@gmail.com wrote:
> hi Frank,
> 
> I appreciate it but seem that this situation is so unusual  that people do 
> not understand. 
> I have done those already.
> 
> 
> So I do 
> 1) pip uninstall django
> 3) pip uninstall django-debug-toolbar
> 
> 2) pip install django==1.3
> 
> 
> 
> then it says:
> 
> 
> Downloading/unpacking django==1.3
>   Running setup.py egg_info for package django
> 
> warning: no previously-included files matching '__pycache__' found under 
> directory '*'
> warning: no previously-included files matching '*.py[co]' found under 
> directory '*'
>   Requested django==1.3, but installing version 1.6.2
> Installing collected packages: django
>   Running setup.py install for django
> 
> then the version 1.6 is installed. Any solution?  
> 

Depending on how old your pip version is, you may need to clean up things in 
your /tmp.
I have faced similar issues with old pip versions. It happened when an 
installation failed and left temporary package files in /tmp. Whatever the 
version you'll want to install, it'll take the one on the /tmp and will not 
remove it by itself.

The correct workaround is to clean /tmp and try a new installation.

Regards,
Xavier Ordoquy,
Linovia


-- 
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/B7C0BA3B-B52C-449A-902D-7B8D096D39F8%40linovia.com.
For more options, visit https://groups.google.com/groups/opt_out.

Django and PrimeUI (Primefaces JS Library) integration

2014-02-18 Thread Livio Leoncio Ribeiro 
I'm working on an app that integrates PrimeUI with Django. I hosted the 
code on bitbucket 
(https://bitbucket.org/livioribeiro/django-primeui)

What's your opinions on it?

-- 
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/95cec8ad-4c7f-4add-81af-4e84aea80fbf%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Questions about Django-socketio and uWsgi Nginx.

2014-02-18 Thread Chen Xu 
I recently started a Django project that has a chatting feature, so I
decided to use django-socketio.

I am trying to setup my uWsgi and Nginx with django-socketio on EC2, but I
have been struggling for a while. Not sure if SockerIOServer and uWsgi is
are the right thing to use.

I have posted a question on stackoverflow :

http://stackoverflow.com/questions/21867839/nginx-and-django-socketio-gives-address-already-in-use-error

Could someone please some directions?

Thanks in advance.


-- 
⚡ Chen Xu ⚡

-- 
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/CACac-qbFqgjHkSytCa24ZGKGa_tr5TZoXpCi06%2Bvwc8xgZX3hw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Many to many logic

2014-02-18 Thread Mike Formica 
I am creating a simple baseball app.  I am stuck with my model to allow a team 
to have multiple players with multiple fielder rankings.  For example player 1 
is on Team A with a short stop rank of 2 but that same player on Team A could 
be a first baseman with a rank of 4.   Can anyone help give me some clues on 
how to approach this.  Thanks so much!

-- 
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/aaec540b-93ca-41e7-b8a6-4d12ddce0bac%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.