Title: EOF ODBC Adaptor Patch (v 13.3)
Entry Number: 2477 Creation Date: October 17 1996
Last Updated: <<Date June 17, 1997>> Procedure Valid for Release: EOF 2.0
Keywords: EOF, OPENSTEP, WebObjects, Enterprise Objects, patch
Overview
This patch is version number 13.3. The ODBC Adaptor shipped with the EOF 2.0 release was version 13.1. You can find the version of the ODBC adaptor in the title of the ODBC Login panel.
Note: This patch is only for use with EOF 2.0 installed on Windows NT as part of OPENSTEP or WebObjects.
In order to install this patch, you will need to use gzip and gnutar to expand the attachment. You'll end up with a supplemental NextLibrary directory, which you can then copy into your existing NextLibrary directory. You need to log in as Administrator to install this patch.
Caution: The patch will replace \NextLibrary\Executables\ODBCEOAdaptor.dll and the entire \NextLibrary\Frameworks\ODBCEOAdaptor.framework directory, so you should take care to create a back up these items before installing over the top of them.
Assuming you have 2482_ODBCAdaptorPatch_NT_tar.gz on c:/tmp and are using the Bourne Shell provided by NeXT, here are the commands to install the patch:
$ cd $NEXT_ROOT
$ mv NextLibrary/Executables/ODBCEOAdaptor.dll NextLibrary/Executables/ODBCEOAdaptor.dll.bak
$ mv NextLibrary/Frameworks/ODBCEOAdaptor.framework NextLibrary/Frameworks/ODBCEOAdaptor.framework.bak
$ gzip -d -c c:/tmp/2482_ODBCAdaptorPatch_NT_tar.gz | gnutar -xvf -
EOF ODBC Adaptor Patch Release Notes
Problems Fixed in This Patch Update
The following problems have been fixed in this update:
ODBC EOAdaptor
References: 73072
Problems: Attempts to save EO's that use the custom value capability will fail. an example is using the Movies example application and adding an image to a Talent. When you attempt to save the change, you will get an error: "NSImage does not respond to selector length".
Fix: The ODBCByteColumn and ODBCLongByteColumn classes now have a corrected implementation of takeInputValue: that calls adaptorValueByConvertingAttributeValue: to correctly convert the custom value into a NSString or NSData for storage purposes. See the EOF 2.0 release notes for the corrected implementation.
References: 73239
Problems: Attempts to reverse engineer a model from an existing ODBC datasource will fail with a dialog with the following message: "An unexpected error has occured which may cause EOModeler to malfunction. You may want to save copies of your open documents and quit EOModeler. Error: invalid name"
Fix: During model reverse engineering, the ODBC method desribeModelForTableNames is more careful to create valid names for it's EOEntities and EOAttributes. The previous adaptor just used the table name or column name and these names aren't always valid names for model objects. Additionally, while generating SQL we now add quotes around names of tables and columns if they contain any characters that aren't letters of the alphabet.
References: 74252
Problems: Creating an EOModel from a Microsoft Access database that uses replication will leave the s_GUID, s_Generation, and s_Lineage columns even though these aren't useful.
Fix: The reverse engineering code now looks for this column in Access databases, and will remove them from the list of classProperties and attributesUsedForLocking. If you want these columns included in your model, just mark them as class properties and/or attributes used for locking.
![[Index]](http://enterprise.apple.com/NeXTanswers/images/index.gif)
![[Download]](http://enterprise.apple.com/NeXTanswers/images/Download.gif)
