Re: [Perfparse-devel-int] Patch for postgresql support and autotools

[Ben C. <bcl...@pe...>]

I get the error.

Friedrich has enlarged the size of the time variables in order to hold 
the longer time format of PostgreSQL:  (not ISO standard definition :)

MySQL:	'YYYY-MM-DD HH:MM:SS'
PSQL:	'YYYY-MM-DD HH:MM:SS.mmm'

But not enlarged the definition held in MySQL code-space.

(Unfortunately the timestamp from Nag does not use milliseconds, so 
cannot use this anyway :)

This will need some work since I use this variable directly on the CGI 
pages, and PSQL will need shortening back to the MySQL variant....

For time being I believe ignoring the warning will work.  Odd, I don't 
get this on my setup.

There are some other bits I've fixed, so will move to get out 0.105.2 
soon.  Then publicly announce PerfParse with PostgreSQL!!!

Might you or Tim have the exit() problem solved on perfparsed for this 
release?

Friedrich,

Is there anything else you want to add to the release?

Ben.





Yves wrote:

> Hi Ben,
> 
> I found time to check configure.ac and Makefile.am files.
> Check the attached patch.
> 
> With that, you are supposed to have the pg_config executable (just like the mysql_config
> one) and configure will use it to set POSTGRESQL_CFLAGS and POSTGRESQL_LIBS.
> 
> I also noticed some mistakes :
> - postgressql mistyping :)
> - you cannot init the same variable in 2 distinct conditionnals blocs (limitation of
> automake ?)
> 
> I fixed them.
> 
> I have not tested what I did, so please do it.
> 
> I noticed some problems when compiling perfparse with mysql support. See the attached
> file. No time to debug myself. Sorry :)
> 
> Yves
> 
> 


-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php