mORMot Open Source

That is it, TrimControlChars(), worked.
I didn't know about this function thank you.

But, just thinking, if the data that I've provided is considered valid, shouldn't we add a TrimControlChars() call in Base64 functions before conversion?
I've asked the guy and we tested using Java.util (built-in) and Apache commons. Both add line feed in the output...

Of course I've test and it still doesn't working.

        pdf := StringReplaceAll(docs._[i].S['pdf'], #13#10, '');
        //FileFromString(DecodeBase64(pdf), fn, True);
        FileFromString(Base64ToBin(pdf), fn, True);

I couldn't send the private PDF so, I asked the other part to make a fake one.

Here https://gist.github.com/mdbs99/fb6ddf23 … 2fff7a82f7

The structure is:

<Parametros>
  <docs>
    <doc>
      <nome>filename</nome>
      <pdf>base64</pdf>
    ...
</Parametros>

Sure. But in that transition to 2.0, would be nice to have a batch script to copy this unit from 2.0 to 1.8 — renamed, following unit name pattern of 1.8, I presume.

I think they don't like code that may not work in all platforms which FPC cover.

Hello,

Packages have been included and now I'm trying to add it in Online Package Manager (OPM).
I've already asked about the author but it seems that he has an issue to compile.

It looks like something related with the version. I'm using Lazarus 2.1.0 r59757M FPC 3.3.1.

Someone knows if we can compile mORMot using FPC 3.0.4, at least the base package?
If it's not possible now, can we make some changes to do it?

I think they only accepted packages that run in the current FPC version.

--

EDIT: he added, but is good to have it working on current version of FPC.

I have just one place, just one Synopse.inc.
Using `a71a5d9b84ad99448cde64396403290c00c196dc` (the previous one) works.

Please, what FPC/Laz revisions are you using on Windows?

I read "Release Notes-7.2.4-stable.pdf" and they wrote that we need to move on from ntwdblib.dll to ADO or FreeTDS, which is a old tech so, that is good.

I will ask them about these changes and tuning but one more question:
The SourceForge SVN is it currently compatible with FPC 3.0.4?  I believe you can answer if you use MSSQL. I don't want to use a "non-updated-forked" branch which has some patches just for FPC... I would like to use the official one.

Thank you.

I believe you can use `SET NOCOUNT ON` before all these instructions.

Good to know.

Hello Leslie7
Actually, FPC already has a XPATH implementation... but this project could be interesting. Thanks for the tip.

Touché!

Thanks. But, in my case, I'm referring about MS SQL Server.
I would like to access MS SQL directly and many tables, on a specific system, don't have ID as integer, only uniqueidentifier type as primary key.

It's strange do not have anyone complain about missing XML.
Many companies use WebServices and XML is the mostly used.

All right.
But, as I have many systems that works with XML, what is the simplest way to use mORMot to work with?
In mostly cases, I need to receive a XML, parse (using XPATH), create a new one, and send it back.
I mean, is that possible (and fast) to use some mORMot "XML to JSON" functions, parse the JSON, create a new one, and use "JSON to XML" to send it as XML at the end?

I've been thinking and my conclusion is the same as you had, I believe, years ago:
Even when packages provide a improvement at developing — simplifying the dependencies paths in user projects — it's simpler do not create packages in main source. Let this "specialization" to the users (developers) in their local computer.

I've tried to make a simple lib compatible with Delphi and Lazarus and it was a pain make changes in both source packages.

However, the new Online Package Manager for Lazarus won't work without a package. Tradeoffs...

Anyway, mORMot is changing my thoughts. Thanks for that.

Indeed, I use more FPC/Lazarus for new projects than Delphi.
I have just one employer that still works with Delphi 7 and that is the version that I use.

Anyway, I like this simplest approach. But, I would like to understand the pros and cons.

I know it could be a pain to change every package version for each Delphi version —in Lazarus we need just one — but can't you see any pros?