#25 where clause work not properly ?


Dear Developer,

In new Version 6.2 and later, I have problem with option where. (older version worked perfectly...)

I have a SQL request in where some one where=activ_byadmin="Y" AND activ_byuser="Y"

I run the MySql Server with --log ann look up with the tail. In this log mysql write only request
AND (activ_byadmin="Y")
but the full request is activ_byadmin="Y" AND activ_byuser="Y" and it should be seen as
AND (activ_byadmin="Y" AND activ_byuser="Y")

Througth README, found that the where schould as
[where=activ_byadmin="Y" AND activ_byuser="Y"]
ist ist right, but we see in MySql log no request as the given...


Additional criteria for the query. For example:
[where=Host.name="web" AND User.active=1]
does not work ? Or we have bad syntax ?

In older version for the 6.2 I have syntax
where='activ_byadmin="Y" AND activ_byuser="Y"' and this works super and properly.

How can we use the pam_mysql with this where clause option? Can You help with syntax, or write the path for the new version?

my System:
# uname -a
FreeBSD hosts 6.2-STABLE FreeBSD 6.2-STABLE #0: Thu Jul 19 01:26:19 CEST 2007 Alexander@hosts:/usr/obj/usr/src/sys/hosts i386
# pkg_info | grep pam_mysql
pam_mysql-0.7.r1 A pam module for authenticating with MySQL

Thank You!

Regards Alexander


  • (C)0||3N

    (C)0||3N - 2008-08-28
    • priority: 5 --> 1
    • assigned_to: nobody --> collen
    • status: open --> open-out-of-date
  • (C)0||3N

    (C)0||3N - 2008-08-28

    Logged In: YES
    Originator: NO

    Can you send some debug info, or a -snip- from your mysql query log ?!

    you could try to do user.active="1"
    let me know if this is still a problem...

    Cheers, Collen


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks