Subject Re: [firebird-support] Re: FireBird 2: Max length of names for tables, fields, constraints, etc
Author Lester Caine
Nols Smit wrote:
> 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.

It is also the reason Oracle can't be used, but there is nothing
stopping the long names being brought under control. That is what we did
on bitweaver - along with renaming reserved words so that we did not
need to run double quoted. It's not the limitation that is the problem -
it's simply that no one will run a port with the shorter table and field
names?

--
Lester Caine - G8HFL
-----------------------------
L.S.Caine Electronic Services - http://home.lsces.co.uk
Model Engineers Digital Workshop -
http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Treasurer - Firebird Foundation Inc. - http://www.firebirdsql.org/index.php