The three asterisks "***" indicate what's new since August 26.
Only EBFs for the three fully-supported versions of SQL Anywhere are shown here: 10.0.1, 11.0.1 and 12.0.1.
Current builds... HP-UX Itanium 11.0.1.2664 EBF 24 Aug 2011 10.0.1.3777 EBF 14 Oct 2008 HP-UX PA-RISC 10.0.1.3778 EBF 16 Oct 2008 IBM AIX 12.0.1 GA Upgrade from 12.0.0 15 Mar 2011 11.0.1.2637 EBF 26 Jul 2011 Linux Itanium 10.0.1.3777 EBF 14 Oct 2008 Linux x86/x64 12.0.1.3311 EBF 01 Apr 2011 11.0.1.2645 EBF 29 Jul 2011 10.0.1.4239 EBF 17 Jun 2011 Mac OS 12.0.1.3352 EBF 26 May 2011 11.0.1.2449 EBF 29 Jun 2010 10.0.1.4042 EBF 01 Oct 2010 NetWare 10.0.1.4036 EBF 10 Mar 2010 Solaris SPARC 12.0.1 GA Upgrade from 12.0.0 15 Mar 2011 11.0.1.2632 EBF 07 Jul 2011 10.0.1.4239 EBF 17 Jun 2011 Solaris x64 11.0.1.2645 EBF 05 Aug 2011 10.0.1.3870 EBF 01 Apr 2009 Windows CE 10.0.1.4036 EBF 09 Mar 2010 Windows Itanium 10.0.1 GA Upgrade from 10.0.0 26 Apr 2007 Windows x86/x64 12.0.1.3436 EBF *** 14 Sep 2011 *** 11.0.1.2661 EBF 22 Aug 2011 10.0.1.4239 EBF 17 Jun 2011
4 comments:
When will build 12.0.1.3436 be available for Linux?
We seem to have a problem that is fixed in the Windows build 3436, but for Linux no newer build than 3311 is available.
================(Build #3315 - Engineering Case #661791)================
A query containing a join between two or more tables could have returned
an incorrect result if the executed query plan used an Index-Only Scan of
some index T_idx over table T. For the problem to have occurred, a column
T.col must have participated in a non-equality join predicate (e.g. "T.col
< S.col", or "T.col BETWEEN S.col1 AND S.col2"), and there
must have existed one or more columns in index T_idx preceeding T.col that
did not participate in equality predicates. This has been fixed.
@J. Hendriks: I do not know when the next build for Linux will be posted. IMO six months is a very long time to wait for another EBF after this one:
Platform: Linux x86/Linux x64 SQL Anywhere - Express Bug Fix, Update of 12.0.1 to build 3311 12.0.1 01 Apr 2011 EBF/Patch
Try asking your question on http://sqlanywhere-forum.sybase.com/
OK, thanks!
Post a Comment