On Fri, 29 Nov 2019 01:52 -05:00, Alexander Burger wrote:
> Wow beneroth,
>
> this is a fantastic and overwhelming piece of analyzis! Thanks a lot!
>
> Perhaps this should be put as an article into the wiki?
I second that. beneroth is the man! :) Tour de force! Thanks, mate!
--
UNSUBSCRIBE:
Wow beneroth,
this is a fantastic and overwhelming piece of analyzis! Thanks a lot!
Perhaps this should be put as an article into the wiki?
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Thanks a lot Beneroth,
You have provided a lot of good information. A number of dimensions to do
the comparison - it will take me a couple of more reads before I can
assimilate all the information.
Regards,
Kashyap
On Thu, Nov 28, 2019 at 3:14 PM wrote:
> By the way, the often used the argument
By the way, the often used the argument "ORM allows to switch from one
(SQL) database to another" is illusory.
In practice such a switch happens very rarely, and when it does it
usually still needs much debugging and changes to the existing
application because the different DBMS just work to diffe
Hi Kashyap,
I've a bit experience with ActiveRecord and some more with EntityFramework.
As said in the other responses, the big fundamental difference between
PicoLisp database architecture and ORMs is that in PicoLisp the
application layer and the database layer is the same layer, it is not
two
Thanks Mattias,
Yeah, intuitively, I do feel "symbols all the way down" makes Picolisp
uniquely at an advantageous position. It would be good to be equipped with
a way to articulate this advantage.
Regards,
Kashyap
On Thu, Nov 28, 2019 at 11:28 AM Mattias Sundblad wrote:
> Hi Kashyap!
>
> Thank
Hi Kashyap!
Thank you for posting many good examples on the mailing list, and
welcome to the PicoLisp world!
> There is a plethora of ORM systems such as ActiveRecords (in Ruby/Rails) or
> Microsoft EntityFramework and similar solutions in other languages where
> Objects are mapped to SQL DB reco
Hi Alex,
There is a plethora of ORM systems such as ActiveRecords (in Ruby/Rails) or
Microsoft EntityFramework and similar solutions in other languages where
Objects are mapped to SQL DB records.
I'd love to know your thoughts about how PicoLisp's approach is
similar/different from them.
Regards,
