Sean Bowman

At this point if you want to change the API, you should create a new project or version it somehow. Your change basically broke a dozen projects at our company.

The problem stems from lines 424-436 in http.clj. The URI gets parsed then reassembled with the query string. Unfortunately, java.net.URI is helpful enough that it decodes the path for you...

Instead of (.getPath u), you should be using (.getRawPath u): ``` user=> (def uri (java.net.URI. "http://localhost:4000/p/abc/d/Just%20For%20Fun/m")) #'user/uri user=> uri # user=> (.getPath uri) "/p/abc/d/Just For Fun/m" user=> (.getRawPath uri) "/p/abc/d/Just%20For%20Fun/m"...

Your code now refers to "github.com/mguz/logxi", but your logxi package has all the code under "v1". Did you perhaps change something locally in logxi that you didn't push? Edit: Just...

A table is a relation. I think this is the same bug I reported in #46.

@tv42 Are you karma trolling? If you don't have a patch or something meaningful to contribute, why not leave the technical discussions to the big boys? Have you even tried...

You do have an obligation to write before `db.Close`, because **your batch functionality doesn't give me any control over when or if it completes**. Has absolutely nothing to do with...

After picking through the batch code, I think I finally get what @tv42 intended, but it's not obvious and I'm not sure what `db.Batch` buys me anymore. It looks like...

I misread the code around running batches as a group under a single transaction; looks like that is what a batch will do for you. Still not really keen on...

For the record, here's how I expected batches to work (hence the confusion): go db.Batch(...) go db.Batch(...) // etc.. // Hangs until batch syncs... if err := db.Close(); err !=...