Re: Multiple db branch: tests

On Fri, 2006-06-30 at 02:59 +, [EMAIL PROTECTED] wrote: > Malcolm, > > Thank you. You questions have actually answered a few of mine. For > those that are left, I'll try to clarify... > > > So wouldn't the analogous situation in your case be to also reserve > > django_test_a and django_test_

Re: Multiple db branch: tests

Malcolm, Thank you. You questions have actually answered a few of mine. For those that are left, I'll try to clarify... > So wouldn't the analogous situation in your case be to also reserve > django_test_a and django_test_b names as databases we will create in the > test framework and then use t

Re: Multiple db branch: tests

On Thu, 2006-06-29 at 14:40 +, [EMAIL PROTECTED] wrote: > Adrian Holovaty wrote: > > On 6/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Is it appropriate to have a test that requires sqlite, or should tests > > > always use the database engine(s) specified in settings? > > > > Test

Simple improvement to raw_id_admin

I have some objects that refer another class that currently has about 3000 instances, so the default drop-down menu for ForeignKey breaks down completely. I then found the raw_admin option, but this has a major weakness, it doesn't change the text describing the selected item when you pick a new,

Re: Unicodification of Django

Jacob Kaplan-Moss wrote: > On Jun 28, 2006, at 6:07 AM, Gábor Farkas wrote: >> what i think we are missing the most is to hear about the "main" >> developers (project owners?) (adrian, malcolm, jacob etc.) opinion >> about >> unicode-ification. if they think we should switch django completely to

Re: Multiple db branch: tests

Adrian Holovaty wrote: > On 6/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Is it appropriate to have a test that requires sqlite, or should tests > > always use the database engine(s) specified in settings? > > Tests should always use the database engines in settings. Ok. > > If they

Re: Request for history: incoming data processing

On Wed, 2006-06-28 at 14:15 -0500, Jacob Kaplan-Moss wrote: > On Jun 28, 2006, at 11:45 AM, Malcolm Tredinnick wrote: > > For things like applications/atomserv+xml and related ones (basically, > > everything else), data should be left unprocessed by the Django > > layers, > > I would have though