Roy,

<< Looks good generally. I was hoping that the erase .old's would make it
but I suppose that's what Windows Explorer is for >>

It's in there for the temporary tables, but not for regular tables in the
form of a NOBACKUP clause, etc.   It's a little dicier than with DBISAM
because EDB actually uses these files for restoration if there's an
exception.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mauro,

<< the optimize for 2' field-index is already present in 2.03 build zero ?
>>

No, that's part of the row value support, which didn't make it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> - Triggers can now be enabled and disabled on a per-session basis via the
> ENABLE TRIGGER and DISABLE TRIGGER SQL statements.  The status of a
> trigger can be queried via the Triggers Information schema table and the
> new Enabled column.

Thank you for this.  This will save me hours of work trying to figure out a
way to temporarily disable a delete trigger when purging old data.

--

---------------------------------------
 Terry Swiers
 Millennium Software, Inc.
 http://www.1000years.com
 http://www.atrex.com

 Atrex Inventory Control/POS -
    Big business features without spending big business bucks!

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------

Hi Tim,

Nice changes, especially these ones (although the others are appreciated
as well):

> - The EXECUTE IMMEDIATE SQL/PSM statement can now accept parameters via a
> USING clause.

> - SQL jobs, scripts, stored procedures, functions, and triggers can now
> declare and use arrays.

> - The START TRANSACTION SQL statement now includes a TIMEOUT clause that
> allows you to specify the total amount of time

> - All error messages now include a reference to the container object of the
> object that is the target of the error message.

Unfortunately this didn't make it in the 2.03 version: "Messaging layer
for general messaging notifications and broadcasts with the ElevateDB
server.". Hopefully it will be in the 2.04 version.

Don't get me wrong, I am not complaining - all changes are welcome and
the stability of EDB is top priority (at least for me) but none the less
I was hoping this feature would be in 2.03 (unless it is and I either
overlooked it or you forgot to mention it - wishful thinking here).

One question though about the catalog: what was exactly changed? I am
just curious. A short answer will do. And if it really technical, don't
answer it. Thanks.


Best regards,
Fons

Wow, what a list...

>>A SELECT statement containing sub-queries in the SELECT column expressions
>>can now return a sensitive result set

I really LOVE that one...

Thanks !!

Fons,

<< Unfortunately this didn't make it in the 2.03 version: "Messaging layer
for general messaging notifications and broadcasts with the ElevateDB
server.". Hopefully it will be in the 2.04 version. >>

Yes, that and the row value support are two of the big changes that need to
make it in ASAP after 2.03 is out.  We need the messaging for the more
recent OS's because we're going to use it for remote configuration of the
server.  I was going to wait on 2.03 to include these two items, but there
was a bug fix that required a call-level change for the C/S interface, and
that requires a minor version number change.

<< One question though about the catalog: what was exactly changed? I am
just curious. A short answer will do. >>

One change was to fix an obscure internal issue with word generator
references, and the others are "placeholders" for future items that will be
used with new features in 2.04 and up.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Thanks for the update and insight. Waiting patiently on 2.04 and as
always: don't rush it - stability is paramount!

Best regards,
Fons

Fons,

<< Thanks for the update and insight. Waiting patiently on 2.04 and as
always: don't rush it - stability is paramount! >>

Most definitely.  It's one of the reasons why 2.03 took so long.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim.  I have no idea how you manage to create what you have done.  I hope you list
of things to do is getting smaller.

>> Thank you for this.  This will save me hours of work trying to figure out a way to
temporarily disable a delete trigger when purging old data.

Terry,

If you do no want to wait to install 2.03, you can disable a trigger by setting the
condition to something like 0 <> 0.

Richard Harding.

Richard,

> If you do no want to wait to install 2.03, you can disable a trigger by
> setting the
> condition to something like 0 <> 0.

Thanks for the tip.  At this point, I'm still wrestling with some other self
imposed issues so I have plenty to do even if it takes another week for 2.03
to be released.   

--

---------------------------------------
 Terry Swiers
 Millennium Software, Inc.
 http://www.1000years.com
 http://www.atrex.com

 Atrex Inventory Control/POS -
    Big business features without spending big business bucks!

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------