Recent

Author Topic: Connection issues, continued...  (Read 874 times)

jksmithiii

  • New Member
  • *
  • Posts: 10
Connection issues, continued...
« on: January 16, 2025, 10:02:19 pm »
win 10, trunk FPC. Tried everything to connect to Maria. She still hates me. Checked for 64 bit libmysql.dll ('PE  d'), validated connection params with HeidiSQL. Tracked down every libmysql.dll on the drive. Heidi must have all the charm because she always connects. So the connection issue has long been solved with that app. But still this is a rolling grey issue with SQLdb.

So, moved over to Zeoslib. Connects right up. But the OPM version has a bug in it that causes exception in the transaction code on app shut down. May work if I did all the hookups manually in code instead of using a data module. But instead of chasing that down, I tried to load and install zcomponents.lpk direct from zeos github. No joy. Defines issue around ASCII7_MESSAGES in zmessages.

Before I try all this on my Linux machine, I'd like to have a stiff Manhattan right now, but I'm out of Makers. Anybody else out there have this lead them to drink?

James

jksmithiii

  • New Member
  • *
  • Posts: 10
Re: Connection issues, continued...
« Reply #1 on: January 17, 2025, 04:50:44 am »
Ok, with some of these tasks, just saves time to not chase lpk issue and wire it up manually. Works fine.

TRon

  • Hero Member
  • *****
  • Posts: 3930
Re: Connection issues, continued...
« Reply #2 on: January 17, 2025, 12:03:45 pm »
Pouring your own drink always offers a finer grained control  :)

It tends to get complicated pretty fast with visual controls and all the coupled events.
I do not have to remember anything anymore thanks to total-recall.

Zvoni

  • Hero Member
  • *****
  • Posts: 2821
Re: Connection issues, continued...
« Reply #3 on: January 17, 2025, 12:48:24 pm »
win 10, trunk FPC. Tried everything to connect to Maria. She still hates me. Checked for 64 bit libmysql.dll ('PE  d'), validated connection params with HeidiSQL. Tracked down every libmysql.dll on the drive. Heidi must have all the charm because she always connects. So the connection issue has long been solved with that app. But still this is a rolling grey issue with SQLdb.

So, moved over to Zeoslib. Connects right up. But the OPM version has a bug in it that causes exception in the transaction code on app shut down. May work if I did all the hookups manually in code instead of using a data module. But instead of chasing that down, I tried to load and install zcomponents.lpk direct from zeos github. No joy. Defines issue around ASCII7_MESSAGES in zmessages.

Before I try all this on my Linux machine, I'd like to have a stiff Manhattan right now, but I'm out of Makers. Anybody else out there have this lead them to drink?

James
... or in the future just quote the exact error-message you get.
With MariaDB it's 90% of cases the skiplibrarycheck-option
One System to rule them all, One Code to find them,
One IDE to bring them all, and to the Framework bind them,
in the Land of Redmond, where the Windows lie
---------------------------------------------------------------------
Code is like a joke: If you have to explain it, it's bad

CharlyTango

  • Jr. Member
  • **
  • Posts: 93
Re: Connection issues, continued...
« Reply #4 on: January 27, 2025, 09:38:09 am »
win 10, trunk FPC.

Who would think of trying a database connection with a trunk version without need?
It is not even guaranteed that trunk versions can be compiled at any time without problems. And for me, ZEOS version 8 is still a long way from being sufficiently tested in all aspects.

I would tackle something like this with a stable version, if necessary even with one that is somewhat older and therefore sufficiently used and tested (perhaps 3.4 or 3.6).
Version 7 of ZEOS, which has already been in use for a few years, would also be suitable.

Such a strategy would drastically reduce your alcohol consumption, so that in principle you would want to
Lazarus stable, Win32/64

 

TinyPortal © 2005-2018