Tim,

This may have been answered previously.

Are you going to base, loosely or strictly, ElevateDB on the newer SQL99
standard?

Lance

Lance,

<< Are you going to base, loosely or strictly, ElevateDB on the newer SQL99
standard? >>

You'd have to define "loosely" and "strictly".  ElevateDB is based upon
the 2003 standard, but there are gaps in the implementation in certain
areas.  These gaps will be documented in the final product.

--
Tim Young
Elevate Software
www.elevatesoft.com

That makes sense.

I noticed that Nexus has some wording with their reference to SQL-2003.

Sounds along the same lines (with a better DB  

"NexusDB V2 implements a large subset of the international standard
ISO/IEC 9075 - SQL:2003, including most of the Core SQL functionality as
well as many of the additional features defined in the standard. In
addition, NexusDB augments SQL:2003 with extensions to expose
vendor-specific functionality.

While NexusDB does not claim official conformance to Core SQL, the
grammar conforms closely to the syntax and processing rules defined in
SQL:2003. Any difference between NexusDB SQL and SQL:2003 is documented
in the Conformance summary at the bottom of each topic page. "

Lance


Tim Young [Elevate Software] wrote:
> Lance,
>
> << Are you going to base, loosely or strictly, ElevateDB on the newer SQL99
> standard? >>
>
> You'd have to define "loosely" and "strictly".  ElevateDB is based upon
> the 2003 standard, but there are gaps in the implementation in certain
> areas.  These gaps will be documented in the final product.
>

Lance,

<< I noticed that Nexus has some wording with their reference to SQL-2003.
>>

I don't know what you're hinting at by coping NexusDB reference material
here, but as the author of the NexusDB v2 SQL Reference, I can tell you that
NexusDB SQL is exactly what it claims - a very compliant implementation of
SQL:2003. To my knowledge, no RDBMS is as far to SQL:2003 Core SQL
compliance as NexusDB v2 is currently. I don't know what ElevatDB brings,
but DBISAM SQL is certainly far from it.

Ole Willy Tuv

<< To my knowledge, no RDBMS is as far to SQL:2003 Core SQL compliance as
NexusDB v2 is currently. >>

Typo, should read:

To my knowledge, no RDBMS is as close to SQL:2003 Core SQL compliance as
NexusDB v2 is currently.

Ole Willy Tuv

</sarcasm on>

Flash Filer v?, uh, I mean NexusDB v1 IMO is also far from being
SQL:2003 compliant, since we're comparing our competitor's previous
versions with our current versions. And what is "very compliant"? Is it
compliant or not? Anyway, from what I gather on the Nexus newsgroups,
the v2 that appears to be in beta still, at least from an operational
point of view, is far from the v2 that was promised IMO.

SQL:2003 or the love of pure SQL for SQL's sake is not the mythological
adventure we all care to undertake. In fact, what most of us are doing
is creating real world apps that customers buy from us, so that we can
pay the bills. DBISAM fits that bill perfectly for me and my apps; it
has that perfect blend of features and price that give the most value.

We can't all join the monastery and become SQL monks, forsaking all that
is not pure SQL. There is a reason that M$, Oracle, Sybase, IBM, etc.
don't yet claim SQL:2003 conformance--maybe they don't yet consider it
as making a significant difference in the way their customers use their
RDBMS.

That's my story and I'm sticking to it

</sarcasm off>

~J. Lee

Ole Willy Tuv wrote:


>I don't know what ElevatDB brings,
> but DBISAM SQL is certainly far from it.
>
> Ole Willy Tuv
>
>

J

Do you want to join my "we have null" campaign?

Roy Lambert

Roy


Damn my fingers that should have read "we hate null"

Roy Lambert

Roy Lambert <roy.lambert@skynet.co.uk> wrote on Tue, 14 Mar 2006 08:00:17 +0000

>J
>
>Do you want to join my "we have null" campaign?
>
>Roy Lambert
>

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message news:58DBB7DC-C976-4E93-90F8-72CA932D7ED0@news.elevatesoft.com...
> Roy
>
>
> Damn my fingers that should have read "we hate null"
>
> Roy Lambert
>
> Roy Lambert <roy.lambert@skynet.co.uk> wrote on Tue, 14 Mar 2006 08:00:17 +0000
>
>>J
>>
>>Do you want to join my "we have null" campaign?
>>
>>Roy Lambert
>>
>

Roy

as a 30 year veteran mainframe dinosaur head in the sand type guy
I used to hate nulls as well but then I slowly came to realise
that real value of null.  Null indicates that no value has been
assigned to the variable this is different to space for alpha or 0 for numeric
and just what value would you put in for boolean?

This attribute is valuable especially when gathering marketing information

gregF

Ole,

<< I don't know what you're hinting at by coping NexusDB reference material
here, but as the author of the NexusDB v2 SQL Reference, I can tell you that
NexusDB SQL is exactly what it claims - a very compliant implementation of
SQL:2003. To my knowledge, no RDBMS is as far to SQL:2003 Core SQL
compliance as NexusDB v2 is currently. I don't know what ElevatDB brings,
but DBISAM SQL is certainly far from it. >>

No one said that DBISAM was, Ole.

On a related note:

I tolerate your postings on these newsgroups out of a sense of intellectual
discussion, but your postings are starting to push things.  These newsgroups
are for support purposes for existing customers *that actively use DBISAM*
and need help with something.  When you post messages here that aren't for
that purpose, you waste my time and the time of other customers.  This isn't
your personal place to come and stir things up by evangelizing on the
conformance or non-conformance of our SQL implementation.  If you have a
support question, then feel free to post any message that you like.  But if
you do not, then refrain from posting or keep it in the General Discussion
newsgroup.

--
Tim Young
Elevate Software
www.elevatesoft.com