[geeklog-devel] FrOSCon 2009

[Vincent Furia]

Joe, at least the two problems you mention below I caught as well. Stan has
fixed the DB_save and removed the print and echo debugging statements. I
haven't thoroughly tested the (new) DB_save yet.

-Vinny

On Mon, Aug 24, 2009 at 10:59 PM, Joe Mucchiello <joe at throwingdice.com>wrote:

> At 05:07 PM 8/24/2009, Dirk Haun wrote:
>
>> Let's see what I can remember from our visitors: The (upcoming) Postgres
>> support was well received. One person even went ahead and checked out
>> Stan's repository (and came back the next day to report that it didn't
>> work for him - we're still in contact trying to figure out what went
>> wrong).
>>
>
> When this was first announced I gave the new code a quick review and I
> remember thinking some of the implementations were a bit off just from
> looking at them. I haven't had a chance to get another look at it since. (I
> want to add pgsql support to my version of the calendar before I release a
> new version.) You might want to look at the implementation of
> pgsql.class.php. For example, his implementation of dbSave() does not
> duplicate the functionality of mysql's REPLACE INTO whereas the mssql
> implementation goes to great pains to do so. Also there are some stray
> echo's and print_r calls in the file from the initial release. (I don't know
> if they've since been removed.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist8.pair.net/pipermail/geeklog-devel/attachments/20090825/7b0c3459/attachment.html>