 |
 |
 |
I've been a bit busy to contribute, but I think a comment derived from
long years of experience is probably called for.
First, I have done what you propose - designed AND implemented an
advanced database system. It's semantic (relational plus some
significant meta data).
I have to agree with Richard and Len on their points. In particular you
don't know what the gotchas will be. It took me 10 years to get a a very
good implementation and another 10 years to get a stable implementation
- even though the syntax looks simple enough. It's the edge cases that
get you - anyone doing this sort of thing will I'm sure concur. The next
10 years for me have been taken up with folding new technologies such as
browsers, javascript, etc into the product.
Don't call it SQL - it's simply not.
And finally I'm not convinced the syntax you propose actually adds
anything. There is a one to one translation into SQL and most database
programmers would do the translation in their head every day.
I don't want to discourage creative thinking, but you will need to tread
a well worn road. Get a customer, build a first pass (alpha) version,
put it into the field. If it's any good it will start to get a life of
it's own - and you'll make a good living along the way. If it gets
really popular it will define a new standard. Remember that like many
other standards, SQL wasn't alone as a way to do relational database
systems - it was just the evolutionary survivor. It's not necessarily
the best way to do things (QUEL was arguably better), but it was the one
that worked best for most people.
Regards
Rick
Dmitry Turin wrote:
> Richard,
>
> RS> your design might have a flaw that can only be found during implementation.
> Speculatively
>
> RS> I don't think you've actually TAKEN a single bit of the advice
> Advice is (in order of following) to not bring different syntax,
> to separate from existing databases, to fear (look first quotation).
>
> RS> Good luck with your effort to standardize your one-person,
> RS> confusingly-named, unimplemented language
> Dictionary is long, continue.
>
>
> Dmitry Turin
> SQL5 (5.5.0) http://sql50.euro.ru
> HTML6 (6.4.3) http://html60.euro.ru
> Unicode7 (7.2.0) http://unicode70.euro.ru
> Computer2 (2.0.2) http://computer20.euro.ru
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l...
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |