Kind of fixed Melanie's "Exception(sql)" correction
Throwing an Ex. with SQL command in the message looks weird, this is a bit better, but I'm still not sure if that's the proper way to handle. Also, there is a catch one level up, so is this one necessary?soprefactor
							parent
							
								
									e4b8d76b10
								
							
						
					
					
						commit
						527a257b9f
					
				| 
						 | 
				
			
			@ -150,9 +150,9 @@ namespace OpenSim.Data
 | 
			
		|||
                    {
 | 
			
		||||
                        cmd.ExecuteNonQuery();
 | 
			
		||||
                    }
 | 
			
		||||
                    catch
 | 
			
		||||
                    catch(Exception e)
 | 
			
		||||
                    {
 | 
			
		||||
                        throw new Exception(sql);
 | 
			
		||||
                        throw new Exception(e.Message + " in SQL: " + sql);
 | 
			
		||||
                    }
 | 
			
		||||
                }
 | 
			
		||||
            }
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
		Reference in New Issue