Just a quick note to give everyone the status of 1.06.  I am finishing up
1.06 (finally) today, and then it will be approx. 1 day of builds and
testing and it will be ready.   The majority of the delays were due to
feature creep.  Things kept popping up that needed addressing, and this was
an ideal time to implement them.

This is the list of new features in 1.06:

SQL syntax highlighting in the EDB Manager, complete with customization of
font/colors,  F1 keyword-sensitive online help for SQL statements, full
search/replace/undo, and error highlighting.

New tabbed document interface in the EDB Manager with
File-Open/Re-Open/Close functionality for all SQL statements and scripts.

Improved keyboard handling for the EDB Manager, including F9 execution, F5
explorer refresh, and Insert/Delete explorer CREATE/DROP support.

SQL history in the EDB Manager for all DDL operations executed by the EDB
Manager in response to interface actions in the explorer.

SQL script support with new TEDBScript component and support for scripts in
the EDB Manager.  The scripts use the same syntax as the procedures,
functions, etc. in EDB so they can be used in either context and can use any
SQL/PSM functionality such as looping, branching, variables, exception
handling, etc.  However, scripts can access multiple databases (like jobs)
and are always executed in the context of the current user's effective
permissions.

ALTER support for all views, procedures, functions, jobs, databases,
indexes, tables, triggers, including ALTER
COLUMN AS and ALTER CONSTRAINT AS support for one-step alteration of columns
and constraints in an ALTER TABLE statement.

The is a new ServerSessionLocks table in the Configuration database that
contains information on all of the locks held by all sessions in an EDB
Server.  In combination with the ServerSessions table, this system table is
useful for querying whether a particular session is disconnected and has a
restrictive transaction or row lock that needs to be released.  Then an
administrator can use the REMOVE SERVER SESSION statement to remove the
offending session.

New TEDBEngine property called UseLocalSessionEngineSettings (default False)
that determines whether the engine settings for ConfigPath, ConfigExtension,
etc. are used with local sessions or whether the new TEDBSession
LocalConfigPath, LocalConfigExtension, etc. properties are used to override
the engine settings.  This applies only to local sessions, and is useful for
applications that use multiple sessions to access multiple application
configurations, such as the EDB Manager.

New ODBD Driver connection string attributes such as CONFIGPATH, CONFIGNAME,
etc. for specifying the configuration path and other settings for local
connections.

New ADO migrator module for migrating any ADO data source to an EDB
database.  Currently this module only supports migrating the tables,
indexes, and table data.  It does not support migrating the views or any
foreign key or check constraints.

Support for output parameters in SQL statements.  This is useful with INSERT
statements where you need to get the new value for an IDENTITY column after
the INSERT executes.

Support for SQL statement execution change detection.   If a
non-parameterized SQL statement is executed again, and the source tables
have not changed since the last execution, then EDB will simply return the
same result set immediately without any delay.  This is also true for any
Refresh calls for the TEDBQuery component, and applies to both sensitive and
insensitive result sets.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Wow !! Especially looking forward in testing the TEDBScript component. Also
the extended ALTER support is very welcome as is the ServerSessionLocks
table. Not that the rest is not interesting, but these are my favourites.
Still working on my SQL knowledge though, so the enhanced SQL editor is very
much appreciated.

Thanks you.

Best regards,
Fons

Excited to get the new release!  Are there any migration issues from 1.05?

Scott,

<< Excited to get the new release!  Are there any migration issues from
1.05? >>

The only thing that needs updating after installing 1.06 is the EDB Manager
settings for the configuration file path for each local session.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

You appear to be having a very long day of building and testing over
there <vbg>.

When 1.06 is out is there any planned order of completion (or time
scale) for the following:

1)   ADO driver

2)   RANGE (or LIMIT) in the SQL

Chris Holland

Chris


Personally I think Tim is using a Mercurian day

Roy Lambert

Chris,

<< You appear to be having a very long day of building and testing over
there <vbg>. >>

The documentation is taking a bit longer than expected, and my father had to
have surgery this week for an obstructed bowel (that whole affair started on
Monday).  Between the two, it's been a dismal week for getting it done.

<< When 1.06 is out is there any planned order of completion (or time scale)
for the following:

1) ADO driver
2) RANGE (or LIMIT) in the SQL >>

Both will be done at the same time, although the range/limit functionality
will not be SQL-based.  More than likely it will be handled in the
EDBDataReader class.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


Sympathy and best wishes to your father

Roy Lambert

Hi Tim,

Good health and wishes to your father.

Understandable that that takes priority.

BTW, I needed to google for obstructed bowel. Hope he is feeling better
soon.

Best regards,
Fons

Hi Tim,

Sorry to hear about your father, hope he recovers soon.

If the Range/Limit is not done via SQL, am I still going to have access
to this function via the ODBC/ADO drivers?

Chris Holland

Tim Young [Elevate Software] wrote:
> Chris,
>
> << You appear to be having a very long day of building and testing over
> there <vbg>. >>
>
> The documentation is taking a bit longer than expected, and my father had to
> have surgery this week for an obstructed bowel (that whole affair started on
> Monday).  Between the two, it's been a dismal week for getting it done.
>
> << When 1.06 is out is there any planned order of completion (or time scale)
> for the following:
>
>  1) ADO driver
> 2) RANGE (or LIMIT) in the SQL >>
>
> Both will be done at the same time, although the range/limit functionality
> will not be SQL-based.  More than likely it will be handled in the
> EDBDataReader class.
>