Possibility of use own logger, not the Ruby's Logger.
Reported by Jan Molic | April 30th, 2008 @ 07:36 AM
I have my own Logger, but it seems there's no way how to use it
DataMapper::Database.setup( {
:adapter => 'mysql',
:host => 'foo',
:logger => MyLogger.new()
} )
Now I do it this way, which I don't prefer:
adapter = context.adapter
def adapter.logger= val
@logger = val
end
adapter.logger = MyLogger.new()
Comments and changes to this ticket
-
Sam Smoot May 2nd, 2008 @ 04:22 AM
There's now a DataMapper "global" logger, same as Merb's in 0.9.0 in DataMapper::logger.
The API doesn't accept blocks for messages, which we may have to revisit.
Why do you use a custom logger though? Maybe there's a compromise we can make to come together on this?
-
Sam Smoot May 8th, 2008 @ 04:42 PM
- State changed from “new” to “hold”
Putting this on hold until I hear back on it...
-
Dan Kubb (dkubb) November 30th, 2008 @ 02:19 AM
- Tag set to “feature, suggestion”
- State changed from “hold” to “invalid”
No reply from Sam's inquiry on May 8th. Marking this ticket as invalid.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Rick