On Fri, Jul 29, 2005 at 10:46:35PM -0400, Bruce Momjian wrote:
>
> Has this been fixed?
>
> ---
>
> Hans-Jürgen Schönig wrote:
> > we have found a bug in CVS head using PL/Perl:
> >
> > [EMAIL PROTECTED] hs]$ psql test < /t
no, this one seems to be fine now.
i have no idea what went wrong.
the code cored at some very "unlikely" place.
somehow rebooting helped ... - this was very strange.
fortunately it works nicely now ...
many thanks a best regards,
hans
Michael Fuhr wrote:
On Fri, Jul
On Sat, Jul 30, 2005 at 02:43:23PM +0200, Hans-Jürgen Schönig wrote:
> no, this one seems to be fine now.
> i have no idea what went wrong.
> the code cored at some very "unlikely" place.
Are you saying that it *did* dump core, or that it *didn't*? It's
possible that your coredumpsize resource li
Michael Fuhr wrote:
On Sat, Jul 30, 2005 at 02:43:23PM +0200, Hans-Jürgen Schönig wrote:
no, this one seems to be fine now.
i have no idea what went wrong.
the code cored at some very "unlikely" place.
Are you saying that it *did* dump core, or that it *didn't*? It's
possible that your core
On Sat, Jul 30, 2005 at 03:46:46PM +0200, Hans-Jürgen Schönig wrote:
> Michael Fuhr wrote:
> >Are you saying that it *did* dump core, or that it *didn't*?
>
> it cored; my core-size settings are ok ...
So were you able to get a stack trace from the core dump?
--
Michael Fuhr
http://www.fuhr.org
[Please copy the mailing list on replies.]
On Sat, Jul 30, 2005 at 05:20:07PM +0200, Hans-Jürgen Schönig wrote:
> Michael Fuhr wrote:
> >So were you able to get a stack trace from the core dump?
>
> yes, but i did not keep the backtrace.
> i did not expect the db to work after the reboot.
>
> yo
I've used EOModeler with odbc for MS SQL Server,
MySQL and MS Access with no problem. But got
problem with postgre odbc driver. (the newest
one)
EOMOdeler cannot get postgresql column types' info
through odbc. Also,
It cannot interact with EOModeler
for very simple query:
SQLExecDir
