Hi!
First off let me add a trick here that we have done in a couple of
engines. If you need access to more of the MySQL guts you can declare
this:
#define MYSQL_SERVER 1
Before your includes. This is probably not the smartest thing in the
world, since it will leave you in need of more binary compatibility.
I believe both PBXT and the AWS engine are now doing this trick. Now,
you will want to update the ac_mysql.m4 that you are using to the
latest version I have in the skeleton engine.
You can see the guts of the latest one here:
http://hg.tangent.org/skeleton-mysql-engine?
f=7d62ca562f56;file=config/ac_mysql.m4
And just to put a plug in for the skeleton engine, I am pretty
liberal about allowing commit access to it, so anyone who contributes
a couple of good patches can get access to update it directly. Its a
resource for learning/a starting place for people who need to hook up
an engine.
Cheers,
-Brian
On Apr 18, 2007, at 5:47 AM, Marko Mäkelä wrote:
> On Tue, Apr 17, 2007 at 01:59:43PM -0700, Brian Aker wrote:
>> Hi!
>>
>> Yes, we have been slow about getting the final patch out for loadable
>> engines in 5.1. If you want to see what it looks like we have made
>> the tree public:
>> http://mysql.bkbits.net:8080/mysql-5.1-wl2936/
>
> InnoDB is still not loadable, because some of the things it requires
> are not declared in <mysql/plugin.h> or any of the MySQL header files
> that are included by storage/innobase/handler/ha_innodb.cc when the
> preprocessor symbol MYSQL_DYNAMIC_PLUGIN is defined. I'm missing
> accessors for these members of THD:
>
> charset()
> in_sub_stmt
> killed
> memdup()
> query
> transaction.xid_state.xid
>
> Additionally, these functions or variables are not accessible to
> plugins:
>
> filename_to_tablename
> get_quote_char_for_identifier
> global_system_variables
> lower_case_table_names
> make_lex_string
> mysql_bin_log
> mysql_data_home
> mysqld_embedded
> mysql_real_data_home
> mysql_tmpdir
> opt_large_page_size
> query_cache
> reg_ext
> specialflag
> strconvert
>
> Will you be merging the patches I sent earlier, or should I prepare
> new
> patches?
>
> Best regards,
>
> Marko Mäkelä
> Innobase Oy/Oracle Corp.
>
> --
> MySQL Internals Mailing List
> For list archives: http://lists.mysql.com/internals
> To unsubscribe: http://lists.mysql.com/internals?
> unsub=brian@stripped
--
Brian Aker, Director of Technology
MySQL AB, www.mysql.com
Seattle, WA. USA
