[baseten-users] BaseTen 1.7 nearing completion
Tuukka Norri
tuukka.norri at karppinen.fi
Thu May 28 21:29:00 EEST 2009
Hi!
Work on BaseTen 1.7 is nearly completed. However, instead of just
promoting the newest SVN revision to 1.7, we'd like to ask you to test
your applications with it. Current candidate is rev. 1292, but in case
bugs are found, we'll naturally fix them. As usual, prebuilt disk
images are available at http://basetenframework.org/autobuilds/
Here are release notes since version 1.6.2. We've also done some work
on the manual, so please refer to it for more information.
BaseTen
– New features and major changes
– Time types are now handled.
– Dates are now assigned UTC or converted to it.
– NSDates are now converted to date strings using NSCalendar instead
of NSCalendarDate.
– Dates with time zones are now returned as NSDates.
– Dates are now stored into the database in UTC.
– The XML data type will now be fetched as NSXMLDocument in case the
column also has a constraint like CHECK(column IS DOCUMENT).
– Bit and varbit fields are now be fetched as NSStrings, because they
can't easily be represented as octets. Fetching them probably
didn't work earlier.
– Text fetched from the database will now be normalized to NFD.
– Instead of storing relationship etc. information with references
to PostgreSQL oids, BaseTen's own identifiers are now used. This
prevents table and view renaming after having them BaseTen enabled,
but allows making backups much more easily.
– To-many-relationships named after the target relation have now the
word “Set” appended to their names. The old names still work. If
you want to find the places in your code that use deprecated names,
add a symbolic breakpoint to BXDeprecationWarning.
– In case of one-to-many and one-to-one relationships, the inverse
relationship's name can now be stored into the foreign key.
– Some related objects or their IDs can now be specified in the value
dictionary when calling
-[BXDatabaseContext createObjectForEntity:withFieldValues:error:].
– Sending locking queries has now been thoroughly documented and can
be (almost) completely disabled.
– Added more SSL status codes. Now situations where SSL is unavailable,
automatic SSL certificate verification fails, user clicks cancel in
certificate trust panel and some other SSL error occurs can be
distinguished from each other.
– More BaseTen's internals have now been documented in the reference
manual.
– Bug fixes and minor changes
– Non-bytea columns will no longer be tried to be unescaped.
– Fixed potential garbage collection -related bugs where objects'
internal pointers were used.
– Changed KVO notification sending during -setPrimitiveValue:forKey:
so that willChange methods are guaranteed to be called before the
update.
– Changed references from NSCountedSet to NSMutableSet in BXSetProxies.
We still create NSCountedSets but their countability property isn't
currently in use.
– Some connection error messages are now more accurate.
– Documented BXDatabaseObjectID as thread-safe since it only
uses NSURL.
BaseTenAppKit
– BaseTenAppKit now has the Interface Builder plug-in embedded.
Interface
Builder loads the plug-in if the framework has been added to a
project.
– Fixed a crasher which occurred when connecting to a server with SSL
capability in asynchronous mode. Moved the code into a method which
both
the connectors use, so it can be tested easily.
– BXSynchronizedArrayController's property fetchesOnConnect is now
called
fetchesAutomatically. If it's set, a fetch will be performed also
when
an already-connected database context is assigned to the array
controller.
– Made sure that BXNetServiceConnector doesn't show an alert panel when
the user clicks cancel in the trust panel.
– Clicking Cancel in the trust panel displays the connection panel
again,
like when clicking cancel in the authentication panel.
BaseTen Assistant
– Relationships are now listed in the Inspector and info windows.
– A graphical representation of the database schema can now be created
for
use with Graphviz or OmniGraffle.
– Temporary information can now be deleted from BaseTen schema.
– Optional relationships should now be created as optional.
– Columns will no longer be created for transient attributes in data
models.
– Help is now more comprehensive.
--
Best regards,
Tuukka Norri
MK&C
More information about the baseten-users
mailing list