Hi All,

In fact, it seems that it has been a little misunderstanding in this case of 
XML Structure. What LR was talking about is the NEW way which has been 
demonstrated by Laurent Esnault during the Summit.

With the new way of handling the 4DB (usually named 'the structure'), it will 
be possible to save everything into text files. Forms will be JSON files, 
Methods will be Text files, and Structure will be XML Files. And you will be 
able to export and reimport any part. And this is what Laurent explained.

I perfectly understand that you are dreaming so hard of it, that you want to 
believe that it is already available! But in fact you will have to wait a 
little bit more, until it will be fully tested and introduced into a R-release.

Sorry about breaking your dreams, but this is the way it works.

And, BTW, I have also to confess that Santa Claus doesn't exist...

My very best,


> On 11 Apr 2018, at 07:57, 4d_tech-requ...@lists.4d.com wrote:
> I suggest you mention JPR in this message so that JPR will see it and
> perhaps pass your comments along :)
> Pat
> On 10 April 2018 at 22:33, Tim Nevels via 4D_Tech <4d_tech@lists.4d.com>
> wrote:
>> On Apr 10, 2018, at 12:40 PM, Randy Engle wrote:
>>> I tried this from several different angles (16r6)
>>> Import XML Structure works like importing records.
>>> It doesn't "update" or "merge", just imports new structure elements
>> (Tables)
>>> Perhaps Laurent was confused at that moment?
>> You are right Randy.  I did some quick tests and IMPORT STRUCTURE command
>> will not update existing tables. The documentation says "If an imported
>> table has the same name as a local one, an error is generated and the
>> import operation is aborted.” and this is the case.
>> So Laurent must have been confused and maybe thought, why create fields
>> with SQL when you could create tables and fields with the IMPORT STRUCTURE
>> command. You can do that, but what we want to do is update existing tables
>> and fields and that is currently not possible with this command.
>> So we are stuck again with the inability to set the “map NULL values to
>> blank” field property when creating fields with SQL.
>> Tim
>> Tim Nevels
>> timnev...@mac.com <mailto:timnev...@mac.com>
>> Innovative Solutions
>> 785-749-3444

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com

Reply via email to