13 Commits

Author SHA1 Message Date
Sean Chittenden
455b76828f Add a *log.Logger argument to physical.Factory
Logging in the backend is a good thing.  This is a noisy interface change but should be a functional noop.
2016-04-25 20:10:32 -07:00
Sean Chittenden
afa6c22fec go fmt the PostgreSQL backend 2016-04-25 18:01:13 -07:00
Devin Christensen
9b175bd936 Make the PostgreSQL backend more performant 2016-01-29 13:47:10 -07:00
Devin Christensen
c2b66587c8 Improve naming
Hopefully this naming scheme will be more straightforward.
2016-01-27 17:15:48 -07:00
Devin Christensen
01c315c766 Update naming and pull DDL for upsert back out 2016-01-22 17:15:10 -07:00
Devin Christensen
bba6cfda6a Move the upsert definition back into the code 2016-01-22 09:47:02 -07:00
Devin Christensen
8710076c39 Remove options for column configuration 2016-01-22 08:41:31 -07:00
Devin Christensen
a2b1b697a0 Remove DDL statements from the code 2016-01-20 18:52:49 -07:00
Devin Christensen
1886fe81f9 Remove superfluous comparison 2016-01-20 17:05:21 -07:00
Devin Christensen
6002154cb6 Ensure rows.Close() is called in List 2016-01-20 17:02:23 -07:00
Devin Christensen
fb55a46d81 Prefer TEXT over VARCHAR
From the PostgreSQL docs
(http://www.postgresql.org/docs/9.4/static/datatype-character.html):

 > Tip: There is no performance difference among these three types,
 > apart from increased storage space when using the blank-padded type,
 > and a few extra CPU cycles to check the length when storing into a
 > length-constrained column. While character(n) has performance
 > advantages in some other database systems, there is no such advantage
 > in PostgreSQL; in fact character(n) is usually the slowest of the
 > three because of its additional storage costs. In most situations
 > text or character varying should be used instead.
2016-01-20 16:56:46 -07:00
Devin Christensen
3d7a81f226 Use native upsert when available 2016-01-20 10:47:54 -07:00
Devin Christensen
5bea0d9731 Add support for PostgreSQL as a physical backend 2016-01-19 17:00:09 -07:00