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

> Den 20. okt. 2015 kl. 18.09 skrev Radek Svarz : > > 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) In general, I think of DB views as either a performance

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: 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