Hi Benoit and Safiur RAHMAN, Regardless of whether the revision #7454 fix works or not, I'd just like to warn of the following possible problem.
In postgresql, a timestamp column (with or without a timezone) is a date+time datatype. Presumably, inserting a time only value into a timestamp column will "assume" the current date for the date part (depending on the postgresql db driver version). If Safiur expects that the database will record the time only in that field and then, say, tries to SELECT based on a time only parameter he(?) will not succeed. There are a few possible ways to use a timestamp column to record time only. However the better solution is to use a "time [ (p) ] [ without time zone ]" column. This will ensure that any WHERE clause can use the time only value. (Just wanted to point that out) regards bruce -- B Bruen <adamn...@gnail.com (sort of)> ------------------------------------------------------------------------------ _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
