Siliconbits skrev:
> We are currently looking for Django developers to join us on a
> freelance basis.
>
> Location is irrelevant as long as you have a fast and reliable
> Internet access.
>
> You will be working from home, so you should be able to work
> independently, but also be able to demonst
Kenneth Gonsalves skrev:
> one thing I would like to see is: table of contents available on all
> pages. Now I have to go to 'documentation' and click on dbiapi. Then,
> if I want to go to 'creating models' I go back to 'documentation' and
> then to creating models. I bookmark these, but am
While looking through the db-backend settings, I found
autoindexes_primary_keys. This seems to be True for all other backends
than mysql and mysql_old.
The only place in the code that this is used is in
django/core/management/sql.py, where it is used to "manually" create
indexes for primary keys
Derek Anderson skrev:
> hey nis,
>
> 1) psycopg2 has been added as a backend
>
Any reason for not using my code (importing postgresql.py for both
backends) rather than having two source files which are identical?
Shouldn't we at least replace postgresql_pcycopg2.py with
from postgresql import
Derek Anderson skrev:
> Django External Schema Evolution Branch
> ===
> http://code.google.com/p/deseb/
>
> I've released v0.2, which supports both MySQL and Postgresql, and works
> with both django-head and django-v0.96.
>
> This release contains the introspec
PyMan skrev:
> Hi all :)
>
> I have the following problem.
>
> I have a function that do some get_or_create on model X giving as
> parameters the field Y and Z. The same function is running on
> different threads, so it can happen that more get_or_create on model X
> and fields Y/Z are called at t
on't like the transformation of strings into field values. How would
you compare a field value to a string?
I guess this means we have to keep referring to self.cleaned_data (and
not clean_data - see http://code.djangoproject.com/changeset/5231)
Apart from that, I am +1 on this (with the na
bh V
E: [EMAIL PROTECTED]
T: (+45) 30 74 66 68
Exact time to be announced, based on the wishes of the participants.
Coffee and (wireless) internet access will be provided.
Nis Jørgensen
No House IT
--~--~-~--~~~---~--~~
You received this message because you are sub
Adrian Holovaty skrev:
> It's about time we scheduled an official Django sprint. We've got a
> bunch of features that are almost done but haven't yet been
> committed/merged -- including newforms-admin, ORM aggregate support,
> multi-DB support and GeoDjango. Plus, we've got almost 1,000 open
> ti
The django documentation currently only mentions supported/recommended
versions for mySQL, not for the other databases.
I think it would be a good idea to have
- documentation of supported versions for all databases (including
shortcomings of the older versions) - similar to what is available fo
Michael Radziej skrev:
> Hi Adrian,
>
> the current behaviour is not a random implementation detail. It's been
> discussed
> in October 2006:
>
> http://groups.google.com/group/django-developers/browse_thread/thread/e36e80faf653b6d4/15fbf502162bc564?lnk=gst
>
Hmmm, It seems to me that reasonab
Carl Karsten skrev:
> I have the begging of something that may eventually get submitted, and
> looking
> for guidance as I build it.
>
> In the spirit of DRY, I have a nifty script that helps create the db defined
> in
> settings.py
>
[snip]
> I am thinking it would be nice if it was hung o
Malcolm Tredinnick skrev:
> On Thu, 2007-07-05 at 00:39 -0700, jedie wrote:
>
>> The documentation philosophy is relevant for me: The documentation
>> should really never show non-working examples.
>>
>
> Unsurprisingly, we are in 100% agreement. So if the documentation and
> the code are
13 matches
Mail list logo
