| 1 |
* Default sequence names for Oracle changed to #{table_name}_seq, |
|---|
| 2 |
which is the most commonly used standard. In addition, a new |
|---|
| 3 |
method ActiveRecord::Base#set_sequence_name allows the developer |
|---|
| 4 |
to set the sequence name per model. This is a |
|---|
| 5 |
non-backwards-compatible change -- anyone using the old-style |
|---|
| 6 |
"rails_sequence" will need to either create new sequences, or set: |
|---|
| 7 |
ActiveRecord::Base.set_sequence_name = "rails_sequence" |
|---|
| 8 |
|
|---|
| 9 |
* OCIAdapter now properly handles synonyms, which are commonly |
|---|
| 10 |
used to separate out the schema owner from the application user. |
|---|
| 11 |
|
|---|
| 12 |
* Fixed the handling of camelCase columns names in Oracle. |
|---|
| 13 |
|
|---|
| 14 |
* Implemented for OCI the Rakefile tasks of |
|---|
| 15 |
:clone_structure_to_test, :db_structure_dump, and |
|---|
| 16 |
:purge_test_database, which enable Oracle folks to enjoy all the |
|---|
| 17 |
agile goodness of Rails for testing. Note that the current |
|---|
| 18 |
implementation is fairly limited -- only tables and sequences are |
|---|
| 19 |
cloned, not constraints or indexes. A full clone in Oracle |
|---|
| 20 |
generally requires some manual effort, and is |
|---|
| 21 |
version-specific. Post 9i, Oracle recommends the use of the |
|---|
| 22 |
DBMS_METADATA package, though that approach requires editing of |
|---|
| 23 |
the physical characteristics generated. |
|---|
| 24 |
|
|---|
| 25 |
* Fixed the handling of multiple blob columns in Oracle if one or |
|---|
| 26 |
more of them are null. |
|---|
