Re: oracle-django problem
Or use this, >From http://www.djangoproject.com/documentation/model-api/#table-names "To override the database table name, use the db_table parameter in class Meta." On Jun 9, 7:46 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Mon, Jun 9, 2008 at 6:43 AM, Harish <[EMAIL PROTECTED]> wrote: > > > hi friends > > > i have a django application, which works on postgres as back-end. > > now i want to migrate the application back-end from postgres to > > oracle. > > > The problem i am facing is that, the existing data table names in > > postgres is too long > > (basically the table name is a combination of application name and > > class name), which is not allowed > > in oracle. (using oracle 11g) Basically oracle only allows 30 > > character as table name. > > > I am looking forward for any solution to my problem > > It isn't clear if you are actually encountering a problem or just > anticipating one. I have no experience with Oracle, but it would seem that > the "naming issues" note here: > > http://www.djangoproject.com/documentation/databases/#naming-issues > > indicates that the developers of the Oracle support were aware of this issue > and dealt with it. Are you running into a problem with this method of > handling the Oracle limitation? > > Karen --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: oracle-django problem
On Mon, Jun 9, 2008 at 6:43 AM, Harish <[EMAIL PROTECTED]> wrote: > > hi friends > > i have a django application, which works on postgres as back-end. > now i want to migrate the application back-end from postgres to > oracle. > > The problem i am facing is that, the existing data table names in > postgres is too long > (basically the table name is a combination of application name and > class name), which is not allowed > in oracle. (using oracle 11g) Basically oracle only allows 30 > character as table name. > > I am looking forward for any solution to my problem > It isn't clear if you are actually encountering a problem or just anticipating one. I have no experience with Oracle, but it would seem that the "naming issues" note here: http://www.djangoproject.com/documentation/databases/#naming-issues indicates that the developers of the Oracle support were aware of this issue and dealt with it. Are you running into a problem with this method of handling the Oracle limitation? Karen --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
Re: oracle-django problem
why does it have to be that big?? what would be the problem of renaming the models?? On Tue, Jun 10, 2008 at 6:13 AM, Harish <[EMAIL PROTECTED]> wrote: > > hi friends > > i have a django application, which works on postgres as back-end. > now i want to migrate the application back-end from postgres to > oracle. > > The problem i am facing is that, the existing data table names in > postgres is too long > (basically the table name is a combination of application name and > class name), which is not allowed > in oracle. (using oracle 11g) Basically oracle only allows 30 > character as table name. > > I am looking forward for any solution to my problem > > > regards > Harish Bhat > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
oracle-django problem
hi friends i have a django application, which works on postgres as back-end. now i want to migrate the application back-end from postgres to oracle. The problem i am facing is that, the existing data table names in postgres is too long (basically the table name is a combination of application name and class name), which is not allowed in oracle. (using oracle 11g) Basically oracle only allows 30 character as table name. I am looking forward for any solution to my problem regards Harish Bhat --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~--~~~~--~~--~--~---
