On Wed, Sep 14, 2005 at 00:09:58 -0400,
Joe <[EMAIL PROTECTED]> wrote:
>
> I'm not sure I agree with the need to "fix" or "sanitize" the data. The
> columns in question are used mostly for publication dates. While you may
> be able to find a full release date for recent books, they are gener
On Wed, 2005-09-14 at 15:49 +1200, Brent Wood wrote:
>
> Sanitizing is one thing, inventing data to fit an incomplete value into a
> date datatype is not good practice.
Choose another datatype, or make a new one, or split the date into
columns. The type of your data is not a timestamp nor a date.
On Wed, Sep 14, 2005 at 03:49:29PM +1200, Brent Wood wrote:
> In case anyone is interested, right now we store year, month & day and
> have a timestamp field where the entire field is null if any one part is
> unknown.
>
> Are there any better ways in Postgres?
You can create a new type, which i
On Tue, 13 Sep 2005, Joshua D. Drake wrote:
> >
> > ERROR: date/time field value out of range: "1997-10-00"
> > HINT: Perhaps you need a different "datestyle" setting.
> > CONTEXT: COPY Entry, line 1, column EntryDate: "1997-10-00"
>
> Well the easy solution is to just make the date a text ty
On 9/14/05, Joe <[EMAIL PROTECTED]> wrote:
Joshua D. Drake wrote:> Well the easy solution is to just make the date a text type but that is> the wrong answer. The right answer is to fix the data set.> MySQL should never have allowed you do insert those dates in the first
> place. I know that doesn't
Joshua D. Drake wrote:
Well the easy solution is to just make the date a text type but that is
the wrong answer. The right answer is to fix the data set.
MySQL should never have allowed you do insert those dates in the first
place. I know that doesn't help you much but at some point
you are goi
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>> Any suggestions (aside from designing a new datatype)?
> Well the easy solution is to just make the date a text type but that is
> the wrong answer. The right answer is to fix the data set.
> MySQL should never have allowed you do insert those date
ERROR: date/time field value out of range: "1997-10-00"
HINT: Perhaps you need a different "datestyle" setting.
CONTEXT: COPY Entry, line 1, column EntryDate: "1997-10-00"
I read Appendix B and section 8.5, but I didn't find any way around
this, i.e., it seems Postgres insists on complete
I'm converting a MySQL database to PostgreSQL. Two of the tables have DATE
columns which have many "partial" dates. For example, a partial date may be for
the publication date of a book, where the date is specified as only the year,
e.g., 1957-00-00, and another partial date may be the publica
