comparison etc/NEWS @ 109460:597339bd6bef

SQL Mode V2.2 - Added sql-connect and sql-connection-alist
author Michael Mauger <mmaug@yahoo.com>
date Sun, 18 Jul 2010 14:44:32 -0400
parents 334eb7871775
children 91bbf4e4290f
comparison
equal deleted inserted replaced
109459:301190722b84 109460:597339bd6bef
40 --- 40 ---
41 ** There is a new configure option --with-crt-dir. 41 ** There is a new configure option --with-crt-dir.
42 This is only useful if your crt*.o files are in a non-standard location. 42 This is only useful if your crt*.o files are in a non-standard location.
43 43
44 --- 44 ---
45 ** Emacs can be compiled against Gtk+ 3.0 if you pass --with-x-toolkit=gtk3 45 ** Emacs can be compiled against Gtk+ 3.0 if you pass --with-x-toolkit=gtk3
46 to configure. Note that other libraries used by Emacs, RSVG and GConf, 46 to configure. Note that other libraries used by Emacs, RSVG and GConf,
47 also depend on Gtk+. You can disable them with --without-rsvg and 47 also depend on Gtk+. You can disable them with --without-rsvg and
48 --without-gconf. 48 --without-gconf.
49 49
50 ** There is a new configure option --enable-use-lisp-union-type. 50 ** There is a new configure option --enable-use-lisp-union-type.
254 For example, adding "(diff-mode . ((mode . whitespace)))" to your 254 For example, adding "(diff-mode . ((mode . whitespace)))" to your
255 .dir-locals.el file, will turn on `whitespace-mode' for *vc-diff* buffers. 255 .dir-locals.el file, will turn on `whitespace-mode' for *vc-diff* buffers.
256 256
257 ** SQL Mode enhancements. 257 ** SQL Mode enhancements.
258 258
259 *** Several variables have been marked as safe local variables. 259 *** Several variables have been marked as safe local variables. The
260 The variables `sql-product', `sql-user', `sql-server', and 260 variables `sql-product', `sql-user', `sql-server', `sql-database' and
261 `sql-database' can now be safely used as local variables. 261 `sql-port' can now be safely used as local variables.
262 262
263 *** Added ability to login with a port on MySQL. 263 *** Added ability to login with a port on MySQL.
264 The custom variable `sql-port' can be specified for connection to 264 The custom variable `sql-port' can be specified for connection to
265 MySQL servers. 265 MySQL servers.
266 266
267 *** Custom variables control prompting for login parameters. 267 *** Custom variables control prompting for login parameters.
268 Each supported product has a custom variable `sql-*-login-params' 268 Each supported product has a custom variable `sql-*-login-params'
269 which is a list of the parameters to be prompted for before a 269 which is a list of the parameters to be prompted for before a
270 connection is established. 270 connection is established.
271 271
272 *** Added `sql-connection-alist' to record login parameter values.
273 An alist for recording different username, database and server
274 values. If there are multiple databases that you connect to the
275 parameters needed can be stored in this alist.
276
277 For example, the following might be set in the user's init.el:
278
279 (setq sql-connection-alist
280 '((dev (sql-product 'sqlite)
281 (sql-database "/home/mmaug/dev.db"))
282 (prd (sql-product 'oracle)
283 (sql-user "mmaug")
284 (sql-database "iprd2a"))))
285
286 This defines two connections named "dev" and "prd".
287
288 *** Added `sql-connect' to use predefined connections.
289 Sets the login parameters based on the values in the
290 `sql-connection-alist' and start a SQL interactive session. Any
291 values specified in the connection will not be prompted for.
292
293 In the example above, if the user were to invoke M-x sql-connect, they
294 would be prompted for the connection. The user can respond with
295 either "dev" or "prd". The "dev" connection would connect to the
296 SQLite database without prompting; the "prd" connection would prompt
297 for the users password and then connect to the Oracle database.
298
272 *** Added option `sql-send-terminator'. 299 *** Added option `sql-send-terminator'.
273 When set makes sure that each command sent with `sql-send-*' commands 300 When set makes sure that each command sent with `sql-send-*' commands
274 are properly terminated and submitted to the SQL processor. 301 are properly terminated and submitted to the SQL processor.
275 302
276 *** Added option `sql-oracle-scan-on'. 303 *** Added option `sql-oracle-scan-on'.
277 When set commands sent to Oracle's SQL*Plus are scanned for strings 304 When set commands sent to Oracle's SQL*Plus are scanned for strings
278 starting with an ampersand and the user is asked for replacement 305 starting with an ampersand and the user is asked for replacement text.
279 text. In general, the SQL*Plus option SCAN should be set OFF under 306 In general, the SQL*Plus option SCAN should always be set OFF under
280 SQL interactive mode. 307 SQL interactive mode and this option used in its place.
281 308
282 *** SQL interactive mode will replace tabs with spaces. 309 *** SQL interactive mode will replace tabs with spaces.
283 This prevents the comand interpretter for MySQL and Postgres from 310 This prevents the comand interpretter for MySQL and Postgres from
284 listing object name completions when being sent text via 311 listing object name completions when being sent text via
285 `sql-send-*' functions. 312 `sql-send-*' functions.