mirror of
				https://github.com/asterisk/asterisk.git
				synced 2025-10-31 02:37:10 +00:00 
			
		
		
		
	Correct typos of the following word families: password excludes undesirable checksums through screening interpreting database causes initiation member busydetect defined severely throughput recognized counter require indefinitely accounts ASTERISK-29714 Change-Id: Ie8f2a7b274a162dd627ee6a2165f5e8a3876527e
		
			
				
	
	
		
			25 lines
		
	
	
		
			1.0 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			25 lines
		
	
	
		
			1.0 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| ; Configuration file for the MYSQL app addon
 | |
| 
 | |
| [general]
 | |
| ;
 | |
| ; Nullvalue governs how NULL values are returned from the database.  In
 | |
| ; previous versions, the special NULL value was returned as the "NULL"
 | |
| ; string.  We now provide an option for the behavior, configured globally.
 | |
| ; nullstring  - the string "NULL"
 | |
| ; emptystring - the string ""
 | |
| ; null        - unset the variable
 | |
| ;
 | |
| ; WARNING: setting nullvalue=null may have undesirable consequences, in
 | |
| ; particular if you use subroutines in AEL or the LOCAL() variable construct.
 | |
| ; You have been warned.  Don't complain if you use that setting in combination
 | |
| ; with Gosub or AEL and get buggy behavior.
 | |
| ;
 | |
| nullvalue = nullstring
 | |
| 
 | |
| ; If set, autoclear will destroy allocated statement and connection resources
 | |
| ; when the channel ends.  For most usage of the MYSQL app, this is what you
 | |
| ; want, but it's conceivable that somebody is sharing MYSQL connections across
 | |
| ; multiple channels, in which case, this should be set to 'no'.  Defaults to
 | |
| ; 'no', as this was the original behavior.
 | |
| autoclear=yes
 |