Re: [AOLSERVER] AOLserver Postgres Driver (2.3.0)
On Saturday 28 September 2002 09:38 pm, Daniel P. Stasinski wrote: > This should also go on the site (AOLserver Postgres Driver v2.3.0). Ours > is still old and crashes the server. Scott has, I believe, refactored the AOLserver Postgres Driver somewhat. My recommendation is to sync the two, and fix the bug that had the patch issued earlier. Scott, if you would like I can take a look at that this week. AFAIK I still have commit privileges on AS CVS on SF. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
Re: [AOLSERVER] AOLserver Postgres Driver (2.3.0)
Yes, I had imported an older version of postgres.so from the OpenACS, but haven't had time to work on it. I'm probably going to start from scratch with a fresh copy from OpenACS and import it. I want to centralize the AOLserver modules to one location, but not sure the OpenACS folks would be satisfied maintaining it at SourceForge, since they already have their own software development manager. /s. On Sat, 28 Sep 2002 18:38:38 -0700, "Daniel P. Stasinski" <[EMAIL PROTECTED]> said: > This should also go on the site (AOLserver Postgres Driver v2.3.0). > Ours is > still old and crashes the server. > > http://openacs.org/sdm/download-package-release.tcl?package_id=2&release_id= > 60 > > or in case that didnt format correctly, try this: > > http://oneweek.org/qk > > Daniel > -- Scott Goodwin [EMAIL PROTECTED] http://scottg.net
Re: [AOLSERVER] AOLserver Postgres Driver (2.3.0)
What I had actually done was refactor the parts out into separate files. Not sure it was the best cut, and the two are certainly badly out of sync because of me. Other than cosmetic changes though, I haven't really changed the way it operates. So starting with a fresh copy of the OpenACS dist would probably be much easier. The biggest problem is: will the OpenACS crew let me take the OpenACS postgres module, refactor it and then use that refactored copy, maintaining it at SourceForge? I realize OpenACS has a terrific SDM, but I think the AOLserver C modules should be maintained and distributed from a central location, and that would be SourceForge. If the OpenACS folks continue with their version of postgres.so, that's fine, but I hate to see two separate modules whose only real differences may be cosmetic. /s. On Sat, 28 Sep 2002 22:08:15 -0400, "Lamar Owen" <[EMAIL PROTECTED]> said: > On Saturday 28 September 2002 09:38 pm, Daniel P. Stasinski wrote: > > This should also go on the site (AOLserver Postgres Driver v2.3.0). Ours > > is still old and crashes the server. > > Scott has, I believe, refactored the AOLserver Postgres Driver > somewhat. My > recommendation is to sync the two, and fix the bug that had the patch > issued > earlier. Scott, if you would like I can take a look at that this week. > AFAIK I still have commit privileges on AS CVS on SF. > -- > Lamar Owen > WGCR Internet Radio > 1 Peter 4:11 > -- Scott Goodwin [EMAIL PROTECTED] http://scottg.net
Re: [AOLSERVER] AOLserver Postgres Driver (2.3.0)
On Sun, Sep 29, 2002 at 04:24:29AM +, Scott Goodwin wrote: > > The biggest problem is: will the OpenACS crew let me take the OpenACS > postgres module, refactor it and then use that refactored copy, > maintaining it at SourceForge? I realize OpenACS has a terrific SDM, > but I think the AOLserver C modules should be maintained and > distributed from a central location, and that would be SourceForge. If > the OpenACS folks continue with their version of postgres.so, that's > fine, but I hate to see two separate modules whose only real > differences may be cosmetic. Hi Scott, I want to say a huge _thank you_ for becoming the unofficial AOLserver-tree community liason. It's great work that you're doing and I'm really glad that it is happenning. It is so exciting to see this flurry of new modules, and best of all, seeing them imported into the tree (after revision) and having their maintainers with commit privs. As for the PostgreSQL driver, I have submitted this question to the OpenACS bboards. If the official driver maintainer has commit privs, then I'm all for it being in the main tree. http://openacs.org/bboard/q-and-a-fetch-msg.tcl?msg_id=0006Qq&topic_id=11 -Roberto -- +|Roberto Mello -http://www.brasileiro.net/ |--+ + Computer Science Graduate Student, Utah State University + + USU Free Software & GNU/Linux Club - http://fslc.usu.edu/ + Ithinkmyspacebarstoppedworking.
Re: [AOLSERVER] AOLserver Postgres Driver (2.3.0)
> I want to say a huge _thank you_ for becoming the unofficial > AOLserver-tree community liason. It's great work that you're doing and > I'm > really glad that it is happenning. It is so exciting to see this flurry > of > new modules, and best of all, seeing them imported into the tree (after > revision) and having their maintainers with commit privs. One day, not long ago, I found myself listed as an Admin instead of a developer of the AOLserver SourceForge area. I didn't ask for it, and nobody told me about it, so I think it's a boo-boo, and that once I'm found out, I'll be demoted back to Developer. Until then, I'll see what I can do to bring some consistency to the AOLserver SF area. Absolute power corrupts absolutely (sound of me with a very deep, baritone, evil laugh -- WHAHAHAHA). > As for the PostgreSQL driver, I have submitted this question to the > OpenACS bboards. If the official driver maintainer has commit privs, > then I'm all for it being in the main tree. I think anyone who has developed a module or contributed significantly deserves commit status. I believe the unwritten rules are these: - if it's for the core server, make it a patch and submit it for the AOL dev team to integrate - if it's for a module, the module maintainer should decide if they want changes submitted as patches to SF or if they'd rather you make changes to the module directly. -- Scott Goodwin [EMAIL PROTECTED] http://scottg.net
