Message-ID: <74DB3341AB704E989C87CAAD89D2526F@marktestcr.marktest.pt>
From: "Oliveiros d'Azevedo Cristina" <oliveiros.cristina@marktest.pt>
To: "Tarlika Elisabeth Schmitz" <postgresql3@numerixtechnology.de>,
	<pgsql-sql@postgresql.org>
References: <20110208181400.2e88d7cc@dick.coachhouse>
Subject: Re: data import: 12-hour time w/o AM/PM
Date: Tue, 8 Feb 2011 18:38:44 -0000
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

Howdy, Tarlika.

If the data doesn't bring the AM/PM how are you supposed to distinguish 
between,say, 10pm and 10am ? Does it always start at 10:30am? So 10am never 
arises?

Best,
Oliveiros

----- Original Message ----- 
From: "Tarlika Elisabeth Schmitz" <postgresql3@numerixtechnology.de>
To: <pgsql-sql@postgresql.org>
Sent: Tuesday, February 08, 2011 6:14 PM
Subject: [SQL] data import: 12-hour time w/o AM/PM


I am importing data in CSV format. My technique is to COPY the data
into interim tables (starting with a "z") where I analyze them, clean
up inconsistencies; eventually I will populate the "proper" tables with
these data. (In the example below: COPY CSV into zevent, from there
populate event.)

The time field of the event data is givng me a headache: it's in 12h
format but without the AM/PM qualifier!

CREATE TABLE zevent
(
  id integer,
  previous integer,
  "next" integer,
  location_id integer NOT NULL,
  datum date NOT NULL,
  otime character varying(5) NOT NULL
)

CREATE TABLE event
(
  id integer NOT NULL,
  location_fk integer NOT NULL,
  otime timestamp without time zone NOT NULL,
  next_fk integer,
  previous_fk integer,
  CONSTRAINT event_pkey PRIMARY KEY (id),
  CONSTRAINT next_event_fk FOREIGN KEY (next_fk)
      REFERENCES event (id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE NO ACTION,
  CONSTRAINT previous_event_fk FOREIGN KEY (previous_fk)
      REFERENCES event (id) MATCH SIMPLE
      ON UPDATE NO ACTION ON DELETE NO ACTION
)