Page 1 of 2

Postgresql locate

Posted: Fri 27 Dec 2013 15:22
by lao
Hi,
i have a problem with postgresql and unidac.
this is the script for create table:
CREATE TABLE mytableone
(
datetimes timestamp without time zone NOT NULL,
codemodule character varying(150) NOT NULL,
CONSTRAINT pk_date_module PRIMARY KEY (datetimes, codemodule)
)
WITH (
OIDS=FALSE
);
ALTER TABLE mytableone
OWNER TO postgres;

insert into mytableone values('06/15/2011 02:28:47 AM','GC_Injector_HP_5890_3240G19047-B');
insert into mytableone values('06/27/2011 01:51:33 PM','GC_Injector_HP_5890_3240G19047-B');

and i try to execute this code:
uniquery1.close;
uniquery1.IndexFieldNames:='datetimes,codemodule';
uniquery1.Open;
if not uniquery1.Locateex('datetimes;codemodule', VarArrayOf([('06/15/2011 02:28:47 AM'), 'GC_Injector_HP_5890_3240G19047-B']), [])
then showmessage('first one not found');
if not uniquery1.Locateex('datetimes;codemodule', VarArrayOf([('06/27/2011 01:51:33 PM'), 'GC_Injector_HP_5890_3240G19047-B']), []) then showmessage('second one not found');


i have a message 'first one not found';
if uniquery1.IndexFieldNames:=''
no problem

my regional options for dates is : MM/dd/yyyy
and for time: hh:mm:ss
i try with unidac 5.1 and 5.2 and delphi 2007
i try with locate and locateex.
i try with interbase no problem.
regards,
sorry for my english...
Lao

Re: Postgresql locate

Posted: Mon 30 Dec 2013 15:09
by AlexP
Hello,

Thank you for the information. We have reproduced the problem and will investigate the reasons for such behaviour.

Re: Postgresql locate

Posted: Thu 02 Jan 2014 08:39
by lao
hi,
i think the problem apear when we have 2 fields in the key and the last field have more than 1 identical value.
I need to use that in production, please when you found the solution, can you explain me what i need to change( i have the sources of undidac).
Thanks
Regards,

Re: Postgresql locate

Posted: Thu 09 Jan 2014 11:09
by lao
Hi,
Happy new year...
Have you some news for this problem?
Regards

Re: Postgresql locate

Posted: Fri 10 Jan 2014 09:16
by AlexP
Hello,

We will fix the problem till the next release

Re: Postgresql locate

Posted: Fri 10 Jan 2014 09:45
by lao
Hi,
Do you have any date for the next release?
Regards,

Re: Postgresql locate

Posted: Fri 10 Jan 2014 14:47
by AlexP
Hello,

We plan to release the new version next month.

Re: Postgresql locate

Posted: Fri 10 Jan 2014 17:05
by stlcours
Hi, Alex

Can you see my question:
http://forums.devart.com/viewtopic.php?f=28&t=28653

Thanks very much!!

Re: Postgresql locate

Posted: Sat 11 Jan 2014 13:54
by AlexP

Re: Postgresql locate

Posted: Tue 04 Feb 2014 13:09
by lao
Hi,
Did locate problem has been solved?
if yes, please can you send me the correction to apply to my unidac src?
We need to implement this very quickly.
Thanks

Re: Postgresql locate

Posted: Wed 05 Feb 2014 11:49
by AlexP
We have fixed the problem. I can send you the fixed method by e-mail. Please specify an e-mail to which I can send the modifications

Re: Postgresql locate

Posted: Tue 11 Feb 2014 08:38
by lao
Hi Alexp
thank you for your response.
you can send me the method at:
[email protected]
regards,

Re: Postgresql locate

Posted: Tue 11 Feb 2014 11:15
by AlexP
We have added quite a lot of changes, therefore send your license number to alexp*devart*com - and I will send you a fixed version

Re: Postgresql locate

Posted: Tue 11 Feb 2014 12:34
by lao
Hi AlexP,
i send you my license number,
thanks

Re: Postgresql locate

Posted: Wed 12 Feb 2014 14:02
by AlexP
I have sent you a letter with the fixed version.