Re: [DOCS] ODBC encoding
On Mon, Jan 12, 2004 at 02:36:29PM -0500, Robert Treat wrote: > On Monday 12 January 2004 01:34, Karel Zak wrote: > > On Sun, Jan 11, 2004 at 11:43:07PM -0500, Robert Treat wrote: > > > On Thursday 08 January 2004 07:36, Karel Zak wrote: > > > > Hi, > > > > > > > > docs for 7.3 contains information how set client encoding for > > > > Windows > > > > ^ > > > > > > ODBC, but in docs for 7.4 I can't found it. Is it right? > > > > > > > > > > http://www.postgresql.org/docs/7.3/static/multibyte.html > > > > > > I think much of that section was rewritten into this: > > > http://www.postgresql.org/docs/current/static/multibyte.html > > > > Did you read my question? :-) > > > > I might be able to convince you I did, but I surely can't convince anyone I > answered it. I'm curious though...does the information from the 7.3 docs not > work for you? I don't work with ODBC/Win, but people who installed 7.4 don't found it in docs and asked about it in others lists. I have care about our good docs only, I was something like docs bugreport :-) Karel -- Karel Zak <[EMAIL PROTECTED]> http://home.zf.jcu.cz/~zakkr/ ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[DOCS] Experimental setup for XSLT processing
I've committed make rules and a stylesheet to try out processing the documentation via XSLT. You need to have a recent OpenSP and xsltproc installed. Then run "make testxml" in the "sgml" documentation directory and it should build HTML using XSLT stylesheets. Once we're satisfied with the results and the performance, I suppose we can consider using that as our primary method. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [DOCS] The Tutorial(TM)
2. The SQL Language 2.1. Introduction 2.2. Concepts 2.3. Creating a New Table 2.4. Populating a Table With Rows 2.5. Querying a Table 2.6. Joins Between Tables 2.7. Aggregate Functions 2.8. Updates 2.9. Deletions 3. Advanced Features 3.1. Introduction 3.2. Views 3.3. Foreign Keys 3.4. Transactions 3.5. Inheritance 3.6. Conclusion I'd be inclined to put aggregates, transactions, foreign keys, and views into the "intermediate" category, leaving only inheritance as "advanced". (Or maybe we should just drop inheritance from the tutorial.) You could possibly even argue that joins are intermediate instead of basic, although that's stretching it a bit. I agree with Peter's point that the first thing to teach is how to get data in and out. You could add triggers, rules into advanced features... You could also break joins up so that when talking about outer, left etc... it goes into advanced but basic "join on" or natural joins are in intermediate. J regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster -- Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC Postgresql support, programming shared hosting and dedicated hosting. +1-503-667-4564 - [EMAIL PROTECTED] - http://www.commandprompt.com PostgreSQL Replicator -- production quality replication for PostgreSQL ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
