Re: Django Channels: best way to launch multiple workers

[Piet van Leeuwen]

On a server is there a recommendation for how many workers to have running?

With Gunicorn we would run...

def max_workers():
return cpu_count() * 2 + 1




On Thursday, February 9, 2017 at 11:38:07 AM UTC+13, Andrew Godwin wrote:
>
> The difference is mostly in Python performance - threading in Python tends 
> to perform worse than using multiple processes, which is why we recommend 
> using multiple processes in the docs. However, you can save a bit of memory 
> usage with threading, so you can use that if you want.
>
> I would not, however, recommend running more than 2 - 4 threads per 
> process, as otherwise you'll likely see performance take a slide due to the 
> GIL.
>
> Andrew
>
> On Wed, Feb 8, 2017 at 11:53 AM, Charlie DeTar  > wrote:
>
>> What's the best way to launch multiple Django channels workers on a 
>> production server to take advantage of extra cores?
>>
>> The documentation says 
>> 
>> :
>>
>> Each server is single-threaded, so it’s recommended you run around one or 
>>> two per core on each machine; it’s safe to run as many concurrent workers 
>>> on the same machine as you like, as they don’t open any ports (all they do 
>>> is talk to the channel backend).
>>
>>
>> However, `python manage.py help runworker` lists a "--threads" option, 
>> which seems to imply that a single invocation of runworker can launch 
>> multiple workers.
>>
>> Is there a functional difference between `./manage.py runworker 
>> --threads 4` and launching `./manage.py runworker` process 4 times?
>>
>> best,
>> Charlie
>>
>> -- 
>> 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 https://groups.google.com/group/django-users.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/django-users/8097b8f7-3f89-49a6-b189-58a0713972ef%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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/96819d5d-cb83-4e11-af79-3c69b16f8b3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Creating login page with Django using HTML and CSS

[ADEWALE ADISA]

You can also check the following link:

https://simpleisbetterthancomplex.com/tutorial/2017/02/18/how-to-create-user-sign-up-view.html
On Oct 9, 2017 3:34 AM, "Tunde Bakare"  wrote:

> Hello,
>
> I am new to Django. And i have gone through materials for steps and ways
> to create Login page for an application with Django using HTML and CSS.
>
> Anyone has materials and easy step by step i can use to learn.
>
> Thank you
>
> --
> 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 https://groups.google.com/group/django-users.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-users/d10571fe-e232-4aa7-851d-dbc5c4a18012%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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAMGzuy__wCGd1vPLwwiME-qB3GEDWB%2B7FRmfwq5cda7deKbMjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can I use Django Channels to solve this architectural prolem?

['matrix1900' via Django users]

Hi,

i read the article, because i have the same situation. Its not clear for me 
how to use the receive_many function outside Django. Its only possible to 
send message  
*Group('sensor').send({'text': 'Hello, world!'}) *from outside and receive 
it on the browser.

But not to receive a message. 


*Here my code example:* 

import asyncio
import traceback
import sys
 
from channels import Group
 
from sensor.asgi import channel_layer
 
 
class ChannelsConsumer(object):
async def start(self, channel_layer, channel_names):
if isinstance(channel_names, str):
channel_names = [channel_names]
 
while True:
channel, message = 
channel_layer.receive_many('sensor',block=False)
#self.stdout.write('RECV' + str(channel) +  str(message))
Group('sensor').send({'text': 'Recieved' + str(channel) + 
str(message)})
if channel:
print('RECV', channel, message)
self.stdout.write('RECV' + str(channel) +  str(message))
#
# await some_long_async_operation_here()
#
Group('sensor').send({'text': 'Hello, world!'})
else:
await asyncio.sleep(0.1)
 

def run(self, channel_layer, channel_names):
loop = asyncio.get_event_loop()
asyncio.ensure_future(self.start(channel_layer, channel_names))
try:
loop.run_forever()
except Exception as e:
traceback.print_exc()
finally:
loop.close()
 
 
consumer = ChannelsConsumer()
consumer.run(channel_layer, 'sensor')
 

Am Freitag, 18. November 2016 20:30:56 UTC+1 schrieb Andrew Godwin:

>
>
> On Fri, Nov 18, 2016 at 6:57 AM,  wrote:
>
>> Hi Andrew, thanks for the advice. Since I implement websockets to serve 
>> my users the live logs, I would just route the service commands (e.g. 
>> "service.start") through the websocket, too. That way I also don't have to 
>> block other things while waiting for the response whether the command was 
>> successful or not.
>>
>> I read into the documentation and setup a basic web socket site that is 
>> working (woohoo). The rest is just more reading and learning and trial and 
>> error, but I am confident I get this working.
>>
>> However, how would I connect my Controller to the Channel layer, setup a 
>> consumer and a producer? I got it working for Django and websockets, but 
>> from a standalone python app? hmmm..
>>
>>
> You can use the raw Python ASGI layer directly from outside Django. I need 
> to write some more docs about this use case and how to go with it (right 
> now it's more been in talks I've given) but basically you want to:
>
> * Import projectname.asgi:channel_layer (the same thing you pass to Daphne)
> * Call the ASGI functions on that to send and receive messages. They're 
> documented here: 
> http://channels.readthedocs.io/en/stable/asgi.html#specification-details
>
> The normal pattern would be to have a loop that listens on 
> receive_many(["channel1", "channel2"]) for incoming messages and dispatch 
> them to a handler function, and to call send(channel, message) directly 
> from anywhere you want to send a message. Send is always non-blocking, but 
> can raise ChannelFull - the spec linked above should cover the specifics.
>
> Andrew
>  
>
>>
>> On Wednesday, 16 November 2016 06:51:19 UTC+1, Andrew Godwin wrote:
>>
>>> You could use channels (well, ASGI, it's lower-level interface) for the 
>>> interconnect:
>>>
>>>  - Use channels for signals from the web service to the controller 
>>> daemon (maybe "service.stop" or "service.start" with the service name in 
>>> the message payload). You can trigger these from simple AJAX or GET views, 
>>> no need for websocket here.
>>>  - Send the log continuously out to a Group as it's received, one group 
>>> per service. Then, when someone joins and wishes to tail the log, tie in 
>>> their socket to the group.
>>>
>>> However, this does not supply log playback of lines before a client 
>>> joins, so you'd have to fill in that gap. In the end, you're probably 
>>> looking at some sort of datastore in the middle there to store logs and 
>>> then replay them into a socket as it joins.
>>>
>>> Andrew
>>>
>>> On Tue, Nov 15, 2016 at 2:27 PM,  wrote:
>>>
 Hi there,

 I want to develop a Django site where users have the possibility to 
 interact with systemd services in realtime and to see the log output in 
 realtime.

 I sketched up a quick draft on my idea how this could work: 
 https://i.imgur.com/pd5uLtl.jpg


 One simplified use-case would be:

   1. User visits Django website.
   2. User chooses one of many systemd services. each service would be 
 represented by a single webpage, eg. /services/id/1, /services/id/2...
   3. User gets presented a realtime log, the source being either 
 journald or 

Savepoints and Group Replication need MySQL upgrade

[yasser . ahmed]

Hello,

I am using 2nd Generation cloud SQL (group replication) with Django.

Django creates savepoints when nesting atomic transactions. Group 
replication supports savepoints from MySQL 5.7.19 and up.

Cloud sql is using version 5.7.14. When will google upgrade the cloud SQL 
version as this is an important feature?

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/fb86cfff-804e-4961-aa25-dd382ba6ba07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Using Django /Channels for polling complex sensor data

['matrix1900' via Django users]

Hi,

My project is to develop a Web Interface for a complex machine. 

   - The web interface should be applied for maintaining and diagnostics. 
   - The webserver should run on a embedded device. 
   - On the embedded device a process which takes all the required data 
   from the complex machine (Sensor data, etc..) and delivers the data to 
   the website  is needed. 
   - Another requirement is, the webinterface should be available for a 
   long product live cycle.
   - The webinterface should show realtime data and allow to manipulate 
   data from the complex machine. 


big requirement: Multiple users can retrieve different web pages that 
contain different data. I need a background worker who receives a separate 
message from each user of the web interface. the message contains the 
information which live data should be sent continuously. 

How do I solve the problem if I have multiple users who want to see 
different live data on the web page? The number of users will not be very 
large. I think  maximum of <10 users. 



I found this example : 
https://medium.com/@johngrant/raspberry-pi-and-django-channels-8d5cddb36226


The idea in this example is, start a separate background worker and send 
periodic data from a sensor to the webserver/website.  But how can I 
receive data from the background receiver or is the example not suitable 
for my problem?



Best Regards,


-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2a091469-ca24-4490-98a4-92f4571215a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Access denied for MySQL user in Django

[Ivan Gruer]

Hi,
as far as i understood cdraccess  is a DB gust user, right?

If so, from your DB admin user, grant cdraccess to access MySQL environment 
table 'mysql.user' as follow:
 
GRANT SELECT ON `mysql`.`user` TO 'user_gui'@'%';

To me it worked,
Ivan

On Monday, January 25, 2016 at 7:52:33 PM UTC+1, James Schneider wrote:
>
>
>>> And I get the usual error message:
>>>
>>> (1045, u"Access denied for user 'cdraccess'@'77.95.177.35' (using password: 
>>> NO)")
>>>
>>>
>>> I have print statements and everything looks correct. It is printed as 
>>> it is in the settings.py file.
>>>
>>> One thing I noticed is that the IP 77.95.177.35 is my machine's IP, NOT 
>>> the host's IP. For some reason the host IP (as it is given in the 
>>> settings.py file) is replaced in this error message by my machine's IP. Is 
>>> that normal?
>>>
>>
>
> Another thought. Do you manage the server/MySQL instance? Have you looked 
> at the logs for MySQL to ensure that the password is the only issue? It's 
> possible you are getting access denied for a number of reasons, including 
> the database not existing when Django tries to access it.
>
> -James
>
>  
>

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/e44f3710-d693-4f37-8a03-9eff7aebd258%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Access denied for MySQL user in Django

[Ivan Gruer]

Hi,
as far as i understood cdraccess  is a DB gust user, right?

If so, from your DB admin user, grant cdraccess to access MySQL environment 
table 'mysql.user' as follow:
 
GRANT SELECT ON `mysql`.`user` TO 'cdraccess'@'%';

To me it worked,
Ivan

On Thursday, January 14, 2016 at 2:27:27 PM UTC+1, Galil wrote:
>
> I have created a Django app and which uses MySQL. The settings.py file in 
> the database sections is:
>
> DATABASES = {
> 'cdraccess': {
> 'ENGINE': 'django.db.backends.mysql',
> 'NAME': os.environ.get('CDR_DB_NAME', 'portal2'),
> 'USER': os.environ.get('CDR_DB_USER', 'cdraccess'),
> 'HOST': os.environ.get('CDR_DB_HOST', '127.0.0.1'),
> 'CONN_MAX_AGE': 0,
> 'PASSWORD': os.environ.get('CDR_DB_PASSWORD', ''),
> },
> 'default': {
> 'ENGINE': 'django.db.backends.sqlite3',
> 'NAME': 'db.sqlite3',
> }}
>
> I run the app like:
>
> CDR_DB_PASSWORD='password' CDR_DB_HOST='host_name' ./manage.py runserver
>
> but I get the following error:
>
> Access denied for user 'cdraccess'@'host_ip_here' (using password: NO)")
>
> I tried to access the database from terminal, like:
>
>$ mysql --host=[host_name] --user=cdraccess -p portal2
>
> and worked fine.
>
> What is going wrong in here? And what does this "(using password: NO)" 
> mean?
>
>

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/71856d5f-d404-4637-8497-1203108d101a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Creating login page with Django using HTML and CSS

[Gourav Chawla]

It isn't clear what are you looking for but if you need instructions on 
creating registration, login, logout views then this[1] is a good place to 
start. Also, look into another chapter where the author talks about using 
django-registration package to remove the hassle of building your own 
registration system.

[1]: http://www.tangowithdjango.com/book17/chapters/login.html

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/fd5d9546-05ce-49a8-a819-51646c6b48d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: django project avoid reload page where work algorithm

[James Schneider]

On Oct 8, 2017 11:25 AM, "Xristos Xristoou"  wrote:





> In the background celery worker picks your task and executes it. It
> doesn't matter how long that takes. Once task is completed worker waits for
> next task.
>
> Every task gets id which you can return to frontend and then for example
> using ajax call you could query if task is ready and inform user about
> progress or completition.
>
>
>> can you show some example with my code ?is easy to bulid ?



It is not necessarily trivial to implement Celery or any sort of batch
processor. It requires a separate server demon that may not be supported on
your hosting platform. I'd suggest combing through the docs for Celery and
the specific Django documentation for it, which includes many examples.

http://docs.celeryproject.org/en/latest/django/first-steps-with-django.html

-James

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CA%2Be%2BciVC_hQtE3AAp%2Bps%3D0hfyEGFBxWiND1u_m9N1Dve1aBXjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: LDAPSearch Troubleshooting

[James Schneider]

On Oct 8, 2017 9:44 PM, "Ken Jenney"  wrote:

1) I'm using a service account. I verified the DN's by connecting using
Apache Directory Studio.


I'm assuming this means that you only verified that your intended DN
strings are valid and that the passwords for both the service account and
your user account are correct?

2) I just promoted the service account user but I'm still facing the same
error.
3) Logging is not helping: it's only reiterating what the original error is
telling me: Caught LDAPError while authenticating ken:
INVALID_CREDENTIALS({'desc': 'Invalid credentials'},) I added logging by
adding this to the config:


I'd be interested to see what the Synology says. You may need to increase
the logging verbosity.




Couple other questions:

a) What do you have listed in AUTHENTICATION_BACKENDS? I'm assuming you
have both the LDAP module and the built-in back-end listed in that order
since you are requesting groups?

a.1) Is it possible that your initial authentication is failing against
LDAP but succeeding against the local authentication back-end, potentially
leading you to believe that LDAP is partially working when it isn't?

a.2) Do you see the service account successfully authenticating on the
Synology upon login at least once?

b) Is this the correct DN for your service account?

AUTH_LDAP_BIND_DN = "CN=netbox,CN=users,DC=kensnet,DC=priv"

Shouldn't that be uid=netbox?

-James

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CA%2Be%2BciWvx3iAWi1P3isTe6CQin%2By8015GZ28kNDK6ynskx8v5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: tox?

[James Schneider]

On Oct 8, 2017 3:21 PM, "Christophe Pettus"  wrote:

On a Django-related project I maintain, someone's submitted a PR that
includes a tox.ini file.  I'll admit I've not used tox before; how standard
is it for Django testing?  I like the idea of being able to run tests
against multiple versions in parallel, but I don't want to require a tool
for testing unless it's very widely used.


I'm not familiar with Tox or it's usage, but in general, I wouldn't make it
a requirement for an end user, and possibly not even for a contributor of a
PR.

IMO, a unit test should only rely on the base test framework included with
Django. An extension like Tox (based on the information blurb above) should
take those tests and run them in multiple environments automatically in a
dedicated test environment that you manage. An end user should be able to
run your tests against their specific environment without it, along with PR
authors for simple bugfix patches. Code standards should be clearly
published and outlined, and should include comprehensive enough information
that all target environments will pass the same tests, ie requiring Py2/Py3
compatibility, PEP 8, and so on.

Larger PR's that introduce new functionality or significant code changes
should be required to utilize something like Tox before being
submitted/accepted, but as long as that is also clearly documented, any dev
providing code at that level shouldn't have an issue complying.

OTOH, it's presumably your software, and if you like it and want everything
tested to that degree before it reaches the PR stage, that's your call.
Larger projects may require this to filter out the number of PR's that
people file, but you also run the risk of missing out on good patches that
an author didn't submit because they didn't feel like deploying and
learning a new test suite.

As a rebuttal against my own argument for not requiring it, Django does
ship with built-in Tox support, although I'm sure other configuration is
required:

https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/
unit-tests/#running-tests-using-tox

Just my $0.02...

-James

-- 
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 https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CA%2Be%2BciVwVoqGkm_Ea43VUvJHmwmARrUgyhgwQk_KXf2WNh5Y0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django queryset returning corrupted value

[Web Architect]

Hi Antonis,

Thanks for your response. You are right, The issue wasn't in MySQL or even 
Django ORM. We were using Cachalot 
(http://django-cachalot.readthedocs.io/en/latest/) for query caching which 
was causing the issue. Disabling cachalot fixed the issue. Would need to 
look more into query caching  to use it properly without issues.

Thanks.

On Monday, October 9, 2017 at 1:54:20 AM UTC+5:30, Antonis Christofides 
wrote:
>
> Hi,
>
> this is very strange of course. I doubt it has anything to do with MySQL, 
> because even if MySQL had done something wrong and had returned a long in 
> place of a string, the Django ORM should have caught that and raised an 
> error earlier. So the problem must be in Django. (But of course with such a 
> strange problem anything is possible).
>
> I'd first try to clean up the Python compiled files (remove them), remove 
> and recreate the virtualenv, and restart Django. Also check the disk space 
> in the machine.
>
> Regards,
>
> Antonis
>
> Antonis Christofideshttp://djangodeployment.com
>
> On 2017-10-07 11:40, Web Architect wrote:
>
> Hi Antonis, 
>
> Thanks for your response:
>
> Following is the model:
>
> from treebeard.mp_tree import MP_Node
>
> @python_2_unicode_compatible
> [docs] 
> class
>  AbstractCategory(MP_Node):
> """A product category. Merely used for navigational purposes; has no  
>   effects on business logic.
> Uses django-treebeard."""
> name = models.CharField(_('Name'), max_length=255, db_index=True)
> description = models.TextField(_('Description'), blank=True)
> image = models.ImageField(_('Image'), upload_to='categories', blank=True,
>   null=True, max_length=255)
> slug = models.SlugField(_('Slug'), max_length=255, db_index=True)
> Following is the queryset:
>
>  >>>cat=category.objects.get(pk=11)
>
> >>> cat
>
> Traceback (most recent call last):
>
>   File "", line 1, in 
>
>   File 
> "/home/pinakee/oscar_v1/lib/python2.7/site-packages/django/db/models/base.py",
>  line 496, in __repr__
>
> u = six.text_type(self)
>
>   File 
> "/home/pinakee/oscar_v1/lib/python2.7/site-packages/oscar/apps/catalogue/abstract_models.py",
>  line 102, in __str__
>
> return self.full_name
>
>   File "/home/waltzz/jivaana/jivaana_custom/catalogue/models.py", line 61, in 
> full_name
>
> cache_key = self.slug + '_full_name'
>
> TypeError: unsupported operand type(s) for +: 'long' and 'str'
>
> >>> cat.slug
>
> 3L
>
>
> The reason above exception is coming because cat.slug is long and not string 
> as it is supposed to be.
> MySQL Version:
>
> mysql -V
>
> mysql  Ver 14.14 Distrib 5.5.48, for Linux (x86_64) using readline 5.1
>
>
> OS:
>
> 2.6.32-504.30.3.el6.x86_64
>
>
> Thanks.
>
>
> On Friday, October 6, 2017 at 11:49:04 PM UTC+5:30, Antonis Christofides 
> wrote: 
>>
>> Hi,
>>
>> could you show the code that defines the slugfield, the queryset that is 
>> returning the wrong value, full error message and traceback (if available), 
>> and the version of your OS and RDBMS?
>>
>> It doesn't matter if the problem is more general; let's focus on one 
>> specific manifestation of it.
>>
>> Regards,
>>
>> Antonis
>>
>> On October 6, 2017 8:16:20 PM GMT+03:00, Web Architect  
>> wrote: 
>>>
>>> Hi, 
>>>
>>> We have running an ecommerce site using Django 1.8.13. It has been 
>>> running fine for a year. But suddenly the django querysets are returning 
>>> corrupted values. I am completely clueless why this is happening. Like a 
>>> model field is of type SlugField but queryset is returning long. 
>>> Would really appreciate if anyone could throw some light on how to fix 
>>> the above issue. When I check the values in MySQL DB using PhpMyAdmin and 
>>> everything is fine. 
>>> Thanks,
>>> Pinakee
>>>
>> -- 
> 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 https://groups.google.com/group/django-users.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-users/0fb7769f-409a-4951-9e2d-4807f0873c16%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