On Tue, 2 Mar 2004 16:43 , 'Schildberg, Steffen' <[EMAIL PROTECTED]> sent:
>> It is DBEXTRACT that concerns me most and is partly >> responsible for misleading me :) DBEXTRACT creates a >> catalog script that will do things such as: >> >> USE USER a >> CREATE TABLE a1 >> USE USER B >> CREATE TABLE b1 >> >> instead of: >> >> CREATE TABLE a.a1 >> CREATE TABLE b.b1 >> >Yes, and the Loader does right here. >You can't create tables on somebody others behalf, can you? So you >(the Loader) must simply log on as this user to create his/her tables. > >> But given that each of these "user user" defaults to >> localhost, the script can only be run localhost without >> manual revision to change >> every "use user" to include the additional host parameters. >> >You shouldn't change those USE USER commands within the catalog script >that you then run with CATALOGLOAD. These USE USER commands are slightly >otherwise handled as 'normal' USE USER commands and a switch to another >db or server wouldn't work here. >And those USE USER commands do not necessarily default to 'localhost'. They >depend on what USE USER command you run before CATALOGLOAD command. Suppose your >localhost is server1 with db tst1 and you want to load the catalog to >tst2 on server2. You run Loadercli on your server1 with the following commands: >use user dba dba serverdb tst2 on server2 > >// >catalogload all instream file '' > >All USE USER commands in would point to tst2 on server2 in this case. Ok, this changes my understanding of loadercli. I had assumed 'use user' was the same throughout the system. Now you have told me that the 'stub commands' behave different than the CATALOGLOAD commands... I have to experiment further. Stephen Gutknecht -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
