I think I do... It's called OpenACS :)
On Wed, 2008-04-02 at 20:49 +0100, Xavier Bourguignon wrote:
Hi All,
Does anybody know what is required to use OpenAcs DB API for
accessing Postgres DB within aolserver?
Thank you
--
AOLserver - http://www.aolserver.com/
To Remove yourself from
You can probably just steal the db code from OpenACS.
Jade
On Wed, Apr 2, 2008 at 1:44 PM, Andrew Piskorski [EMAIL PROTECTED] wrote:
On Wed, Apr 02, 2008 at 02:39:57PM +0100, Xavier Bourguignon wrote:
Ok, so how do I get this OpenACS db_* AP to work?
You would have to install OpenACS:
thank you all for the info.
Jeff, I have been using your code and adapted it to my needs, thanks for that.
On 02/04/2008, Juan José del Río (Simple Option)
[EMAIL PROTECTED] wrote:
I think I do... It's called OpenACS :)
On Wed, 2008-04-02 at 20:49 +0100, Xavier Bourguignon wrote:
Hi
Hi all,
I just want to thank you for the information provided, very useful.
On 03/04/2008, Jade Rubick [EMAIL PROTECTED] wrote:
You can probably just steal the db code from OpenACS.
Jade
On Wed, Apr 2, 2008 at 1:44 PM, Andrew Piskorski [EMAIL PROTECTED] wrote:
On Wed, Apr 02, 2008 at
Ok, this may not be an aolserver problem, but maybe an OS problem, but
at the moment, when I set a cookie, I set it to live for 1 minute
only.
Now here is the problem.
If I look at my cookie in firefox, it says that cookie will expire in
1 hour and not 1 minute.
I have checked the datettime on
One minute is probably too short a time, the computer clocks on client and
server would have to be very close, and being off by a minute isn't uncommon.
Anyway, maybe show what you are doing instead of describing what you are
doing. How is the cookie duration set, what does the Set-Cookie
Can you show the code on how you are setting the cookie?
Setting a time using the old style netscape cookie spec is entirely
unreliable as it depends on the client's computer clock being accurate.
I don't find timed cookies very useful in any case and only ever use
no time-out (i.e.:
On Apr 2, 2008, at 5:42 PM, Bas Scheffers wrote:
The only issues I ever faced was (CSV) file uploads, where the data
needed to be extracted and put into the database. This could
contain any encoding without me knowing. In practice it only ever
contained stupid Windows encoding, so I
On Thu, Apr 3, 2008 at 4:14 PM, Cynthia Kiser [EMAIL PROTECTED] wrote:
H CSV + stupid Windows encoding. Bas perhaps you have just what I
need for a character set issue. I have a data file - actually delimited by
upsidedown exclamation points, not commas.
It never occurred to me to try
On 04/04/2008, at 8:44 AM, Cynthia Kiser wrote:
It never occurred to me to try parsing this with Tcl instead. Is
there an AOLserver or straight Tcl module I should be using to parse
pseudo-CSV? Or is the answer keep it simple and just read lines and
split on ¡ with 'split'?
Tcl lib has a
I echo Bas here. The only issue I've ever had is when writing to or reading
from files. You have to specify the encoding.
Jade
On Thu, Apr 3, 2008 at 3:14 PM, Cynthia Kiser [EMAIL PROTECTED]
wrote:
On Apr 2, 2008, at 5:42 PM, Bas Scheffers wrote:
The only issues I ever faced was (CSV)
11 matches
Mail list logo
