MC front end to PostgreSQL

[Pierre Sahores]

Sadhunathan Nadesan a écrit :
> 
> | Just as you say, Alain and we, all, are going to open "l'avenue des
> | Champs-Elysees" to the web-dedicated metacard developments.
> | "Because they did'nt know it was impossible,..." ;-)
> |
> | > > Do you mean you will distribute MC
> | > > stacks and the user won't go through a browser?
> | >
> | > You certainly can.
> | >
> | > Let's conquer the Web with MetaCard,
> | >
> | > Alain Farmer
> 
> Hi Guys,
> 
> Again, pardon my late entry here, but I'm hoping to keep this topic
> alive.  I had asked Pierre before about a working application to look at.
> It appeared that what he showed me (if I correctly understood) was all
> server based, with HTML, and MC as a background CGI language.  Meaning,
> he had a cool site where you could look up authors and books and stuff
> (sorry, my French isn't really very good, so pardon the guesswork) which
> had browswer, maybe PHP forms - calling CGI scripts written in MC which
> in turn invoked shell commands to do SQL stuff with Postgres.
> 
> Very nice.  I was hoping to see something a bit different.  A sort of
> real data base application.  Across the net.
> 
> In other words, something where the front end is running on the client
> (an MC app) and the back end is a data base across the web on the server.
> Something with rich a interactive nature, the kind of application you
> can build native with MC for strictly local use.
> 
> Such as, you bring up the stack and it displays all the fields in the
> current record.  You click next, next, next buttons and it is paging
> through .. not cards in your stack, but records in  your data base on
> the back end.  You want to change something, you just change it, press
> the update button, and the back end data base is updating.  Without,
> hopefully, having to hand code a lot of SQL statements to make everything
> work, but if so, so be it.
> 
> Anyone have anything like that happening?

Yes ! I'm building such Metacard based client apps and, with a back-end
database server available (PostgreSQL, for me), you can do same in using
(in addition to the server-side code we spoken about some weeks ago in
this thread) such kind of code to do this client speak with the back-end
server in using the "POST" method :

    put "&SQL=" & urlencode(fld "Request") into larequete
    put "id1=data1&id2=data2&id3=data3" & larequete into retour
    set httpheaders to "Content-type: application/x-www-form-urlencoded"
& return
    post retour to url (fld "csrecents" of cd 2 & "wmc.xml")

where id1, id2 and id3 are contextual parameters and the field "Request"
can hold a direct SQL query or client-side fields contents to be passed
to the database server trought the metacard server-side cgi or was.

> Mahalo
> Sadhu
> _______________________________________________
> metacard mailing list
> metacard at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/metacard

-- 
Cordialement, Pierre Sahores

Inspection académique de Seine-Saint-Denis.
Applications et bases de données WEB et VPN
Qualifier et produire l'avantage compétitif