+2013-01-09 Russ Tyndall <russ@acceleration.net>
+ sql/oodml.lisp - changed view-classes-and-storable-slots to a
+ method (as it was intended to be all along)
+
+2012-12-19 Kevin Rosenberg <kevin@rosenberg.net>
+ * Version 6.4
+
+2012-11-20 Russ Tyndall <russ@acceleration.net>
+ ## Large refactoring of sql/oodml.lisp and surrounding code
+ * cleaned up update-records-from-* to utilize a single codepath
+ previously there was much duplicate code
+ * tried to further unify direct/effective slot-defs
+ * cleaned up much of the normalized classes code to be more
+ consistent in how it operated, and the code it used (less
+ copy/paste more functions)
+ * tried to standardize iteration a bit, previously almost all
+ of the iteration constructs in CL were used. Tried to
+ standardize on loop for readability / cohesiveness
+ * made functions to more easily look up particular slots, since
+ this was being done differently in each function
+ * added more doc-strings and updated documentation about
+ normalized classes
+ * inner-joins that are referenced in where clauses are no longer
+ added to the select table list (since they are also referenced
+ in the join position and this led to sql errors)
+ * collect-table-references methods added for sql-ident-table and
+ list
+
+ ## Semantic changes
+ * disallow where-less updates from objects (ie cannot call
+ update-records-from* with a keyless object)
+ * ordered-class-direct-slots now returns direct-slot-definitions
+ instead of effective-slot-definitions (as per name)
+ * direct-slot-definitions now contain the db-info hash table (same
+ as effective slots)
+ * removed this-class arg from update-instance-from-records - used to
+ be used for normalized code, no longer needed for that.
+ * find-all - bug fixes in table references, previously where clauses
+ surrounded by a list would have none of their references added to
+ the select. This was being exploited by certain code paths. Now
+ all where clauses are searched
+ - No longer includes order-by and distinct as columns in the select
+ list. The values seemed to be ignored in every code path and distinct
+ seemed to be intended to be used as a boolean anyway
+
+
+2012-11-20 Nathan Bird <nathan@acceleration.net>
+
+ * update-objects-joins - changed the default of slot from t (which
+ used to mean :deferred) to :immediate (to match the default
+ behavior of other parts of the system). It also seemed like a bad
+ default to pull all the slots that were explicitly specified to be
+ not pulled by default. This function now accepts more special
+ values (:immediate, :deferred, :all, or a list of slots). To get
+ the old behavior call with :slots :deferred.
+
+
+2012-10-30 Russ Tyndall <russ@acceleration.net>
+ * sql/command-object.lisp - added dates/times to the parameter value
+ coersion and pulled this into a new generic prepare-sql-parameter
+
+2012-09-04 Kevin Rosenberg <kevin@rosenberg.net>
+ * Version 6.3 released
+
+2012-09-04 Russ Tyndall <russ@acceleration.net>
+ * sql/expressions.lisp - Try to respect the casing of symbols
+ where it seems intentional (ie: is not default). This should fix
+ a failing test case, and I think behaves more understandibly.
+
+ If you specify a casing '|Foo Bar| lets treat that a string "Foo Bar"
+ and output it escaped
+
+2012-08-28 Ryan Davis <ryan@acceleration.net>
+ * db-sqlite3/sqlite3-api.lisp - allow pathnames in the connection
+ settings, so '("/db/my.sqlite") and '(#P"/db/my.sqlite") are
+ equivalent. Updated the docs to match.
+
+2012-08-17 Russ Tyndall <russ@acceleration.net>
+ * db-postgresql-socket3/package.lisp - shadow
+ postgresql-notification for compatibility with new
+ cl-postgres (Thanks Zach)
+
+2012-07-09 Russ Tyndall <russ@acceleration.net>
+ * sql/oodml.lisp - fixed a bug where the order by was being
+ destructively modified, causing odd caching issues when the
+ selected object was not statically known (eg unreferenced tables
+ could show up in the query if they were cached by a previous call
+ through this function. I replaced this code with a
+ non-destructive variant which should solve this.
+
+ Thanks to Philipp Marek for the bug report
+
+2012-06-25 Russ Tyndall <russ@acceleration.net>
+ * sql/util.lisp, sql/metaclasses.lisp
+ Dequote database-identifiers if needed (passed a quoted symbol)
+ Metaclass args come through unquoted, so this eases interactions
+ with them
+
+2012-06-22 Russ Tyndall <russ@acceleration.net>
+ * sql/metaclasses.lisp: Changed compute-effective-slot-definition
+ to correctly copy the autoincrement-sequence slot to the ESD
+ previously it was being skipped (seemingly by accident). Thanks
+ to flip214 on #lisp for the bug report
+
+2012-04-26 Kevin Rosenberg <kevin@rosenberg.net>
+ * Version 6.2 released: thanks to all the contributors!
+
+2012-04-25 Nathan Bird <nathan@acceleration.net>
+
+ * doc/threading-warnings.txt: Adding some notes from J.T.Klein
+ about the current state of thread-safety in clsql. This should be
+ incorporated into the main docs at some point.
+
+2012-04-25 Russ Tyndall <russ@acceleration.net>
+ * sql/expressions.lisp (output-sql): on rendering update/insert
+ expression values, ensure that *in-subselect* is bound to T
+ so that the values will be correctly paren delimited
+
+2012-04-24 Nathan Bird <nathan@acceleration.net>
+
+ * sql/expressions.lisp (output-sql): on mysql CREATE TABLE
+ statements use 'ENGINE=innodb' instead of 'Type=InnoDB'. This has
+ apparently been preferred since mysql 4.1 and mysql 5.5 removed
+ type as a valid keyword.
+
+2012-03-28 Russ Tyndall <russ@acceleration.net>
+
+ * sql/sequences.lisp: [A Patch FROM 2011-07-28 changed sequences.
+ They were previously prefixed with _CLSQL_SEQ_ but are now
+ suffixed with _CLSQL_SEQ. This is likely to break existing
+ implementations using the default sequence names
+
+ setting *old-sequence-names* to T, should force using the older
+ naming scheme
+
+2012-03-27 Ryan Davis <ryan@acceleration.net>
+
+ * sql/expressions.lisp: Fixed bug with subqueries in the where
+ clause of update-records and delete-records generating invalid
+ SQL. Previously subselects in where clauses would not have enough
+ parentheses, for example: "WHERE Id IN SELECT foo_id FROM bar"
+ vs. "WHERE Id IN (SELECT foo_id FROM bar)"
+ * tests/test-syntax.lisp: Added tests for using subqueries in the
+ where clause in update-records and delete-records. Moved asserts
+ in the test-output-sql/sql-ident-table function into the standard
+ test framework.
+ * doc/appendix.xml: added :connection-string to the information on
+ ODBC connection specs, and added example code connecting to ODBC
+ databases.
+
+2012-01-05 Nathan Bird <nathan@acceleration.net>
+
+ * db-odbc/odbc-dbi.lisp: handle sql decimal type in the same way
+ as numeric type-- read into a double float.
+
+2011-01-04 Russ Tyndall <russ@acceleration.net>
+ * sql/operations.lisp
+
+ Fixed bug reported by JTK related to the not-null sql-expression
+ especially as used in conjunction with the is operator.
+
+ Made null called with more than one argument throw an exception
+ instead of silently discarding all arguments past the first
+
+2012-01-04 Nathan Bird <nathan@acceleration.net>
+
+ * db-odbc/odbc-api.lisp (%sql-driver-connect): in the call to
+ odbc's SQLDriverConnect default the WindowHandle argument to a null ptr so
+ that connecting with :connection-string will work in the default
+ case of SQL_DRIVER_NOPROMPT.
+
+ I.e. you can now do things like:
+ (clsql:connect '("DsnName" "UserName" "" :connection-string
+ "DRIVER={FreeTDS};SERVER=...;DATABASE=...;UID=...;PWD=...;PORT=1433;TDS_Version=8.0;APP=clsql")
+ :database-type :odbc)
+
+ I believe the DsnName and Username at that point are only used when
+ printing the connection information.
+
+2011-12-20 Kevin Rosenberg <kevin@rosenberg.net>
+ * Version 6.1.1
+ * db-oracle/oracle.lisp: Typo correction (Elias Martenson)
+
+2011-12-19 Kevin Rosenberg <kevin@rosenberg.net>
+ * Version 6.1.0
+ * db-oracle/oracle.lisp: Change length function to
+ uffi:foreign-string-length to handle foreign encodings.
+ Thanks to Elias Martenson.
+
+2011-11-28 Russ Tyndall <russ@acceleration.net>
+ * db-odbc/odbc-api.lisp, tests/test-time.lisp
+
+ In ODBC backend, avoid going through the common lisp
+ universal-time type (because it lacks support for historic dates)
+
+ *time-conversion-function* renamed to *time-format*
+
+ Patch from: Francisco Vides Fernandez
+
+2011-10-18 Russ Tyndall <russ@acceleration.net>
+ * db-odbc/odbc-api.lisp
+
+ Added type specifier so MSSQL nvarchar fields can make it through
+
+2011-09-12 Russ Tyndall <russ@acceleration.net>
+ * sql/fddl.lisp sql/generic-postgres.lisp db-mysql/mysql-sql.lisp
+ sql/generic-odbc.lisp sql/odbc-api.lisp sql/odbc-dbi.lisp
+
+ Fix bugs in list-attribute(s|-types) where passing an escaped,
+ instead of unescaped column name, caused these functions to return
+ less data than they should have.
+
2011-08-03 Kevin Rosenberg <kevin@rosenberg.net>
* CLSQL 6.0.0 released
* test/: Better, more tests, better type coercion in tests and
throughout (%get-int)
+ [edit 2012-03-28 - RT]
+ * sql/sequences.lisp: Sequences were previously prefixed with
+ _CLSQL_SEQ_ but are now suffixed with _CLSQL_SEQ. This is likely
+ to break existing implementations using the default sequence names
+
+ setting *old-sequence-names* to T, should force using the older
+ naming scheme
+
2011-07-16 Kevin Rosenberg <kevin@rosenberg.net>
* Version 5.4.0 release
projects / clsql.git / blobdiff