I did not. I meanty sql calls, but you are correct, object fields need to be handled in a different way. That is why I never use object fields. I do not think 4D should ever create field types that work in 4D but not in SQL or vice versa. I will not use them no matter how cool they may be. There are also SQL data types that 4D does not know about. In case of table with object data type, I would export that table in 4D format in then import.
Whether you use import or sql calls to get at data, you can use database setting to turn off indexing while saving the data. I would do this and then turn on indexing between each table Regards and thanks for the reminder about object fields Chuck On Thu, Jul 26, 2018 at 12:44 PM, John DeSoi via 4D_Tech < 4d_tech@lists.4d.com> wrote: > > > > On Jul 26, 2018, at 11:21 AM, Chuck Miller via 4D_Tech < > 4d_tech@lists.4d.com> wrote: > > > > Sometimes it is better to use sql to recreate data file. Now that v16 > handles blob arrays it is very fast. > > If you mean SQL EXPORT DATABASE, it will not work if the database has > object fields. > > John DeSoi, Ph.D. > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** > -- ----------------------------------------------------------------------------------------- Chuck Miller Voice: (617) 739-0306 Fax: (617) 232-1064 Informed Solutions, Inc. Brookline, MA 02446 USA Registered 4D Developer Providers of 4D, Sybase & SQL Server connectivity http://www.informed-solutions.com ----------------------------------------------------------------------------------------- This message and any attached documents contain information which may be confidential, subject to privilege or exempt from disclosure under applicable law. These materials are intended only for the use of the intended recipient. If you are not the intended recipient of this transmission, you are hereby notified that any distribution, disclosure, printing, copying, storage, modification or the taking of any action in reliance upon this transmission is strictly prohibited. Delivery of this message to any person other than the intended recipient shall not compromise or waive such confidentiality, privilege or exemption from disclosure as to this communication. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
