on-rev reliability ?

[Pierre Sahores]

Le 10 juil. 2013 à 04:02, Rick Harrison a écrit :

> Hi Pierre,
> 
> Were you able to get phpPgAdmin to work correctly with
> the new version of PostgreSQL?  It keeps throwing
> permission errors at me when it tries to execute it's
> SQL code for queries etc.

phpPgAdmin works fine against my apps. About the permission sets, i suppose you mean the tables owners rights. While accessing the tables via phpPgAdmin needs to use the main on-rev account owner rights, i have the habit to create and grant dedicated sub owners to my different dbs to restrict securely the way my LC-server handlers interacts with PostgreSQL and in this way all works fine and as expected.

> So now we have to use "WHERE CAST" instead of "WHERE"?
> Who thought that would be better?

A simple and interesting PostgreSQL ascending compatibility glich, at least but, to the end, PostgreSQL stay indeed the rock-solid RDBMS it always went before, AKA 100% trustable/reliable to the end ;-)
> 
> Of course now I'm on the tio server so I guess my mileage may vary from yours.

Just be sure to have an eye on the version number of the PostgreSQL installation running on tio to know if you have to update your LC coding…

Best,

Pierre
> 
> Thanks in advance,
> 
> Rick
> 
> 
> On Jul 9, 2013, at 6:22 PM, Pierre Sahores <sc at sahores-conseil.com> wrote:
>> 
>> AFAIK, the PostgreSQL version installed on pancake (8.4.13) > the one i relied before on Loki (8.1.x) needed me to update some of my revDB calls to get my LC-Server apps OK. Was not a LC problem but a PostgreSQL one. If your LC-Server powered apps don't rely on a PostgreSQL backend, the problem should be elsewhere (MySQL ?) but in case of yes, see below what revDB call update went needed on my side, very simple to the end (all the statements containing a WHERE close have to be updated) :
>> 
>> What worked fine before against PostgreSQL 8.1.x :
>> 
>>> put "SELECT * FROM" && CustArticles && "WHERE article_chemin = '" & tparam2 & "'" into sqlStatement
>>> put revQueryDatabase(myDatabaseID,sqlStatement) into dbCursorID
>> 
>> 
>> need to become against PostgreSQL 8.4.13 :
>> 
>>> put "SELECT * FROM" && CustArticles && "WHERE CAST(article_chemin as TEXT) = '" & tparam2 & "'" into sqlStatement
>>> put revQueryDatabase(myDatabaseID,sqlStatement) into dbCursorID
>> 
>> Same kind of pg syntax update are needed against the DELETE … WHERE and UPDATE … WHERE statements.
>> 
>> That said, pancake is against my own LC-Server/PostgreSQL production apps (previously installed on loki) a very trustable and reliable platform with no down time at all (alike this seems to happen, time to time, against some other on-rev servers even if my own apps went running perfectly fine too when they went hosted on loki).
>> 
>>> widestep
>>> 
>>> Uptime	Outages	Response time
>>> 100.00%	1	462 ms
>>> 
>>> Downtimes
>>> 
>>> From	To	Downtime
>>> 2013-06-12 12:13:27	2013-06-12 12:14:27	0h 01m 00s
>>> 
>>> This is a scheduled report from Pingdom. If you wish to no longer receive this report you can unsubscribe by logging in to My Pingdom and update your email report settings.
>>> 
>>> 
>>> Copyright © 2013 Pingdom AB
>> 
>> HTH,
>> --
>> Pierre Sahores
>> mobile : 06 03 95 77 70
>> www.sahores-conseil.com
>> 
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode

--
Pierre Sahores
mobile : 06 03 95 77 70
www.sahores-conseil.com