unordained wrote:

>Yes. But you won't like it. I didn't want to tie the concept of making Firebird support user-
>defined types directly to whatever type system I would prefer. That would make it far too easy to
>kill the proposal immediately. Architects may agree in principle, but disagree on how far they
>should take it -- I'm happy to take whatever I can get.
>
>
>

Here's what you need to do. First, write a problem description
explaining what you need to do that you can't with the existing system.
Second, you need to write a draft requirments document. There will be
much haggling over the requirements, but ultimately they will be judged
against the problem statement. In all likelihood, the problem statement
will be amended. Then you or somebody else needs to develop a specific
proposal. If the project catches our imagination, we might get a couple
of competing proposals. The proposal should address the extensions
required to meet the agreed requirements, any impact on backward
compatiblity, and sketch an implementation.