MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:Paul DuBois Date:December 11 2007 4:55pm
Subject:Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535
View as plain text  
At 11:15 AM +0100 12/11/07, Sergei Golubchik wrote:
>Hi!
>
>On Dec 08, Konstantin Osipov wrote:
>>  * Sergei Golubchik <serg@stripped> [07/12/07 23:22]:
>>  >
>>  > http://www.jsw4.net/info/listserv_archives/mysql/05-wk02/msg00115.html
>>
>>  mentions handle_options and my_init, which are not in mysql.h
>
>One should use mysql_library_init() instead which calls my_init
>internally.
>
>>  > http://www.listsearch.com/MySQL/Message/index.lasso?216520
>>
>>  Mentions my_init(), not in mysql.h.
>>
>>  > http://www.searchy.net/mailinglists/MySQL_General/msg11412.html
>>  > http://www.galileo-press.de/openbook/c_von_a_bis_z/c_027_003.htm
>>
>>  Uses my_init(), doesn't include my_sys.h and it all works only
>>  because it's a C program, so no prior declaration is required.
>>
>>  > http://search.cpan.org/~darren/MySQL-Config-1.03/lib/MySQL/Config.pm
>>
>>  Export parse_defaults as well, not part of mysql.h
>>
>>  > (the last is the pupe-perl emulation, shows that the functionality is
>>  > used indeed)
>>  >
>>  > ... and many more
>>
>>  Point is: for anything even little beyond trivial one has to
>>  include my_sys.h.
>
>if you refer to my_init() - one should use mysql_library_init()
>instead, it's in mysql.h

True, mysql_library_init() is what should be used now.

But none of our own clients use it. :-(

-- 
Paul DuBois, MySQL Documentation Team
Madison, Wisconsin, USA
MySQL AB, www.mysql.com
Thread
bk commit into 5.1 tree (kostja:1.2614) BUG#25535konstantin4 Dec
  • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Sergei Golubchik6 Dec
    • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Konstantin Osipov6 Dec
      • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Sergei Golubchik7 Dec
        • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Konstantin Osipov7 Dec
          • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Paul DuBois7 Dec
            • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Konstantin Osipov7 Dec
          • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Sergei Golubchik7 Dec
            • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Konstantin Osipov7 Dec
              • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Sergei Golubchik7 Dec
                • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Konstantin Osipov7 Dec
                  • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Sergei Golubchik11 Dec
                • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Konstantin Osipov7 Dec
                  • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Sergei Golubchik11 Dec
                    • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Paul DuBois11 Dec
                • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Konstantin Osipov8 Dec
                  • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Paul DuBois8 Dec
                    • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Konstantin Osipov8 Dec
                    • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Sergei Golubchik11 Dec
                      • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Konstantin Osipov11 Dec
                        • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Sergei Golubchik11 Dec
                        • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Paul DuBois5 Feb
                      • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Paul DuBois11 Dec
                        • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Paul DuBois11 Dec
                          • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Sergei Golubchik11 Dec
                            • Re: bk commit into 5.1 tree (kostja:1.2614) BUG#25535Paul DuBois11 Dec