Jim Nasby

> What version of PostgreSQL are you using? This was on 9.5.

It's just a varchar, two datetime fields and a timestamp field. Which I just noticed was a timestamp field... maybe that's the problem. Unfortunately that project has spun down so...

What I was wondering if whether it was possible for a MSSQL timestamp (_timestamp_, not _datetime_) field to return an empty string, or whether there was something wrong with it's...

Perhaps a better solution would be to go the other direction: have a package that wraps a supplied error the same way that the underlying package does. That would allow...

@jaekwon > I think it should always be possible to unwrap an error an exact number of times to get to what you want. Can't you do that by creating...

I think there would need to be a `func SetStackBounds(start,end int)` that found the first error that had a stack trace and adjusted it's stack trace accordingly. For withStack{}, this...

I've run into this same kind of problem while using pkg/errors: https://github.com/pkg/errors/issues/129.

I've pondered that kind of logging ability as well. In addition to a file filter, I've pondered a filter based on function name. I've also thought about adding some notion...

I'm not sure if this is still an open item, but here's a few thoughts about it: - I think it would be useful to have a way to scream...

So.... I've got a branch where I've [tested 8.1 through 11](https://travis-ci.org/decibel/pgtap/builds/592828836). 9.0 and older don't work because the travis script can't find appropriate packages. Also, we're unable to test versions...