Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 8B42F9FB1BF for ; Fri, 26 Jan 2007 16:21:30 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 39561-05 for ; Fri, 26 Jan 2007 16:21:26 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by postgresql.org (Postfix) with ESMTP id 16C8A9FB1A5 for ; Fri, 26 Jan 2007 16:21:25 -0400 (AST) Received: by ug-out-1314.google.com with SMTP id k3so774811ugf for ; Fri, 26 Jan 2007 12:21:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=pAN5ky6WBkUYsc8gFy+0R6I7zFQ+mvd1pgrJdnytfbjzzsPw3MDyQR0RrTk9kF0Moz1cNDzsnm0pD9SjI6/6C/xGTq7A5R5YuU1gw1/QNwVHcRTmtVmdSGJKzq0Cau+nrAWCldViHbfNXyBStC6iIq64qhgRoUc6U8eOqKSWdjs= Received: by 10.82.135.13 with SMTP id i13mr2131211bud.1169842881645; Fri, 26 Jan 2007 12:21:21 -0800 (PST) Received: by 10.82.183.4 with HTTP; Fri, 26 Jan 2007 12:21:21 -0800 (PST) Message-ID: <1f30b80c0701261221t9bd0735yb221c7dfbc9fc6ad@mail.gmail.com> Date: Sat, 27 Jan 2007 01:21:21 +0500 From: imad To: "Shoaib Naazir" Subject: Re: Query regarding PostgreSQL date/time binary format for libpq Cc: pgsql-interfaces@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_51712_22655217.1169842881609" References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/42 X-Sequence-Number: 6420 ------=_Part_51712_22655217.1169842881609 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I am not totally confident about it but my first guess is that it is not possible. Because all data type "in" functions expect a char* as argument from the world outside. --Imad www.EnterpriseDB.com On 1/25/07, Shoaib Naazir wrote: > > Hi, > I am working on an application using PostgreSQL. I need to send date to > PostgreSQL in binary format using the libpq interface. I have walked through > the PostgreSQL code base, did find some reference to the date/time binary > format but didn't get the exact format. To much code to digest in one parse > :). > Can you please provide me with any good reference to the exact binary > format dbserver expect for date/time. I just can't use the text format :(. > Any reference material, paper, web page or a mail specifying the exact > binary date/time format will do. > > Thanks in advance. I really appreciate your time. > > regards, > Shoaib Naazir. > > > *Artificial intelligence is no match for natural > stupidity. * > > > ------------------------------ > Get into the holiday spirit, chat with Santa on Messenger. Ho-Ho-Ho! > ------=_Part_51712_22655217.1169842881609 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I am not totally confident about it but my first guess is that it is not possible. Because all data type "in" functions expect a char* as argument from the world outside.

--Imad
www.EnterpriseDB.com


On 1/25/07, Shoaib Naazir <je_shoaib@hotmail.com> wrote:
Hi,
   I am working on an application using PostgreSQL. I need to send date to PostgreSQL in binary format using the libpq interface. I have walked through the PostgreSQL code base, did find some reference to the date/time binary format but didn't get the exact format. To much code to digest in one parse :).
   Can you please provide me with any good reference to the exact binary format dbserver expect for date/time. I just can't use the text format :(. Any reference material, paper, web page or a mail specifying the exact binary date/time format will do.
 
Thanks in advance. I really appreciate your time.
 
regards,
Shoaib Naazir.


Artificial intelligence is no match for natural
stupidity.



Get into the holiday spirit, chat with Santa on Messenger.  Ho-Ho-Ho!

------=_Part_51712_22655217.1169842881609--