Re: Dynamic forms data is not getting sent in the POST

> rendering code in template: > > > {{ formset.management_form|crispy }} > > > {% for form in formset.forms %} > > {% crispy form formset.crispy_helper %} > > {% endfor %} >

Re: Corrupted Migration?

Hi all, Thanks for all the help! Sorry for the incredibly slow response, but I just wanted to give an update: The problem was that I was trying to remove a foreign key (let's call that foreign key "book", referencing a "book" table). I had to manually go into the migration and add '_id'

Re: Keep object along a session.

sorry, typo. Regards. I need to create an object when a user connects to the system. and the object must be kept alive until the user disconnects. This object is unique for each user connected to the system. This object can not be serialized and changes its state throughout his life. This

Keep object along a session.

Regards. I need to create an object when a user connects to the system. and the object must manternerce alive until the user disconnects. This object is unique for each user connected to the system. This object can not be serialized and changes its state throughout his life. This object

Re: duplicated selenium test fails

Hi Ulrich, On 10/19/2015 03:03 AM, Ulrich Laube wrote: > It boils down to this: > > I have a selenium test in a django project against the admin page. All > green. > If I duplicate the test class via copy and paste + renaming, then one is > green and one is red, despite containing the same code.

Dynamic forms data is not getting sent in the POST

I'm trying to add dynamic forms to my inline formset using the steps mentioned in the post: Add a dynamic form to a django formset using javascript in a right way I have inline

Re: save() prohibited to prevent data loss due to unsaved related object 'committee'

What does the Committee.save() method look like? You have no problem if you remove that method? On Tuesday, October 20, 2015 at 2:22:24 PM UTC-4, Yaniv Mirel wrote: > > I've found out that this error is happening because I also have a def > save() function on the committee model. > So I am not

Re: save() prohibited to prevent data loss due to unsaved related object 'committee'

I've found out that this error is happening because I also have a def save() function on the committee model. So I am not sure if this is a bug or I am not suppose to have it like that. On Tuesday, October 20, 2015 at 9:02:27 PM UTC+3, Yaniv Mirel wrote: > > Hi, > > I am getting this error when

Use of transactions

Hello, first, let me give you an idea of the problem I'm facing. This is a company with a fruit packaging plant, they use several printers for the barcodes they attach in fruit boxes, clamshells and pallets. There is a Django table that keeps track of the current number for each one (caja,

save() prohibited to prevent data loss due to unsaved related object 'committee'

Hi, I am getting this error when running model post save signal. The error traceback is for gr.save() it seems like the committee model is not saving before it need to be assigned to GroupRole model as a FK. this is the post_save signal code. @receiver(post_save, sender=Community) def

Any opening for Django Entry Level in Dallas area

Hello all, My name is Muhammed Elegbede. I have been in and out of programming for about 6 years now owing to different job openings. Right now, I am fully set to return to programming. I would love to take up any entry level django position if there's any available. I have limited myself to

Re: What is the recommended schema design for dynamic dates in Django for PostgreSQL?

Hi Erik, thanks for m2m suggestion. What do you think about using suggested view in DB? (@SO) (i.e. the DB would do the conversion on the fly) Radek On Tuesday, October 20, 2015 at 5:39:18 PM UTC+2, Erik Cederstrand wrote: > > > > Den 20. okt. 2015 kl. 14.09 skrev Radek Svarz

Re: What is the recommended schema design for dynamic dates in Django for PostgreSQL?

> Den 20. okt. 2015 kl. 14.09 skrev Radek Svarz : > > [...] > Django code and further long details are @ SO: > http://stackoverflow.com/questions/33167079/what-is-the-recommended-schema-design-for-dynamic-dates-in-django-for-postgresql > Regarding your need for a way

Re: Push notifications in Django

*For web app you should use web sockets, not push notifications.* On Sunday, June 28, 2015 at 6:51:36 AM UTC+3, harsh.rathore14 wrote: > > I want to build an Webapp which will have push notification on comments, > mentions etc. > -- You received this message because you are subscribed to the

Re: makemigrations and language_code

Simply run ./manage.py makemigrations myapp That will avoid running for all your installed apps. On Monday, October 19, 2015 at 12:58:23 AM UTC-4, Hugo Osvaldo Barrera wrote: > > I'm having a rather confusing scenario regarding makemigrations and > language_code: > > * I've an app (let's

Re: Why django (when using inlineformset) run 20 times the same SQL for each record (form)?

Here is my view, model and form: https://gist.github.com/fellipeh/f10824e61552efd71c8e Here is my HTML: {% csrf_token %} {{ formset.management_form }} {% crispy formset helper %} Regards, T.·.F.·.A.·. S+F *Fellipe Henrique P. Soares*

Re: Why django (when using inlineformset) run 20 times the same SQL for each record (form)?

Are you sure that's the code? I think that would generate an error as you can't combine variables in the same {{ ... }} tag. Not being pedantic; it's just important to make sure we're looking at the right HTML to help diagnose the problem. Can you paste the whole view? Thanks! On Tuesday, 20

Re: ValueError: save() prohibited to prevent data loss due to unsaved related object

Could you provide a minimal example project that reproduces the error? On Tuesday, October 20, 2015 at 2:42:57 AM UTC-4, Mike Dewhirst wrote: > > On 18/10/2015 5:18 PM, Mike Dewhirst wrote: > > On 18/10/2015 6:28 AM, Tim Graham wrote: > >> Do you have code that worked before (didn't result in

Re: What is the recommended schema design for dynamic dates in Django for PostgreSQL?

> Den 20. okt. 2015 kl. 14.09 skrev Radek Svarz : > > [...] > 1 Milestone is a date stored as a string in form -MM-DD or a special tag > "today", which means daily changing date (dynamic - the date was not stated, > but until today is some state valid - if today is

What is the recommended schema design for dynamic dates in Django for PostgreSQL?

Hi all, we have a Django app focusing on timeline evolution visualization. There we have conceptually the relationship of: 1 Item with 1 or more Lifecycles (more for versioning purposes) 1 Lifecycle has 0..n Milestones 1 Milestone is a date stored as a string in form -MM-DD or a special

Re: ValueError: save() prohibited to prevent data loss due to unsaved related object

On 18/10/2015 5:18 PM, Mike Dewhirst wrote: On 18/10/2015 6:28 AM, Tim Graham wrote: Do you have code that worked before (didn't result in data loss) but doesn't work now? If so, it could be a bug in Django. Yes indeed. It is all in my repo. I'll go back to 1.7.x and rerun the tests and