Re: Request for help: building a docker/vagrant platform for running Django's test suite

2015-04-21 Thread Tommy Beadle
I have a decent amount of Docker experience.  Doing something like this
definitely sounds like a reasonable thing to do with Docker.  I'd be
willing to help out.

On Tue, Apr 21, 2015 at 1:25 PM, Tim Graham  wrote:

> Hi John,
>
> Kevin and I are going to chat about it tonight. I'll keep this thread
> updated with ours plans and progress.
>
> Tim
>
> On Tuesday, April 21, 2015 at 1:00:46 PM UTC-4, John Giannelos wrote:
>>
>> Hey all,
>>
>> I would also be interested to contribute to this effort.
>> Is there a ticket/github issue to track it?
>>
>> Best,
>> John
>>
>> On Sun, Apr 19, 2015 at 11:18 AM, Kevin Glavin 
>> wrote:
>>
>>> Hi Tim,
>>>
>>> I have been using Docker, Vagrant, and Jenkins for a while now
>>> independently. Would love to help out with this effort.
>>>
>>> Feel free to reach out to me privately if you'd like to continue the
>>> discussion.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Django developers  (Contributions to Django itself)" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to django-develop...@googlegroups.com.
>>> To post to this group, send email to django-d...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/django-developers.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/django-developers/0d3fd331-5d1f-4e9c-b7a6-2586341d419c%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 developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/b6e51b9c-41e4-4756-b43a-1497ec727aac%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Grace and Peace,
Tommy B.

I want to live like I know what I'm leaving.
--Switchfoot, "Awakening"

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAKfxM0LbZH63AXK9O98LYiFwse151n2%3DqOL-Ov6nUCUd%2BfwsQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Unneeded index created with unique=True and db_index=False in TextField

2015-04-14 Thread Tommy Beadle
I believe that Postgres will *always* create an index on a column with a
UNIQUE constraint.

regression=> create table yo (id serial primary key, blah varchar(32)
unique);
CREATE TABLE
regression=> \d yo
Table "public.yo"
 Column | Type  |
Modifiers
+---+-
 id | integer   | not null default
nextval('yo_id_seq'::regclass)
 blah   | character varying(32) |
Indexes:
"yo_pkey" PRIMARY KEY, btree (id)
"yo_blah_key" UNIQUE CONSTRAINT, btree (blah)

regression=> drop index yo_blah_key;
ERROR:  cannot drop index yo_blah_key because constraint yo_blah_key on
table yo requires it
HINT:  You can drop constraint yo_blah_key on table yo instead.


On Tue, Apr 14, 2015 at 9:01 PM, Some Developer 
wrote:

> Using Django 1.8, psycopg2 2.6 and PostgreSQL 9.4.1.
>
> I have a model with a models.TextField(unique=True, db_index=False,
> primary_key=False) field in it.
>
> I understand that an index is created because of the comment shown in this
> code:
>
> https://github.com/django/django/blob/master/django/db/
> backends/postgresql_psycopg2/schema.py#L17
>
> but even though the index is suggested for LIKE queries using non C
> locales I would have thought the addition of db_index=False would have
> negated that.
>
> I feel that this is a bug. An index is not required by PostgreSQL on a
> unique constraint (it may be recommended but that is beside the point) and
> if I explicitly state db_index=False then the Django ORM should remove the
> index even though the index is recommended.
>
> Thoughts?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers  (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/django-developers/552DB881.1090006%40googlemail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Grace and Peace,
Tommy B.

I want to live like I know what I'm leaving.
--Switchfoot, "Awakening"

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAKfxM0LJNbT%2BWtBW0n%3DD9K3QxNjLas7H3t2ZpMWfuaxXh1uxbQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.