Re: selecting app for syncdb

2013-05-22 Thread Michał Nowotka
I don't and I won't (south is not working with Oracle). -- 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 email to django-developers+unsubscr...@googlegroups.com. To

selecting app for syncdb

2013-05-22 Thread Michał Nowotka
Hello, Is the any particular reason why syncdb doesn't have argument with list of applications to be synced? -- 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 email

[no subject]

2013-05-02 Thread Michał Nowotka
I'm sorry for crossposting this question but my emails are somehow ignored on django-users list... According to that webpage: http://www.techempower.com/benchmarks/#section=data-r4 django performance is really bad comparing to other popular web frameworks. Are there any plans to change this

db_type method for ForeignKey is buggy?

2013-01-28 Thread Michał Nowotka
Hello django developers! This is db_type method definition: def db_type(self, connection): rel_field = self.rel.get_related_field() if (isinstance(rel_field, AutoField) or (not connection.features.related_fields_match_type and

Status of bug #11580 ?

2012-11-06 Thread Michał Nowotka
Hello, There is a bug submitted 3 years ago: https://code.djangoproject.com/ticket/11580 I have exact the same problem using django 1.4. Are there any plans to fix that in near future? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To

Re: Django produce sql with table name different then specified in meta db_table

2012-10-31 Thread Michał Nowotka
I think you mixed many things here. First of all db_table = 'schema_name\".\"table_name' is a well known hack to make django support Oracle multiple schemas. So this is not a bug, but it would be nice if we have better solution. As the consequence of this hack django treats the hole db_table

Re: Django produce sql with table name different then specified in meta db_table

2012-10-31 Thread Michał Nowotka
Another thing - this name is not truncated - some junk is appended and not after 30 characters but earlier and only for some table names regardless of length. I suppose this is a bug in django oracle backend and that's why I'm writing it here. -- You received this message because you are

Re: Django produce sql with table name different then specified in meta db_table

2012-10-31 Thread Michał Nowotka
I would understand truncating but please take a look: class DefinedDailyDose(models.Model): #... class Meta: db_table = u'mnowotka\".\"defined_daily_dose' managed=False where the name is even longer DefinedDailyDose.objects.exists() gives: SELECT * FROM (SELECT ROWNUM AS

Django produce sql with table name different then specified in meta db_table

2012-10-31 Thread Michał Nowotka
Hello, I'm using django 1.4 with oracle backend In my models.py I have: class ProteinTherapeutics(models.Model): #... class Meta: db_table = 'mnowotka\".\"protein_therapeutics' managed=False And this: ProteinTherapeutics.objects.exists() produces this SQL: SELECT * FROM

Possible bug in django oracle backend - no way to map from model type to oracle NUMBER type.

2012-10-17 Thread Michał Nowotka
Currently I'm working with some oracle legacy db which I would like to access using django ORM. I have a column of type NUMERIC (without precision and scale) and all possible values are kept there (for example, 65, 2.3, 0.5) After running inspectdb django suggested that this column