Re: AUTOCOMMIT. displaying and setting
Hi Yes, you can set the variabe per-connection. mysql > set SESSION autocommit=0; Check with two connections. For Transaction safe engines(such as InnoDB, BDB, or NDB Cluster),to disable autocommit mode for a single series of statements, use the START TRANSACTION or BEGIN statement. With START TRANSACTION, autocommit remains disabled until you end the transaction with COMMIT or ROLLBACK. The autocommit mode then reverts to its previous state once transaction done. Thanks ViSolve DB Team. - Original Message - From: "Amit Dor-Shifer" <[EMAIL PROTECTED]> To: "Visolve DB Team" <[EMAIL PROTECTED]> Cc: Sent: Wednesday, November 22, 2006 10:59 AM Subject: Re: AUTOCOMMIT. displaying and setting > Thanks! > I played a bit init_connect. I'm not sure though how can I verify the > autocommit value. You say 'by select'. Something like this? > > select @@AUTOCOMMIT; > > Because that still gives me a value of '1'. > > More important to me: Can this variable be set per-connection? If so, > how? Specifically, how do I set it for a none-console connection (e.g. > my previously mentioned jdbc connection)? > > BTW: > # mysql --version > mysql Ver 14.7 Distrib 4.1.21, for pc-linux-gnu (i686) using readline 5.1 > > Amit > > Visolve DB Team wrote: >> There is no global system variable to set Autocommit; but we can >> achieve the >> same with 'init_connect=SET AUTOCOMMIT=0'. >> This variable can be set from the mysql or in the commandline or in the >> option file. >> Like, >> mysql > SET GLOBAL init_connect='SET AUTOCOMMIT=0'; >> or >> mysql>SET @@GLOBAL.init_connect='SET AUTOCOMMIT=0'; >> >> or in the option file >> [mysqld] >> init_connect='set AUTOCOMMIT=0' >> or >> shell> mysqld --init_connect='set AUTOCOMMIT=0' >> By default AUTOCOMMIT is enabled. ie set to 1. If set to 0, then >> disabled. >> check with 2 connections; try inserting or updating in one connection; >> check >> in the other with select. >> >> This variable was added in MySQL 4.1.2. >> >> >> - Original Message - From: "Amit Dor-Shifer" <[EMAIL PROTECTED]> >> To: >> Sent: Tuesday, November 21, 2006 4:41 PM >> Subject: AUTOCOMMIT. displaying and setting >> >> >>> Hi. >>> >>> I'm puzzled rgd. a/m. Is AUTOCOMMIT a variable? If so, is it a session >>> variable? Should it show up when issuing a "SHOW VARIABLES" command? >>> >>> How do I set this variable when initalizing a jdbc connection? Can I >>> pass it on the connection URL? Can someone present a code line for this? >>> >>> How do I set this variable for an interactive console session? Can i do >>> this from the command line? When I attempt this I get: >>> # mysql -p --autocommit=0; >>> mysql: unknown variable 'autocommit=0' >>> >>> >>> Thanks, >>> Amit >>> >>> -- >>> MySQL General Mailing List >>> For list archives: http://lists.mysql.com/mysql >>> To unsubscribe: >>> http://lists.mysql.com/[EMAIL PROTECTED] >>> >> > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] >
Re: AUTOCOMMIT. displaying and setting
Thanks! I played a bit init_connect. I'm not sure though how can I verify the autocommit value. You say 'by select'. Something like this? select @@AUTOCOMMIT; Because that still gives me a value of '1'. More important to me: Can this variable be set per-connection? If so, how? Specifically, how do I set it for a none-console connection (e.g. my previously mentioned jdbc connection)? BTW: # mysql --version mysql Ver 14.7 Distrib 4.1.21, for pc-linux-gnu (i686) using readline 5.1 Amit Visolve DB Team wrote: > There is no global system variable to set Autocommit; but we can > achieve the > same with 'init_connect=SET AUTOCOMMIT=0'. > This variable can be set from the mysql or in the commandline or in the > option file. > Like, > mysql > SET GLOBAL init_connect='SET AUTOCOMMIT=0'; > or > mysql>SET @@GLOBAL.init_connect='SET AUTOCOMMIT=0'; > > or in the option file > [mysqld] > init_connect='set AUTOCOMMIT=0' > or > shell> mysqld --init_connect='set AUTOCOMMIT=0' > By default AUTOCOMMIT is enabled. ie set to 1. If set to 0, then > disabled. > check with 2 connections; try inserting or updating in one connection; > check > in the other with select. > > This variable was added in MySQL 4.1.2. > > > - Original Message - From: "Amit Dor-Shifer" <[EMAIL PROTECTED]> > To: > Sent: Tuesday, November 21, 2006 4:41 PM > Subject: AUTOCOMMIT. displaying and setting > > >> Hi. >> >> I'm puzzled rgd. a/m. Is AUTOCOMMIT a variable? If so, is it a session >> variable? Should it show up when issuing a "SHOW VARIABLES" command? >> >> How do I set this variable when initalizing a jdbc connection? Can I >> pass it on the connection URL? Can someone present a code line for this? >> >> How do I set this variable for an interactive console session? Can i do >> this from the command line? When I attempt this I get: >> # mysql -p --autocommit=0; >> mysql: unknown variable 'autocommit=0' >> >> >> Thanks, >> Amit >> >> -- >> MySQL General Mailing List >> For list archives: http://lists.mysql.com/mysql >> To unsubscribe: >> http://lists.mysql.com/[EMAIL PROTECTED] >> > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: AUTOCOMMIT. displaying and setting
There is no global system variable to set Autocommit; but we can achieve the same with 'init_connect=SET AUTOCOMMIT=0'. This variable can be set from the mysql or in the commandline or in the option file. Like, mysql > SET GLOBAL init_connect='SET AUTOCOMMIT=0'; or mysql>SET @@GLOBAL.init_connect='SET AUTOCOMMIT=0'; or in the option file [mysqld] init_connect='set AUTOCOMMIT=0' or shell> mysqld --init_connect='set AUTOCOMMIT=0' By default AUTOCOMMIT is enabled. ie set to 1. If set to 0, then disabled. check with 2 connections; try inserting or updating in one connection; check in the other with select. This variable was added in MySQL 4.1.2. - Original Message - From: "Amit Dor-Shifer" <[EMAIL PROTECTED]> To: Sent: Tuesday, November 21, 2006 4:41 PM Subject: AUTOCOMMIT. displaying and setting Hi. I'm puzzled rgd. a/m. Is AUTOCOMMIT a variable? If so, is it a session variable? Should it show up when issuing a "SHOW VARIABLES" command? How do I set this variable when initalizing a jdbc connection? Can I pass it on the connection URL? Can someone present a code line for this? How do I set this variable for an interactive console session? Can i do this from the command line? When I attempt this I get: # mysql -p --autocommit=0; mysql: unknown variable 'autocommit=0' Thanks, Amit -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL MiniConf at linux.conf.au 2007 CfP
This is a call for participation in the second MySQL Miniconf which will be part of the linux.conf.au (LCA) 2007 conference in Sydney, Australia. The Miniconf will be run on Monday, January 15th, before the conference proper starts. This is the first conference of its type to be held in the Southern hemisphere and we are looking forward to participants from areas around Australia, New Zealand, South-East Asia, India and South America. Any topic is allowed based around MySQL. Types of presentations that we're after, include: Conference presentations (30 - 45 minutes) Tales of Deployment (10 - 30 minutes) - these are designed to show people how MySQL has been implemented in the real world, which will comprise of a mash-up of a case study and a discussion session. Please submit an abstract of your suggested presentation via email to [EMAIL PROTECTED] For all abstracts, the following information is required: Title of Presentation Description (no longer than 250 words) Targeted Audience Full Name Email Address URL of Home Page (if it should be listed in the program) Job Title (if it should be listed in the program) Company/Affiliation (if any) Postal Address Contact Telephone Number (for last minute issues, cell phone number preferred) Short Biography (1 or 2 paragraphs) Your proposal must be sent before the 30th November 2006 in order to be considered for inclusion in the conference. Please note that the MySQL Miniconf forms part of the LCA 2007 main conference held by Linux Australia. This means that you must register for LCA 2007 attendance to participate in the conference. For further details regarding registration and accommodation for LCA 2007, please visit LCA 2007. Speakers will be notified by 7th December 2007. -- Colin Charles, Community Engineer MySQL AB, Melbourne, Australia, www.mysql.com Office: [EMAIL PROTECTED] / +46 18 174 400 ext. 4528 Mobile: +614 12 593 292 / Skype: colincharles MySQL Forge: http://forge.mysql.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: shutdown database but not mysqld
In the last episode (Nov 22), Alfred Mak said: > Can I shutdown one of the databases in MySQL but not the whole mysqld > process (i.e. keeping the other databases still running) ? "shutdown" would be the wrong word then :) How about revoking permissions (either at the mysql or the filesystem level) ? You could also flush tables, then rename the database directory somewhere out mysql's data directory. -- Dan Nelson [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
