doc/bin_sequel.rdoc in sequel-4.3.0 vs doc/bin_sequel.rdoc in sequel-4.4.0
- old
+ new
@@ -22,11 +22,11 @@
sequel sqlite:/
sequel postgres://user:pass@host/database_name
sequel mysql2://user:pass@host/database_name
-See the {Connecting to a database guide}[link:files/doc/opening_databases_rdoc.html] for more details about and examples of connection strings.
+See the {Connecting to a database guide}[rdoc-ref:doc/opening_databases.rdoc] for more details about and examples of connection strings.
=== YAML Connection File
Instead of specifying the database connection using a connection string, you can provide the path to a YAML configuration file containing the connection information. This YAML file can contain a single options hash, or it can contain a nested hash, where the top-level hash uses environment keys with hash values for
each environment. Using the -e option with a yaml connection file, you can choose which environment to use if using a nested hash.
@@ -75,10 +75,10 @@
You can use the -M attribute to set the version to migrate to:
sequel -m /path/to/migrations/dir -M 3 postgres://host/database
-See the {migration guide}[link:files/doc/migration_rdoc.html] for more details about migrations.
+See the {migration guide}[rdoc-ref:doc/migration.rdoc] for more details about migrations.
=== Dump Schemas
Using the -d or -D options, Sequel will dump the database's schema in Sequel migration format to the standard output: