Thank for your answer. It makes all more clear now. Do you know something about the loader developments: time scheduling, versions?
Thanks. Matteo ----- Original Message ----- From: "Schildberg, Steffen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 05, 2004 5:47 PM Subject: AW: CATALOGLOAD Row too long > Hi Matteo, > > Matteo Gattoni [mailto:[EMAIL PROTECTED] wrote: > > > > What does it mean "change sqlmode for table create to > > oracle"? What do I need to do? > > Maybe, modify the file extracted manually and transform the > > table creation into Oracle Mode. > > Infact in the file, it is in internal mode: > > > Yes, it is the only choice you have right now. > > > How could I make this changing automatic? I would like to create an > > automatic export/import process. > > > At the moment you can't. The tiny little problem is the Loader. > It does ignore SQLMODE statements in case of CATALOGEXTRACT meaning > that even if you have the following subsequent commands > > SQLMODE ORACLE > // > CATALOGEXTRACT TABLE ... > > the Loader would place SQLMODE INTERNAL into your file. This is a bug > and needs to be fixed. We'll do it asap. Sorry for any inconvenience. > The problem is that the Loader has no information on the SQLMODE at > creation time of the catalog. So it can't set it properly and simply > sets it to the standard: INTERNAL. But it shouldn't at least ignore > the users will :-) > > > I created the table in SQLMODE ORACLE. How could I have > > changed it into Internal then? Why Do I find it in Internal mode? > > > The kernel stores this information but does not share it (at the present). > So you won't find this information in any of the system tables. > > > If the mode are totally equivalent (as more than one time I find in > > documentation and mails - only syntaxes differ), why there > > will be such a > > difference between internal and oracle mode? Are there other > > differences? > > > They are not totally equivalent. The thing is in your case that the DB > allows in SQLMODE ORACLE to define tables which records exceed the size > limit of a single db page of 8 kB. The DB checks this only at insertion > time (you won't be able to insert records which values exceed the size of 8 kB). > In SQLMODE INTERNAL you won't even be able to define such a table. > May be you can change the table definition in your source db in a way > that its records fit into a single db page? > > Regards, > Steffen > -- > Steffen Schildberg > MaxDB Team > SAP Labs Berlin > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
