Re: interactive pgsql book
That is quite interesting. Let me CC this over to the hackers/docs
lists to see if we want to do this for our main docs.
As for my book, I want those messages sent to me so I can fix them or
add information to the book. I think maybe we want the same thing for
the manuals. We want to get suggestions so we can compile them into the
manuals and add to them, rather than having comments, but I am
interested to hear what others say.
Hi
First: I'm looking forward to buying the PostreSQL book when it's
published.Have you thought about making the book interactive, so other people can
contribute/discuss to the book.
It can be made with PHP4 and PostreSQL 7 - of course :-)You could possibly remove irrelevant/annoying postings.
The book would be better, because you'd get more feedback.
Look at this as an example:
http://www.php.net/manual/ref.pgsql.phpWhat do you think?
I'm not a PHP programmer, but I've just managed to make a query to
PostgreSQL using PHP :-)
On the other hand, I'm a experienced Cold Fusion programmer, so it will
be easy to learn PHP.I wouldn't mind using some of my spare time to implement this neat
function.Poul L. Christiansen
--
Bruce Momjian | http://www.op.net/~candle
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Import Notes
Reply to msg id not found: 392BAB82.D8496DEC@faroenet.fo
Benjamin Adida wrote:
on 5/24/00 12:02 PM, Vince Vielhaber at vev@michvhf.com wrote:
On Wed, 24 May 2000, Bruce Momjian wrote:
That is quite interesting. Let me CC this over to the hackers/docs
lists to see if we want to do this for our main docs.As for my book, I want those messages sent to me so I can fix them or
add information to the book. I think maybe we want the same thing for
the manuals. We want to get suggestions so we can compile them into the
manuals and add to them, rather than having comments, but I am
interested to hear what others say.By "interactive" I ass/u/me Poul is referring to PHP's annotated manual.
I've found that to save me HOURS due to oddball little quirks that someone
else discovered first and noted in the annotated docs.I'd not only support this, if it's wanted I'll make sure it's implemented.
I'm not trying to start any kind of war, but since OpenACS is being
considered for community management already, it can automatically set up
HTML file annotation with no extra effort. All you do is add the HTML files
to the doc directory and sync up with the database (one click), and you've
got user-contributed annotations (with moderation if you so desire).This is similar to Philip Greenspun's photo.net docs.
-Ben
If OpenACS has the features that I've mentioned, then I see no need to re-invent
the wheel.
When will we be able to use OpenACS?
- Poul L. Christiansen
Import Notes
Reference msg id not found: B5517988.44DC%ben@mit.edu | Resolved by subject fallback
On Wed, 24 May 2000, Bruce Momjian wrote:
That is quite interesting. Let me CC this over to the hackers/docs
lists to see if we want to do this for our main docs.As for my book, I want those messages sent to me so I can fix them or
add information to the book. I think maybe we want the same thing for
the manuals. We want to get suggestions so we can compile them into the
manuals and add to them, rather than having comments, but I am
interested to hear what others say.
By "interactive" I ass/u/me Poul is referring to PHP's annotated manual.
I've found that to save me HOURS due to oddball little quirks that someone
else discovered first and noted in the annotated docs.
I'd not only support this, if it's wanted I'll make sure it's implemented.
Vince.
Hi
First: I'm looking forward to buying the PostreSQL book when it's
published.Have you thought about making the book interactive, so other people can
contribute/discuss to the book.
It can be made with PHP4 and PostreSQL 7 - of course :-)You could possibly remove irrelevant/annoying postings.
The book would be better, because you'd get more feedback.
Look at this as an example:
http://www.php.net/manual/ref.pgsql.phpWhat do you think?
I'm not a PHP programmer, but I've just managed to make a query to
PostgreSQL using PHP :-)
On the other hand, I'm a experienced Cold Fusion programmer, so it will
be easy to learn PHP.I wouldn't mind using some of my spare time to implement this neat
function.Poul L. Christiansen
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net
128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
on 5/24/00 12:02 PM, Vince Vielhaber at vev@michvhf.com wrote:
On Wed, 24 May 2000, Bruce Momjian wrote:
That is quite interesting. Let me CC this over to the hackers/docs
lists to see if we want to do this for our main docs.As for my book, I want those messages sent to me so I can fix them or
add information to the book. I think maybe we want the same thing for
the manuals. We want to get suggestions so we can compile them into the
manuals and add to them, rather than having comments, but I am
interested to hear what others say.By "interactive" I ass/u/me Poul is referring to PHP's annotated manual.
I've found that to save me HOURS due to oddball little quirks that someone
else discovered first and noted in the annotated docs.I'd not only support this, if it's wanted I'll make sure it's implemented.
I'm not trying to start any kind of war, but since OpenACS is being
considered for community management already, it can automatically set up
HTML file annotation with no extra effort. All you do is add the HTML files
to the doc directory and sync up with the database (one click), and you've
got user-contributed annotations (with moderation if you so desire).
This is similar to Philip Greenspun's photo.net docs.
-Ben
Vince Vielhaber wrote:
By "interactive" I ass/u/me Poul is referring to PHP's annotated manual.
I've found that to save me HOURS due to oddball little quirks that someone
else discovered first and noted in the annotated docs.
i'd have to agree 100% with this. i use php and i've had much the same
experience. as a matter of fact, i think i commented to tom lockhart
about this a long time ago when i was having some problem understanding
how setting up alternate database locations worked. it fills a
different role than a FAQ & it's a lot easier than searching mailing
lists (even when the list search is working). it seems like there are a
lot of quirks that are non-intuitive to a lot of users (e.g., recently i
was having trouble getting an index to be used on a query and realized
that i needed to add an explicit typecast on the query) that aren't
covered anywhere, maybe even not in the mailing lists.
jeff
Bruce Momjian <pgman@candle.pha.pa.us> writes:
Have you thought about making the book interactive, so other people can
contribute/discuss to the book.
It can be made with PHP4 and PostreSQL 7 - of course :-)
...and with the OpenACS version of the ArsDigita Community System and
PostgreSQL -- of course! :-) See <http://www.openacs.org/>.
-tih
--
This is the Unix version of the ILOVEYOU worm, and in the spirit of such, it
depends on the user community to propagate. Please send this message to all
of your friends and randomly delete numerous files from your system. Thanks!
Import Notes
Reply to msg id not found: BruceMomjiansmessageofWed24May2000111738-0400EDT