Обсуждение: newbie question to setTimestamp( int parameterIndex, Timestamp x, Calendar cal)

Hi all!

I am new to postgresql and i have the following question:

how does setTimestamp( int parameterIndex, Timestamp x, Calendar cal) work?
why is there a parameter Timestamp? I have a Calendar in my java code and I
would like to store it in the database via a PreparedStatement. So for
example:

I have the following table:

CREATE TABLE dates( date    TIMESTAMP WITH TIME ZONE );

Java code:

PreparedStatement ps = connection.prepareStatement( "INSERT INTO
    dates (date) VALUES ?");
ps.setTimestamp( 1, new Timestamp(), myCalendar );

Is this correct? But why is there a Timestamp parameter? It seems clear that
the
calendar should be converted into a timestamp because the method is named
setTimestamp. I am really confused about this.

Please help

Peter

Peter,

Timestamp is the actual time that you want to store. The calendar
object is there if you want to use a different calendar to reference
the timestamp to ?

Dave
On 19-Jul-05, at 6:49 AM, Peter.Zoche@materna.de wrote:

> Hi all!
>
> I am new to postgresql and i have the following question:
>
> how does setTimestamp( int parameterIndex, Timestamp x, Calendar
> cal) work?
> why is there a parameter Timestamp? I have a Calendar in my java
> code and I
> would like to store it in the database via a PreparedStatement. So for
> example:
>
> I have the following table:
>
> CREATE TABLE dates( date    TIMESTAMP WITH TIME ZONE );
>
> Java code:
>
> PreparedStatement ps = connection.prepareStatement( "INSERT INTO
>     dates (date) VALUES ?");
> ps.setTimestamp( 1, new Timestamp(), myCalendar );
>
> Is this correct? But why is there a Timestamp parameter? It seems
> clear that
> the
> calendar should be converted into a timestamp because the method is
> named
> setTimestamp. I am really confused about this.
>
> Please help
>
> Peter
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>                http://archives.postgresql.org
>
>

Hi,

This is 2 static method what convert from/to TimeStamp/GregorianCalendar:

public static Timestamp Gregorian2Timestamp(GregorianCalendar
gregorianCalendar) {
        return (gregorianCalendar == null ? null : new
java.sql.Timestamp(gregorianCalendar.getTimeInMillis()));
}

public static GregorianCalendar Timestamp2Gregorian(Timestamp timestamp) {
        GregorianCalendar result = null;
        if (timestamp != null) {
            result = new GregorianCalendar();
            result.setTime(new Date(timestamp.getTime()));
        }
        return (result);
}

linimi

On 7/19/05, Dave Cramer <pg@fastcrypt.com> wrote:
> Peter,
>
> Timestamp is the actual time that you want to store. The calendar
> object is there if you want to use a different calendar to reference
> the timestamp to ?
>
> Dave
> On 19-Jul-05, at 6:49 AM, Peter.Zoche@materna.de wrote:
>
> > Hi all!
> >
> > I am new to postgresql and i have the following question:
> >
> > how does setTimestamp( int parameterIndex, Timestamp x, Calendar
> > cal) work?
> > why is there a parameter Timestamp? I have a Calendar in my java
> > code and I
> > would like to store it in the database via a PreparedStatement. So for
> > example:
> >
> > I have the following table:
> >
> > CREATE TABLE dates( date    TIMESTAMP WITH TIME ZONE );
> >
> > Java code:
> >
> > PreparedStatement ps = connection.prepareStatement( "INSERT INTO
> >     dates (date) VALUES ?");
> > ps.setTimestamp( 1, new Timestamp(), myCalendar );
> >
> > Is this correct? But why is there a Timestamp parameter? It seems
> > clear that
> > the
> > calendar should be converted into a timestamp because the method is
> > named
> > setTimestamp. I am really confused about this.
> >
> > Please help
> >
> > Peter
> >
> > ---------------------------(end of
> > broadcast)---------------------------
> > TIP 4: Have you searched our list archives?
> >
> >                http://archives.postgresql.org
> >
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>