This is primarily a patch release for 4.0. If you are using
Oratcl in any kind of long running daemon type code, I suggest
an upgrade.
Several memory leak conditions have been resolved with this release.
Snapshot of the ChangeLog
Version 4.1 August, 2002
- The 'oralob' and 'oralong' commands have been implemented in 'C'.
This will make those commands available in slave interps and in
other situations where the old tcl file sourcing was made difficult
due to auto_path idiosyncracies. The files 'oralob.tcl' and
'oralong.tcl' will persist in the library directory as a baseline
for the new 'oralob.c' and 'oralong.c' files which are created
from them.
- Fixed a bug in oraparse that prevented asynchronous
transactions from parsing properly with the supplied examples.
Thanks to Miguel Bagnon (bag...@safelayer.com) for the alert.
17-SEP-2002
- Added support for describing user defined types to Oracols and
Oradesc. Began work for a test suite file.
Thanks to Olly Stephens (ollyst...@sourceforge.net) for the patch.
- Changed a bogus error message in [orainfo server $lda].
- Added a 'status' option to 'orainfo' that returns the server status.
Example: orainfo status $lda
Returns 1 if server status is OCI_SERVER_NORMAL
Returns 0 if server status is OCI_SERVER_NOT_CONNECTED
This is useful for detected loss of server, due to crash or shutdown.
- Rebuilt Oratcl_ColAppend() to use a Tcl_DString instead of a
Tcl_Obj ** in the building of the -datavariable option result.
This eliminates a Tcl_Obj (24 byte) leak for each result column.
22-NOV-2002
- Added support for sysdba and sysoper connections to 'oralogon'
usage: oralogon sysdba
usage: oralogon sysoper
Thanks to Aleksey Kurbatov (akur...@borlas.ru) for the patch.
04-DEC-2002
- Fixed a bug in orasql that prevented the commit option from working
Thanks to Christian Traber (chri...@traber-net.de) for the alert.
12-DEC-2002
- Changed 'oralogon' to pay attention to the return code from
OCIInitialize. If the return code is not OCI_SUCCESS raise an error.
This will avoid a core dump if the ORACLE_HOME environment variable
is not set on a unix platform.
13-DEC-2002
- Corrected an incorrect word in the documentation, the man page
indicated a 'sqlcode' option to the oramsg command. The option
is really 'sqltype'
Thanks
Todd Helfter
--
Todd M. Helfter
Database Analyst/Programmer
Purdue University
t...@purdue.edu
Just a small issue:
I tried the oratcl4.1 win-binaries and had to get the msvcr70.dll.
Think it's only installed if you have MSVC7.
Is it possible to distribute the dll with the package?
Regards,
Christian
Hi Christian, Good suggestion.
Does anyone know what the legalities of redistributing this dll
are.
I don't want the MS police banging on my door. :)
Todd
There should be a REDIST.TXT file in your MSVC7 installation. It
contains the names of the files that are redistributable. Look if
msvcr70.dll is listed (it probably is).
Michael Schlenker
> In article <78d39ece.03012...@posting.google.com>,
> >I tried the oratcl4.1 win-binaries and had to get the msvcr70.dll.
> >Think it's only installed if you have MSVC7. Is it possible to
> >distribute the dll with the package?
t...@jumpgate.ics.purdue.edu (Todd M. Helfter) writes:
> Does anyone know what the legalities of redistributing this dll are.
IANAL. That DLL is part of VC++ AFAICS, it is the dynamic C/C++
runtime for VC++ 7.0, right. You should have a file called REDIST.TXT
or REDISTRB.WRI or similar somewhere in your VC++ installation, which
lists this file among others and also has a pointer to the
redistribution license terms.
If you don't own VC++ or some other Microsoft product that lists the
DLL as redistributable, you most likely have no license to
redistribute the DLL.
so long, benny
Visit INFO: Redistribution of the Shared C Runtime Component in Visual C++
.NET
http://support.microsoft.com/default.aspx?scid=kb;en-us;326922
for more info.
Chang
"Todd M. Helfter" <t...@jumpgate.ics.purdue.edu> wrote in message
news:b18m8a$ss5$1...@mozo.cc.purdue.edu...