Re: Schema tests: delete_tables

Hi Russell, I understand what Maximiliano is asking. It's a flaw with SchemaTests.delete_tables [1] and it is essentially doing a raw drop table, instead of using the 3rd party backend friendly SchemaEditor.delete_model [2]. There was the last time I checked (and still exists) a lot of raw SQL in

Re: Schema tests: delete_tables

On Tue, May 20, 2014 at 7:07 AM, Maximiliano Robaina wrote: > Hi, > > Running tests, (I'm using firebird) in schema app, I see that the tearDown > method deletes all tables created by each test. The problem here is for > tables with AutoInc field where sequences are created

Re: inspectdb and non "public" schema in postgresql

On Tue, May 20, 2014 at 5:38 AM, Fabio C. Barrionuevo da Luz < bna...@gmail.com> wrote: > Hello Django core developers. > Sorry if this is not the correct place to handle this. > Not really - this mailing list is for discussing the development of Django itself, not for solving usage questions.

Re: #22383 Add the HTML5 required tag to the input fields which are required for database entry

Here is a more concrete proposal based on Loic's comment in the ticket: A normal deprecation cycle based on the value of a new ` use_required_attribute` boolean attribute on forms. To deprecate you could do: class form.Form(object): #... use_required_attribute = None class

Schema tests: delete_tables

Hi, Running tests, (I'm using firebird) in schema app, I see that the tearDown method deletes all tables created by each test. The problem here is for tables with AutoInc field where sequences are created independently, when the table is dropped we need delete the sequence object too. The, to

inspectdb and non "public" schema in postgresql

Hello Django core developers. Sorry if this is not the correct place to handle this. I have a legacy database in PostgreSQL, which is still in production. I want to migrate it to Django. I tried to do the reverse engineering of the database to generate models classes I set my settings like this:

Re: Database-dependant tests and third-party backends

DECIMAL datatype of DB2 also doesn't supports max_digits 38 and decimal_places = 30. In DB2 precision range defined between 1 to 31 and In firebird range is 1 to 18(ref http://www.promotic.eu/en/pmdoc/Subsystems/Db/FireBird/DataTypes.htm) It would be good if max_digits and decimal_places can

[GSOC] Weekly update

Hi All, Today I will be starting my weekly updates on my SoC project: refactoring Meta to a stable API. For anyone who missed out, you will be able to view it here: https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit This week is the first official week of

Re: Database-dependant tests and third-party backends

El miércoles, 7 de mayo de 2014 22:03:11 UTC-3, Russell Keith-Magee escribió: > > > On Thu, May 8, 2014 at 12:40 AM, Aymeric Augustin < > aymeric@polytechnique.org > wrote: > >> Hello, >> >> I'm trying to make the lives of maintainers of third-party database >> backends a bit easier. >> >

Re: Database-dependant tests and third-party backends

El miércoles, 7 de mayo de 2014 14:18:25 UTC-3, Shai Berger escribió: > > Hi, > > On Wednesday 07 May 2014 19:40:08 Aymeric Augustin wrote: > > > > I'm trying to make the lives of maintainers of third-party database > > backends a bit easier. > > > > +1. > > > > > *1) Checking database

Re: Database-dependant tests and third-party backends

I have created a ticket #22653 ( https://code.djangoproject.com/ticket/22653 ), for the issue I have mentioned. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an

Re: Release of 1.7 news for podcast?

Thank you thank you! It's a massive release so I for one would much rather be sure and confident than rushed. Thank you Tim and Andrew, and take care (I would recommend sunshine and sandy beaches ... bt ... ) Elena :) @elequ On Monday, May 19, 2014 4:57:59 AM UTC+8, Andrew Godwin wrote: