In Firebird-Architect@yahoogroups.com,
Jim Starkey <jas@n...> wrote:

> 1. Two level name space (aka schemas)

i.e. separate dbs? Scott.emp and scott.hr?
Potential to cross query different dbs?

Or does that have something to do with
catalogues that Martijn mentioned? (Please
excuse ignorance).

> 2. Long identifiers (128 characters)

Makes sense though mind you, a wee bit of
thought doesn't make life too difficult, but
then I'm sure that BG said that about 8.3.

8-)

> 3. UTF-8 only ODS

Argument seems very strong here - only one
of the posters was talking about Cyrillic
not working properly. An optional mechanism
for backward compatibility to be included?
A bit like the move to dialect 3?


<Snip arguments in favour of above ideas.
No debate from me>


Now, my wish list. I'm suggesting this as a
humble user of db, not as someone who has
a sufficient knowledge of C++ to be able
to programme any of it.

------------------------------------------
1) And should have a *_high_* priority.


Take a look here

http://blogs.teamb.com/
craigstuntz/articles/
IBPerformanceMonitoring.aspx

I believe that if FB is to have any cred
as a serious contender in middle/heavy-middle
division of the entreprise db world, then
good, decent instrumentation *_must_* be
implemented.

Being able to kill long running queries.
Being able to assign a Qry_Max_Time after
which the query will automatically be
killed by the system.

A whole host of the other features listed
on the blog above. There's a reason why
Oracle is the world's leading db - yes
you have 3 gazillion parameters, but you
can diagnose problems.

Obviously the more sophisticated features
would/could be set to inactive, but those
who knew what they needed to know could
get that information. I also appreciate that
there's a balance to be struck, and that FB/IB
market themselves as db-free systems. There
has been some talk on one of the lists about
having a "Standard" and "Entreprise" version.
Maybe our Entreprise version could have a
whole truckload of parameters which are given
reasonable defaults for most apps in "Standard"?
----------------

---------------------
2. Also quite important.

Move the code base to 1 (preferably the gcc)
compiler. Having an Open Source project
that relies on a Microsoft compiler does little
for "street cred". It might also help lead to
2.5 which is support for the BSD's <insert
your favourite OS here>. Could also help
encourage some fresh blood in the programming
area?

I do also appreciate that a significant effort
is underway to unify the code base, and have no
more "Classic" or "Superserver", just something
that will work anywhere. That should extend to
the compiler being used.
---------------------------

---------------------------
3. Not sure here. Would a write-ahead log
give (some) users more confidence? Would it allow
for PITR?
----------------------------

----------------------------
4. Maybe a system to be able to specify
different index types for different sorts
of data - a l'Oracle?
-----------------------------

-----------------------------
5. Geographic data types. PostgreSQL
is way ahead here.
-----------------------------


OK, there it is - if I think up of anything
else, I'll post it. In any case, keep up
the good work.

Rgs.


Paul...

> Jim Starkey