Subject | Re: FireBird 2: Max length of names for tables, fields, constraints, etc |
---|---|
Author | Nols Smit |
Post date | 2006-11-22T08:03:03Z |
Thanks for the replies. The reason why I'm asked the question:
I stumbled across Django (http://www.djangoproject.com/).
Django was developed at World Online, the Web department of a newspaper in Lawrence, Kansas, USA.
Quoted from their FAQS (http://www.djangoproject.com/documentation/faq/)
"World Online has been using Django for more than three years. Sites built on Django have weathered traffic spikes of over one million hits an hour and a number of Slashdottings. Yes, it's quite stable."
But it seems it's bounded to the build-in SQLite 3, PostgreSQL and MySQL (where's my pack of Valoid).
According to this posting (http://code.djangoproject.com/ticket/1261), the max. length of 31 chars for table names, etc. is the problem why FireBird can't be used.
Regards,
Nols Smit
Disclaimer Legal Notice:
By having opened and read this electronic mail, you are deemed to have
understood and accepted all disclaimers and conditions pertaining to
electronic mail emanating from, and received by The Council for Geoscience,
further detail of which may be viewed at the following hyperlink:
http://www.geoscience.org.za/disclaimer.htm
[Non-text portions of this message have been removed]
I stumbled across Django (http://www.djangoproject.com/).
Django was developed at World Online, the Web department of a newspaper in Lawrence, Kansas, USA.
Quoted from their FAQS (http://www.djangoproject.com/documentation/faq/)
"World Online has been using Django for more than three years. Sites built on Django have weathered traffic spikes of over one million hits an hour and a number of Slashdottings. Yes, it's quite stable."
But it seems it's bounded to the build-in SQLite 3, PostgreSQL and MySQL (where's my pack of Valoid).
According to this posting (http://code.djangoproject.com/ticket/1261), the max. length of 31 chars for table names, etc. is the problem why FireBird can't be used.
Regards,
Nols Smit
Disclaimer Legal Notice:
By having opened and read this electronic mail, you are deemed to have
understood and accepted all disclaimers and conditions pertaining to
electronic mail emanating from, and received by The Council for Geoscience,
further detail of which may be viewed at the following hyperlink:
http://www.geoscience.org.za/disclaimer.htm
[Non-text portions of this message have been removed]