mirror of
				https://github.com/asterisk/asterisk.git
				synced 2025-10-31 02:37:10 +00:00 
			
		
		
		
	Added a new boolean configuration flag -
`order_multi_row_results_by_initial_column` - to both res_pgsql.conf
and res_config_odbc.conf that allows the administrator to disable the
explicit `ORDER BY` that was previously being added to all generated
SQL statements that returned multiple rows.
Fixes: #179
(cherry picked from commit 0bb192831c)
		
	
		
			
				
	
	
		
			37 lines
		
	
	
		
			1.3 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			37 lines
		
	
	
		
			1.3 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| ;
 | |
| ; Sample configuration for res_config_pgsql
 | |
| ;
 | |
| ; The value of dbhost may be either a hostname or an IP address.
 | |
| ; If dbhost is commented out or the string "localhost", a connection
 | |
| ; to the local host is assumed and dbsock is used instead of TCP/IP
 | |
| ; to connect to the server.
 | |
| ;
 | |
| [general]
 | |
| dbhost=127.0.0.1
 | |
| dbport=5432
 | |
| dbname=asterisk
 | |
| dbuser=asterisk
 | |
| dbpass=password
 | |
| ;dbappname=asterisk    ; Postgres application_name support (optional). Whitespace not allowed.
 | |
| ;
 | |
| ; dbsock is specified as the directory where the socket file may be found. The
 | |
| ; actual socket is constructed as a combination of dbsock and dbport.  For
 | |
| ; example, the values of '/tmp' and '5432', respectively, will specify a socket
 | |
| ; file of '/tmp/.s.PGSQL.5432'.
 | |
| ;
 | |
| ;dbsock=/tmp
 | |
| ;
 | |
| ; requirements - At startup, each realtime family will make requirements
 | |
| ; on the backend.  There are several strategies for handling requirements:
 | |
| ; warn        - Warn if the required column does not exist.
 | |
| ; createclose - Create columns as close to the requirements as possible.
 | |
| ; createchar  - Create char columns only
 | |
| ;
 | |
| requirements=warn
 | |
| 
 | |
| ; When multiple rows are requested by realtime, res_config_pgsql will add an
 | |
| ; explicit ORDER BY clause to the generated SELECT statement. To prevent
 | |
| ; that from occuring, set order_multi_row_results_by_initial_column to 'no'.
 | |
| ;
 | |
| ;order_multi_row_results_by_initial_column=no
 |