mORMot Open Source

Slightly off topic but made qp fro delphi for the ZLib implementation, if someone cares, please vote and give more info: https://quality.embarcadero.com/browse/RSP-38978

-Tee-

Is code/tool still available somewhere?

All links seem to point something obsolete.

-tee-

Basically I do not care who takes the project when/if it comes alive

I just posted here if some company would reach back to me for it. Would be very pleased if it based off of mORMot.

Just offering (preminilary) business opportunity, to mORMot community.

Hope this makes it bit more clear.

Also trying to point out if this project goes live, I would try to influence that as much of it as possible is released as Open Source so community can benefit, if something along those lines is developed.

-Tee-

Size of problem for Programmers mainy, easy to start new project, couple of units in uses and that's it. But pain to go through, be SyCommons have lot of stuff most of users have not even seen

I would prefer unit scopes/namespaces but that would mean dropping quite many delphi versions (dotted filenames) mORMot.JSON.Utils /mORMot.UF8.Utils ... (or similar)

For older delphi versions  there would always be 1.18, so not the worst thing to drop all but pretty much patest delphi versions.

-Tee-

At this stage it would be too much of an question, I could open up the repository, maybe, and then someone could check it out.

But it would not be interactive way I would I'd liked it to be. Also I think it would be fun to chat with fellow programmer from somewhere else anyways.

-Tee-

Huh, Long time no see...

But I am back.

Even the very latest will hit to that same problem. It might depend upon Delphi settings (Maybe you can get around that in Delphi side), but at least in my configuration it always fails to compile that.

With default settings latest Delphi versions does not like few of the Units without the UnitScope. Winapi.Windows is required and some other also, can't remember which ones

-Tee-

This Video/Webinar is very important because of the Process.

Making small program and preferably enhance it in series of webinars. To further see the process.

It is like going into Paris and into the Louvre, look all the paintings, but it would be much more interesting to see how Leonardo Da Vinci actually painted the Mona Lisa.

It could be similar to FishFacts, and add some features to show off all the Good features of mORMot. And to actually show whole process from DataBase to the component on the screen.

Like I told in my post, because of mORMot flexibility and set of features, you can also easily make App that has worst possible structure

-Tee-

Hello,

I've been pondering that would be very helpful that someone would make "full" mORMot app on Youtube. Like Fisfacts with couple more features to show how app should be build from scratch.

IF you look at plain Demo it pnly shows the result but not the process. And YouTube-video could also tell what and why.

Or it could be series of videos how to add feature X.

But anyhow it would  far superior to just to have demo app and the result code.

Later could have WEB interface or Mobile etc.

I think best would be feature by feature Work in progress type of Webinar/Video to see best practices and would also see what kind of work it would be from day to day.

I started one hobby project and did some code for it, but then it hit me that I am not sure at all am I doing this in best possible mORMot way.

Video to go something like

1. Define some basics and units and so
2. Add some basic structure/Tables
3. Add some Data validity stuff Foreign keys
4. Add authentication
5. Add Feature X
6. Add feature Y

Hope this random rambling gives the idea what I would love to see. It could more than less show all bells and whistles of mORMot in one (set of) video(s). Maybe not all, but on app that would have Clitn, server an DB and authentication could be later.

-Tee-

OK,

I've am just familiar with FireBird and been using it, I like it in a way. I know it is not the fastest out there, but it is very simple to install and start using. FB3.x should be faster, but how much, time will tell. I see FireBird important also because of lot of Delphi code base have been using FB and InterBase for long time and changing the DB server is quite big decision.

For my this particular (hobby) project I am working on any OpenSource and Free DB Server is OK.

Which OpenSource database servers are supported without external libraries?

Main reason not to use Zeos for me that I try to limit the amount of external libraries to bare minimum.

-Tee-

OK,

It had info how to go around it, did not see it

I was just thinking that this is good to know, because sometimes caching the ID:s in the engine level is not good idea (If there are some other thingys accessing the DB, and you can't control that)...

I had system that looked up the pk values and so at the startup and it tool so long without the proper index... (There was pretty big tables)...

-Tee-

Hello,

Good to see that there are some cleanups, but I think it went little bit too fad,

Downloaded latest code (at the leaves) and now some files are missing, it might be release thing, but would be nice to get all latest files from there also. Like now some files changed the name, I need to get rid of old files so I know which files are deprecated... And after reapplying the (zip or what not) content to disk some are missing...

like :  sqlite3fts3.obj

Now I really do not know the best way top get working version. Because if I unzip the latest release I'll have extra files in the my local repository...

Any ways, which would be best way to get the latest files with the 1.18 "prerelease" version to the test...

-Tee-

Thanks...

Yes...

Way to create foreign key hierarchy between those  for those tables exist in the DB and maintaiunin/creating them from Delphi side (needed/possible) would be quite good life insurance.

It is very difficult to start fixing the DB after you've put something garbage in it... If your (user) code contains bug and you modify DB with wrong ID's you are big trouble...

Yes...

This might be the Right way to go for now...

Building factory, that supports all lazy load and so, would be quite difficult, maybe...

But Still i think that would be the way to go, way or other...
´....

btw... for us newbies would be good to have simplest possible demos to tinker around, to show what is to correct way to do certain feature.

Like one to many etc relation ships... Looking from documentation might take too much time and usually contains information which is not relevant on the Simplest possible solution (Or other way around maybe, documentation would bee too vast if all examples and code snippets would contain ready to run code...)

I wold also stress the importance of having GUI support maybe we users could start project on that, it would use Synopse code where it would be smart, (Like serialization code must contain code needed to get properties and fill them back again).

I would think that it should have few key features (Not too carefully thought out, so it might not be the optimal plan).

1. Fast
2. Easy interface (self explaining)
3. High level (Fallback) code formatters and parsers
3.1 Possibility to override the formatters and parser for different needs (Like Double might be money or so)
3.2 Possible to setup  parser for single property or some larger group
4. Possibility to register Mediators (The UI component handlers, I think they are called mediators )
4.2 Maybe single source file for mediator and maybe some standard collections for components that are in Single standard Delphi unit.
5. Some neat way to inform user (configurable and way to disable) that the value is not valid
5.1 There should be Regular expression validators and way to use something else also (Delphi code)
5.2 Possibility to update at least the regEx validators from the server side
5.3 Auto correct feature would be sweet. Some trivial would be that entering 0.10€ would be converted to 0,10€ automatically on my locale. It is very annoying if the UI will not help such trivial stuff, but again this should not be forced, and maybe again some neat way to inform user...
5.4 I've made some demo lib for some kind of value validation which used regular expressions, and it used some predefined background colors when possible, and some code I've found somewhere to pain subtle frame around the component depending is the value correct or not. It was few years back so I do not remember all details...

So what do you think? Would we able to start collaboration project on this??

-Tee-

Just to give some feedback... (And some more than less of an Off topic stuff )

This is just a problem (IMHO) if you are trying to fit mORMot to old program architecture. New one you can live with this, I think and most likely this decision makes many things better (at least I think it would be easier to at framework level this way).

So why to complain? I see not big reason to do so...

Files are Evil. Nice to give some non programmer (DB admin or program architect) job to do mapping with an XML-file etc, but this makes debugging really pain in the *rse... If mappin is done in code it is very easy to debug.

....

And last something my own ideas/rant...

I've tried to use little bit of the RemObjects Data Abstract, and I think it is good product for what is designed for, but falls short in many aspects.

Even if you are DB-expert (which I have been lucky to work with) are in more than less trouble with pretty simple SQL (By simple by I mean that what it does, not what it looks like). With AQL you can do what you like or know how to do. But very soon you have so complex SQL in your hands that it makes your life

My dream would be that I define the SQL sent to db-server with debuggable code. Best would be the way to chop it in pieces some how. Doing some queries with Ro-da the code was starting to be more than less as complex as the SQL, which is not good.

There should be tool that would simplify the process significantly.

Like defining the Query in a way that it is in logical parts, not just massive Fluent interface mess, which is very close to produced SQL. All the complexities of SQL should be hidden (I have no very good idea how it could be done), because if you can say something like.

1. Fetch these columns in these tables
2. the relation of these tables are ones I give you here
3. limit the result like this.

If you write an SQL for this, maybe join of an two tables, it already starts to be unreadable.

I was pondering while back, some kind of query builder, which would have two modes. the developement mode which would do most of the process in the client side. and programmer could analyze the resulted data more than less visually, but also by writing some kin d of unit tests or helper methods. (if data is known it would be easy to define cod that loops the dataset trough and does some tests on it).

And after you've debugged the client side part of it and it works, then it could be set to build the final SQL which does the complex SQL and let the DB.-server then return the just the data which is needed.

Because in some cases I've been thinking that time it takes to build these SQL's, would be cheaper (with not so good performance) to just load the bulk data (if not way too big) and do the filtering in Pascal-code at server and/or client level. Mainly because it is very very difficult to find the reason  why this and that behaves oddly in the SQL, but very easy to look trough the any kind of Dataset in Pascal code and define few if clauses and put needed rows in the other set of data. Might not perform super well, but at least you would feel that you know what is going on

Actually we did something like this, for static data, we made Hash tables of objects (of DB rows) with certain parameters and it was really  easy to figure out why something was not working as it should.

In few words what I am talking about is that easier it is to define the what data is going to be fetched from the server the better. I think even by making some Cached tables on the serverside which you make using pure pascal code is better than have monsters f queries that takes lot of time to change/develop and/or fix...

-Tee-

Hello,

Would it be possiblöe to refactor this functuionality out on some Commons unit. To it's own entity, so it would be more usable in programs that might not use mORMot

There are some cool stuff in mORMot, but could kind of publish some of the stuff in it's on entities, so they would be easy to use in app that will not use the rest of the library. Mainly the problem is that the unit name would not tell the other programmers the reaon why this mysterious SynSqliteMormotCommonsGlobalUtils.pas is included in the uses clause

Just my 0.02€

-Tee-