360e602c5b6fc7f1fcfab73982323b4b6e9193d1 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/233af21b248e819265c8eb5e754d70c0954ec1ad 233af21b248e819265c8eb5e754d70c0954ec1ad

2008-09-03T11:58:21-07:00

Bump version to 2.5.0 21bfe3cd2763c655a0bc4f417f85f68a77902bf2 Jeremy Evans code@jeremyevans.net ec6619ef704e0097a183e825e3c2ed2c04a1cdb1 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/360e602c5b6fc7f1fcfab73982323b4b6e9193d1 360e602c5b6fc7f1fcfab73982323b4b6e9193d1

2008-09-02T12:24:39-07:00

Add set_defaults! and set_overrides! Dataset mutation methods e18099a90cf781b2e1d2c6eda63bfaf7510e16df Jeremy Evans code@jeremyevans.net 7350715293092a04645376b2d9e82a382e5c5cb0 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/ec6619ef704e0097a183e825e3c2ed2c04a1cdb1 ec6619ef704e0097a183e825e3c2ed2c04a1cdb1

2008-08-28T14:03:23-07:00

Add Dataset #set_defaults and #set_overrides, used for scoping the values used in insert/update statements Sequel has long been known for its chainable filters. Before this commit, it was not possible to chain the values used in insert or update statements. This commit adds two methods, with slightly different features, to accomplish this. set_defaults is used to set the default values used in insert or update statements, which can be overriden by the values passed to insert or update: DB[:t].set_defaults(:x=>1).insert_sql # => INSERT INTO t (x) VALUES (1) DB[:t].set_defaults(:x=>1).insert_sql(:x=>2) # => INSERT INTO t (x) VALUES (2) DB[:t].set_defaults(:x=>1).insert_sql(:y=>2) # => INSERT INTO t (x, y) VALUES (1, 2) set_overrides is used to set default values that override the values given to insert or update statements: DB[:t].set_overrides(:x=>1).insert_sql(:x=>2) # => INSERT INTO t (x) VALUES (1) In addition, chaining calls to set_default and set_overrides operate slightly differently: DB[:t].set_defaults(:x=>1).set_defaults(:x=>2).insert_sql # => INSERT INTO t (x) VALUES (2) DB[:t].set_overrides(:x=>1).set_overrides(:x=>2).insert_sql # => INSERT INTO t (x) VALUES (1) As show above, with set_default, the last call takes precedence, whereas with set_overrides, the first call takes precedence. Note that set_defaults and set_overrides only are used when insert or update is called with a hash. Dataset#insert had to go through some significant refactoring for this to work. All the specs still pass, so hopefully nothing broke because of it. 0c788c300024a1b6845a8a5321c5d5be77743868 Jeremy Evans code@jeremyevans.net 6acb504cd1ae8842b7b65270cecb73cad2fb31c4 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/7350715293092a04645376b2d9e82a382e5c5cb0 7350715293092a04645376b2d9e82a382e5c5cb0

2008-08-28T11:42:24-07:00

Allow Models to use the RETURNING clause when inserting records on PostgreSQL This commit makes model.save! check for an insert_select method on the dataset. If it exists, it calls that method and uses the result as the values, instead of inserting and then reloading the values from the database. This should be faster as well as less error prone. It changes a recent commit to the PostgreSQL adapter so that insert_sql does not use the RETURNING clause by default. You need to call the insert_returning_sql method if you want the RETURNING clause. That is what Dataset#insert now does on PostgreSQL servers 8.2 and higher. This caused some issues with prepared statements, but this commit takes care of that as well. This commit also contains a small speedup to Dataset#single_value, as well as a missing spec for Database#raise_error. 047b64334656734b1f3fd7e2272096ada83d8474 Jeremy Evans code@jeremyevans.net 80c2c9e537aaa98000867b393d4fe9eb326396c7 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/6acb504cd1ae8842b7b65270cecb73cad2fb31c4 6acb504cd1ae8842b7b65270cecb73cad2fb31c4

2008-08-27T15:51:32-07:00

Raise Sequel::DatabaseError instead of generic Sequel::Error for database errors, don't swallow tracebacks This commit adds a new exception class, Sequel::DatabaseError. This exception class should be used for all errors that come from the database, such as invalid syntax in a query or database access rights violation. This commit adds a couple private Database methods, raise_error and transaction_error. raise_error converts the exception to a DatabaseError, keeping the previous exception message (prepended with the previous exception class) as well as the traceback. If an optional :classes option is passed, it only converts the exception if it is one of those classes. transaction_error calls raise_error with the :classes options set to the array of passed classes, unless the error is an Error::Rollback. These DRY up some code in the adapters. This commit also removes the convert_pgerror method for the postgres adapter, since it is no longer necessary. This is a backwards incompatible change for SQLite users, since the SQLite adapter previously raised Error::InvalidStatement instead of just Error. cffbef6325cd7d5eaa42e32f35b8865faef60b32 Jeremy Evans code@jeremyevans.net 5a2bd738ab9ced38fa91620768f9a0dae2c99134 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/80c2c9e537aaa98000867b393d4fe9eb326396c7 80c2c9e537aaa98000867b393d4fe9eb326396c7

2008-08-27T13:39:13-07:00

2008-08-27T13:05:12-07:00

Use INSERT ... RETURNING ... with PostgreSQL 8.2 and higher This makes the PostgreSQL adapter use INSERT ... RETURNING ... if it is connected to an 8.2.0 or later server. This should provide a performance boost, as it doesn't require extra queries being issued to determine the value of the inserted primary key. This also makes the Database object clear the cache for @primary_keys and @primary_key_sequences when drop_table is called. It adds a Database#primary_key public method for determining the primary key for a given table. If also adds a Dataset#server_version private method to make things more testable. fb14d1e43976d43943d2cde6124e8d8d5859df5e Jeremy Evans code@jeremyevans.net 2cc47d290dbdf8f380e37252c9e651a3115de2d5 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/5a2bd738ab9ced38fa91620768f9a0dae2c99134 5a2bd738ab9ced38fa91620768f9a0dae2c99134

2008-08-27T11:51:31-07:00

Document general but adapter specific return values for fetch_rows, delete, insert, and update 349edf786f17d21706c419738d9ff1b9a98cbc1e Jeremy Evans code@jeremyevans.net aa48478575089d3e3c2f31594ffa0b6bb282dac7 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/2cc47d290dbdf8f380e37252c9e651a3115de2d5 2cc47d290dbdf8f380e37252c9e651a3115de2d5

2008-08-27T11:42:37-07:00

Make insert_sql, delete_sql, and update_sql respect the :sql option Before this commit, all of the following would raise errors: DB["INSERT INTO blah (id) VALUES (1)"].insert_sql DB["DELETE FROM blah"].delete_sql DB["UPDATE blah SET num = 1"].update_sql Now, these just return the SQL given. This implies: ds = DB["..."] ds.update_sql.should == ds.delete_sql 426d125a1794613ccb6435c09deeefb8939c6edc Jeremy Evans code@jeremyevans.net 61ba0d19e9483f83ceae774f7d1e70fed8ab2a39 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/aa48478575089d3e3c2f31594ffa0b6bb282dac7 aa48478575089d3e3c2f31594ffa0b6bb282dac7

2008-08-27T11:03:07-07:00

2008-08-27T10:43:48-07:00

Default to converting 2 digit years Before, Sequel would treat 06/07/08 as being in the year 0008 instead of 2008, at least when using the Date and DateTime classes. This commit changes that so that 2 digit years are treated as year + 1900 if year >= 69 or year + 2000 if year < 69. To get back the old behavior: Sequel.convert_two_digit_years = false If you are using ruby 1.9, you should watch out, as the date parsing differs from ruby 1.8: Date.parse('01/02/08', true).to_s # ruby 1.8 => "2008-01-02" Date.parse('01/02/08', true).to_s # ruby 1.9 => "2001-02-08" 9499417fba4822ac605803c2d22c4ff765124483 Jeremy Evans code@jeremyevans.net cb2ab0e8d3f32446b16f17a6fb11904a558a27b0 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/61ba0d19e9483f83ceae774f7d1e70fed8ab2a39 61ba0d19e9483f83ceae774f7d1e70fed8ab2a39

2008-08-26T16:08:40-07:00

Make the PostgreSQL adapter with the pg driver use async_exec, so it doesn't block the entire interpreter 566aee3bc7c3b2eddb29d113c0821d75ed87f7d4 Jeremy Evans code@jeremyevans.net 140035bc9c8b11af61fd3a6bb8efebc70f09f72f Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/cb2ab0e8d3f32446b16f17a6fb11904a558a27b0 cb2ab0e8d3f32446b16f17a6fb11904a558a27b0

2008-08-26T16:03:54-07:00

Make jarredholman's composite key schema patch usable on Ruby 1.9 065bc3d0b213572c9e9325e4c975833cda65cf34 Jeremy Evans code@jeremyevans.net 5323c2bb642a705db74949300a227742b1f24ba6 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/140035bc9c8b11af61fd3a6bb8efebc70f09f72f 140035bc9c8b11af61fd3a6bb8efebc70f09f72f

2008-08-25T17:00:43-07:00

Fix use of shared MSSQL adapter by the ODBC and ADO adapters ee532fb53632863946b839b66375e253afaa05c9 Jeremy Evans code@jeremyevans.net 0330d82e3fc28b208d671b6a71bf8e86e373cac7 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/5323c2bb642a705db74949300a227742b1f24ba6 5323c2bb642a705db74949300a227742b1f24ba6

2008-08-24T12:13:20-07:00

Better error messages for invalid String#to_{date,time,datetime} conversions b7607b799aa9bb492368573321e8de12646aa436 Jeremy Evans code@jeremyevans.net 32f6a46d5082e3b232fade5559e83ad351d536c0 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/0330d82e3fc28b208d671b6a71bf8e86e373cac7 0330d82e3fc28b208d671b6a71bf8e86e373cac7

2008-08-24T12:11:54-07:00

Update CHANGELOG for jarredholman's recently added schema generator features f801ea34f312d600fa4c6b33493ccd81018128d1 Jeremy Evans code@jeremyevans.net 919c47a6655517d9232c6c02b74ecd13d21fafb3 Jarred Holman jarred.holman@gmail.com http://github.com/jeremyevans/sequel/commit/32f6a46d5082e3b232fade5559e83ad351d536c0 32f6a46d5082e3b232fade5559e83ad351d536c0

2008-08-22T15:06:39-07:00

Fixed validate_uniqueness_of to assign the error message to the correct field. bac30424f096d33ae5d16129aa6026264852104f Jarred Holman jarred.holman@gmail.com 7ae2be4240df17b76991b3957cfe1ad66e828bcb Jarred Holman jarred.holman@gmail.com http://github.com/jeremyevans/sequel/commit/919c47a6655517d9232c6c02b74ecd13d21fafb3 919c47a6655517d9232c6c02b74ecd13d21fafb3

2008-08-22T13:46:50-07:00

Added support for composite primary key, composite foreign key and unique constraints to Schema::Generator and Schema::AlterTableGenerator 2f107e8717a510b579a7df435098ed93c3a97cd1 Jarred Holman jarred.holman@gmail.com 35e692145144bd3d28c7d577317334dee24b98d3 Jarred Holman jarred.holman@gmail.com http://github.com/jeremyevans/sequel/commit/7ae2be4240df17b76991b3957cfe1ad66e828bcb 7ae2be4240df17b76991b3957cfe1ad66e828bcb

2008-08-21T18:58:13-07:00

Allow creation of tables with composite primary keys eb79b1ee68770c264984c081ecfadde4ebce9089 Jarred Holman jarred.holman@gmail.com aa0e9e8ca23100d8fead81f9f2d6cde5afc4885a Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/35e692145144bd3d28c7d577317334dee24b98d3 35e692145144bd3d28c7d577317334dee24b98d3

2008-08-20T08:03:18-07:00

Work with the 2008.08.17 version of the pg gem 239f82a3baf54ee5fe9725de40ea2b36e5674573 Jeremy Evans code@jeremyevans.net c64dda9b6b7df1c932f0ab24b524b0b4f23d1903 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/aa0e9e8ca23100d8fead81f9f2d6cde5afc4885a aa0e9e8ca23100d8fead81f9f2d6cde5afc4885a

2008-08-19T13:04:54-07:00

Disallow abuse of SQL function syntax for types (use :type=>:varchar, :size=>255 instead of :type=>:varchar[255]) This commit also refactors type_literal to return the entire literal value for the type, instead of just the base type (so it includes any length and/or UNSIGNED specifiers). It also makes type_literal private. In addition, this fixes an issue with renaming or changing the type of a varchar column on MySQL, if you wanted the size to be different than 255. 6a9181e554042d1d0546def71daa4b39e51b396f Jeremy Evans code@jeremyevans.net 2ec2acd4d685d6834b130802000b1f5dd58da7d9 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/c64dda9b6b7df1c932f0ab24b524b0b4f23d1903 c64dda9b6b7df1c932f0ab24b524b0b4f23d1903

2008-08-18T09:47:28-07:00

2008-08-18T09:42:06-07:00

Quote index names when creating or dropping indexes This also refactors some schema creation methods. It quotes tables and columns as well as indexes in the schema creation methods that the MySQL adapter overrides. It adds a couple new methods, drop_index_sql and column_references_sql, which eliminates some duplication in the MySQL adapter. 9d47db28dfee145b56eb4af25f476e1718e44120 Jeremy Evans code@jeremyevans.net c7a70c0138be15a7d78b10cd94d37fd4f4fcd864 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/2ec2acd4d685d6834b130802000b1f5dd58da7d9 2ec2acd4d685d6834b130802000b1f5dd58da7d9

2008-08-16T14:06:39-07:00

Update some RDoc comments in sequel_model/schema.rb ce5bbcc62280219daeb10069fde5235457094d45 Jeremy Evans code@jeremyevans.net 04a0dff5e8db8123dad782d3c68e57e3c039167a Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/c7a70c0138be15a7d78b10cd94d37fd4f4fcd864 c7a70c0138be15a7d78b10cd94d37fd4f4fcd864

2008-08-13T12:23:38-07:00

Don't have column accessor methods override plugin instance methods This commit changes where the column accessor methods are defined. Instead of defining them directly in the class, this defines them in an anonymous module that is included in the class. Because columns accessors are generally defined when the class is created (before the plugin has been added), the plugin instance methods module will be included after the column accessor module, so it will take precedence. Because the column accessor methods don't override existing instance methods, if a plugin has already been added, using set_dataset after a plugin has been added (e.g. in a subclass) won't create column accessors that override the plugin's instance methods. This commit should also have a minor speedup in the general case, by recognizing when a dataset is inherited and omitting some redundent code in that case. While here, simplify the code for Sequel::Model(). 01a8964d421e86f2f1bd9ca329389ee003250f32 Jeremy Evans code@jeremyevans.net 1cb84f39cc418f9916cd6737895585960990348d Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/04a0dff5e8db8123dad782d3c68e57e3c039167a 04a0dff5e8db8123dad782d3c68e57e3c039167a

2008-08-13T10:56:19-07:00

Allow validation of multiple attributes at once, with built in support for uniqueness checking of multiple columns This commit allows you to support validating multiple attributes at once: validates_each([:column1, :column2]) do |obj, attributes, values| # attributes = [:column1, :column2] # values = [obj.send(:column1), obj.send(:column2)] end Support was added to validates_uniqueness_of to work on multiple values at once: validates_uniqueness_of([:column1, :column2]) This is quite different from the following code: validates_uniqueness_of(:column1, :column2) Which makes sure the each value is unique to its column, instead of the combination of values being unique. This will give a validation error message if an entry already exists in the database that has the same value for column1 and column2. It works for any number of columns. validates_uniqueness_of now supports an :allow_nil option that will skip checking if the values of all columns are nil. Previously, it automatically skipped the validation if the value was blank. There was also a slight memory reduction by reusing the default proc if :if is not specified. bb9c5ab3a422347c60fc8d321de65c45b8ddce46 Jeremy Evans code@jeremyevans.net 40b75585ed513766b07cbb22264dd8b4fb81854f Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/1cb84f39cc418f9916cd6737895585960990348d 1cb84f39cc418f9916cd6737895585960990348d

2008-08-12T16:55:11-07:00

In PostgreSQL adapter, fix inserting a row with a primary key value inside a transaction This bug took quite a while to find and fix. It was compounded by the fact that there were multiple bugs in the underlying implementation: 1) Errors raised by PostgreSQL weren't getting reraised inside insert_result. 2) Determining the sequence names was not done correctly. This caused weird errors, such as the code raising an error stating there was already an error on the transaction, without showing an error or even that a query was issued. To fix this and similar issues, have the connection log the SQL it issues to find primary keys, sequences, and sequence values, just like the Database object logs the SQL. To make sure that inserting a row with a primary key value works inside transactions, figure out the primary key first and see if it contained in the values hash. If not, figure out what the sequence is for the table, and get the last sequence value used. This is done because trying to get the last sequence value first if the sequence wasn't yet used on the connection causes PostgreSQL to abort the transaction. It would return an invalid result instead of aborting the transaction if the connection had previously been used to insert a row into the same table, without an easy way to detect things. Fix the SQL used for finding primary keys and sequences so that unnecessary columns aren't returned. Keep track of sequences at the Database level instead of the connection level. Make insert_result, primary_key_for_table, and primary_key_sequence_for_table private methods. The :table option when inserting is now unquoted (generally a symbol), instead of the quoted string used previously. ef36244ae44d163d6484b2bd12187be7dadede48 Jeremy Evans code@jeremyevans.net 725011da06b3cbdd091873757560c9db9ae8e0fa Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/40b75585ed513766b07cbb22264dd8b4fb81854f 40b75585ed513766b07cbb22264dd8b4fb81854f

2008-08-12T16:53:26-07:00

Small ruby 1.9 spec compatibility fix 19fc99998eafc322a4244f8797e1975422624f7e Jeremy Evans code@jeremyevans.net 545e2e42a2443070ac0b617b1012fdf80b53f956 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/725011da06b3cbdd091873757560c9db9ae8e0fa 725011da06b3cbdd091873757560c9db9ae8e0fa

2008-08-11T15:47:05-07:00

Allow :join_table association option to have a string value Before, using a string value would result in very weird error messages, because of the implementation of the many_to_many add_/remove_/remove_all_ methods. Have those methods use database.dataset.from(join_table) instead of database[join_table], which should work. The documentation will remain the same, and I don't guarantee that using a string will work in future versions. The main reason for this commit is so if you do use a string, you won't get an error message that doesn't make sense. 07e80182b508d74cb5533c897a97b0464f3ecb17 Jeremy Evans code@jeremyevans.net 2ea38a89b10a0de41bc0e0aef68cd29bc4782751 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/545e2e42a2443070ac0b617b1012fdf80b53f956 545e2e42a2443070ac0b617b1012fdf80b53f956

2008-08-07T13:20:42-07:00

Allow before_save and before_update to affect the columns saved by save_changes c94c27a04347a202a6be564ad5a1f72f5f8385db Jeremy Evans code@jeremyevans.net a815637364b680721c9f5156d786887d55e03c08 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/2ea38a89b10a0de41bc0e0aef68cd29bc4782751 2ea38a89b10a0de41bc0e0aef68cd29bc4782751

2008-08-06T16:03:35-07:00

Make Dataset#single_value work when graphing, which fixes count and paginate on graphed datasets 89248f52d5dda3b98a32e1d97b1a192e835e0362 Jeremy Evans code@jeremyevans.net 8e4f911ab5380a0630423ff1198a10f960662fdd Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/a815637364b680721c9f5156d786887d55e03c08 a815637364b680721c9f5156d786887d55e03c08

2008-08-06T09:52:41-07:00

Bump version to 2.4.0 edddca1d1f619f506adc8e8f8e2b742b102fc159 Jeremy Evans code@jeremyevans.net 2142f0a0f152f11b94944985ecb060ddc6cc0660 Jeremy Evans code@jeremyevans.net http://github.com/jeremyevans/sequel/commit/8e4f911ab5380a0630423ff1198a10f960662fdd 8e4f911ab5380a0630423ff1198a10f960662fdd

2008-08-06T09:28:08-07:00

Remove the generated html files when cleaning 0a0d52163a29b2fbc1c613d7c40d2539c8093307 Jeremy Evans code@jeremyevans.net