Updated in 468a827.


On Tue, Jun 4, 2013 at 11:16 AM, Logan Linn <notifications@github.com>wrote:

> In sql/triggers.sql:
>
> > +ALTER TABLE poky DROP CONSTRAINT IF EXISTS created_at_utc_check;
> > +ALTER TABLE poky ADD CONSTRAINT created_at_utc_check CHECK (EXTRACT(TIMEZONE FROM created_at) = '0');
> > +
> > +
> > +-- upsert tuple while ensuring that the modified timestamp is >= than the current
> > +-- timestamp if the record exists. if the timestamp parameter is null, the
> > +-- tuple is inserted using a modified_at of NOW or updated leaving the existing
> > +-- modified_at intact.
> > +-- Return values:
> > +--  'inserted' on insert
> > +--  'updated' on successful update
> > +--  'rejected' when the modified at does not satisfy the >= condition
> > +CREATE OR REPLACE FUNCTION upsert_kv_data(b TEXT, k TEXT, d TEXT, m timestamptz DEFAULT NULL) RETURNS TEXT AS
> > +$$
> > +DECLARE
> > +    existing_row_lock RECORD;
>
> Looks like this can be removed
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/drsnyder/poky/pull/9/files#r4529366>
> .
>



-- 
http://damonsnyder.net