Ok but with some bugs here and there, granted. That said, you can see
the site and use many parts of it.
I guess I must submit the patches to sourceforge?
One of the current problems I have is with persistent connections.
In Utility.pm, the part that defines the sqlConnect and checks for an
existing connection makes my apache segfault... I have no idea why, I
don't know if it's a bug that is due to a slash-postgresql related bug
or not. In any case, when I remove that part between
#Ok, first let's see if we already have a connection
and
#Ok, new connection, let's create it
it works well. The problem is, correct me if I'm wrong, the connection
isn't persistent anymore, right? That's a performance serious prob.
In order to correct this, I have to understand the mechanism behind
this. One of the things that troubles me is the structure of the $self
object used. PLEASE one of the developers who's familiar with
slashcode's internals save me sometime, personal life aside, I have both
a job and a university to work for too, so I can't spend a full day
searching everytime I need to understand a little problem. I'm only
asking for pointers, i.e. tell me where I can find the given info (I
would even be grateful for a "take a look at file xxx or read page/url
xxxx").
Best regards,
Chahine
PS: the sqlReplace is a headache to recode, I think it's easier to
recode every function that uses it instead... any better idea?
|
