Frank Schönheit - Sun Microsystems Germany schrieb:
Hi Regina,
(feedback to a spec! I love communities :)
First: Nothing of this is nailed down. There are other ways to implement
this (at least in a "solution compatible way"), so I highly appreciate
every feedback.
Well ... you won't like this argueing ;) ... because people keep
screaming for queries in queries. Of course we could simply make views
editable (which in fact is what is internally going in), but even then,
I'm pretty sure a lot of MSA users will keep saying "I want queries in
queries, MSA has it". Even if you tell them they can do the very same
thing by creating a view, and editing it if necessary, they will continue.
You judge me right. Doing it the same way as Access is no argument to
me. Access has been developed about ten years ago. Shouldn't we better
in the meantime? Of cause we must help Access users, but not by
?twisting (verbiegen) our product, but by leading them to the better
way. And I believe Access users are not too stupid to learn.
That's basically the main idea behind the proposed architecture.
However, as said, this is not nailed down, so keep your arguments coming :)
Here are my arguments against turning queries to views:
(1) It has unwanted consequences concerning the embedded HSQL database:
Up to now views are readonly, so you cannot alter your data out of a
view, which on the other hand is possible out of a query. So you will
loose functionality unless you implement, to write a record out of the view.
(2) It is not necessary for the embedded HSQL database:
(2a) You can use views to nest your statements.
(2b) You can already use queries in queries by nested selects like
SELECT ... FROM (SELECT ...) ...
You can set the query to “not parse” and it will work. The HSQL database
is capable of queries in queries, but the parser prevents you from using
it. Therefore you can get the feature, if you change the parser.
(3) The way cannot be transfered to other database systems, because
(3a) they might not know views like older MySQL or flat tables.
(3b) the user might not have the right to create a view, but has only
the read right and perhaps update right on the table.
(3c) Views are stored in the database system which might be on a server,
to which the user has no write access, but queries are stored in the
odb-file and therefore are possible for each user.
kind regards
Regina
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
