[Gambas-user] Extracting fields from a Result

[Doug Hutcheson]

On Wed, 2018-01-03 at 16:18 -0500, T Lee Davidson wrote:
> On 01/03/2018 02:13 PM, Tobias Boege wrote:
> > Also, I kind of lost the thread. We have two issues here, right?
> > 
> >   1. The pg driver might not handle the case-insensitive column
> > names
> >      correctly in all places.
> >   2. Opening IDE-defined connections with passwords fails.
> 
> AFAIK, that is correct, Tobi.
> 
> 
> > I have never used the Connection editor, but from reading the code,
> > it doesn't save the password directly somewhere but uses
> > Desktop.Passwords
> > to store and retrieve it, leaving the details to the current
> > desktop's
> > tools. (I've never had much luck with gb.desktop as a whole, I must
> > say,
> > and I don't know how it works.)
> 
> I would have to agree that the problem is in the Connection editor,
> and more specifically, the manner in which it handles passwords.
> 
> As I reported earlier, when Saving the connection properties, I got
> an error, "Cannot store passwords on desktop KDE5: No wallet
> found" even though "Remember password" was not enabled. That option
> seems to have no effect.

Just to add some information to that, I use the Gnome desktop, not KDE.
Gnome uses GnomeKeyring and, prompted by this discussion, I have just
browsed the keyring. It does have the correct password set for my
application PostgreSQL_test, using path
PostgreSQL_test/Connection/Connection1 - Connection1 being the
connection I have established for my test harness.
> It is not an error that there was no wallet found. I don't use one.
> So, there should be a fall-back for that, IMO.
> 
> But even then, after I have entered the password and it is set in the
> editor's password field, the application is still unable
> to connect.
> 
I agree. When I use the Connection editor, I can go back to it at any
time and find the password still correctly shown. Interesting.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gambas-basic.org/pipermail/user/attachments/20180104/d0a77133/attachment-0001.html>