and now for something completely different

hi again :)

oops, wrong button clicked. that wasn't the "attach" button. i'm sorry.
here is the file.

regards,
Miha
Index: docs/de_DE/hints/view-without-pk.html
===================================================================
--- docs/de_DE/hints/view-without-pk.html    (revision 4632)
+++ docs/de_DE/hints/view-without-pk.html    (working copy)
@@ -14,7 +14,7 @@
 Das Einf�gen von neuen Zeilen oder die �nderung existierender Zeilen mit dem Edit Data Tool ist ohne
 Prim�rschl�ssel nicht m�glich.
 </p>
-</p>
+<p>
 Um Daten editieren zu k�nnen, erfordert pgAdmin III einen Prim�rschl�ssel auf der Tabelle, was i.d.R. ohnehin
 im Rahmen eines guten Datenbankdesigns vorhanden sein sollte.
 Alternativ kan die Tabelle auch WITH OIDS angelegt werden. Bitte beachten da� Eindeutigkeit von OIDs <B>nicht</B>
Index: docs/en_US/hints/view-without-pk.html
===================================================================
--- docs/en_US/hints/view-without-pk.html    (revision 4632)
+++ docs/en_US/hints/view-without-pk.html    (working copy)
@@ -13,7 +13,7 @@
 Since the table <INFO> doesn't have a primary key or OIDs, you can view the data only.
 Inserting new rows and changing existing rows isn't possible for the Edit Data tool without primary key.
 </p>
-</p>
+<p>
 In order to edit data, pgAdmin III requires a primary key on the table, which is a good database design practice
anyway.
 Alternatively, the table can be created WITH OIDS. Please note that oids are <B>not</B> guaranteed to be unique over a
very 
 long period of time, so using oids as kind-of primary key is only second choice.
Index: docs/en_US/hints/fki.html
===================================================================
--- docs/en_US/hints/fki.html    (revision 4632)
+++ docs/en_US/hints/fki.html    (working copy)
@@ -13,8 +13,8 @@
 </p>
 <p>
 It all starts with a master table, which will be the referenced table. It needs to have a primary key (well, actually
the 
-referenced columns only need to be not null and covered by a unique index, but it's really good advise to have it a
-primary key. The slave table depends on the master table, in the sense that the columns on which
+referenced columns only need to be not null and covered by a unique index, but it's really good advice to have a
+primary key). The slave table depends on the master table, in the sense that the columns on which
 the foreign key is created must match the master table for any key inserted or updated. The slave table is the
referencing
 table of the foreign key.
 </p>
Index: docs/en_US/hints/pk.html
===================================================================
--- docs/en_US/hints/pk.html    (revision 4632)
+++ docs/en_US/hints/pk.html    (working copy)
@@ -24,7 +24,7 @@
 </p>
 <p>
 If you look at PostgreSQL's system tables, you will find that none of them has a primary key, so what's this about?
-Actually, All of these tables have one or two columns (usually OID only) which uniquely identifies each row, obeying
the
+Actually, all of these tables have one or two columns (usually OID only) which uniquely identifies each row, obeying
the
 second rule for a primary key, not allowing zero, and being covered by an index for faster access. Usage of OIDs has
 historic reasons, and isn't really first choice for designing user tables. PostgreSQL still uses this for backwards
compatibility, 
 and while a newer approach would probably use explicit primary keys it won't be changed now any more.
Index: docs/en_US/tips.txt
===================================================================
--- docs/en_US/tips.txt    (revision 4632)
+++ docs/en_US/tips.txt    (working copy)
@@ -41,6 +41,6 @@
 pgAgent can be used to schedule regular batch and SQL jobs, such as the re-creation of date-sensitive partial indexes,
orpurging of old records. 
 It is good practice to build application logic into the database itself by using functions and views. This ensures
thatdifferent front-ends to your products will always see the same views of data and update and modify data in the same
way.Better yet, you only have to write it all once for all front-ends! 
 To help keep your databases secure, minimise the amount of access you allow to remote hosts when creating your
pg_hba.conffile, and always use encrypted connections unless you have good reason not to. 
-You can restrict access to individual columns of a table for a particular user or group by denying them drect access
toit, and creating a view containing only the columns they should see for them to use instead. If your users need to
updatethe data, you can create rules to apply updates to the view to the base table instead. 
+You can restrict access to individual columns of a table for a particular user or group by denying them direct access
toit, and creating a view containing only the columns they should see for them to use instead. If your users need to
updatethe data, you can create rules to apply updates to the view to the base table instead. 
 PostgreSQL has been run on diverse platforms such as the Microsoft X Box, Sony PlayStation II, and Sharp Zaurus PDAs!
 EnterpriseDB donated an Apple Powerbook to the pgAdmin project to help improve the Mac OS X port of pgAdmin and their
simplifiedderivative product, EDB Studio.  
Index: docs/sl_SI/tips.txt
===================================================================
--- docs/sl_SI/tips.txt    (revision 4632)
+++ docs/sl_SI/tips.txt    (working copy)
@@ -2,7 +2,7 @@
 # Prazne vrstice se prezrejo, vrstice, ki se začnejo s # so komentarji.
 # Poba, nucej UTF-8 :)

-Z redno uporabo VACUUM-a se lahko izboljša delovanje PostgreSQL-a.
+Z redno uporabo VACUUM-a se lahko izboljša delovanje PostgreSQLa.
 Uradni rojstni dan PostgreSQL je 8. julij. Projekt PostgreSQL je nastal leta 1996.
 Prvi prototip za izvirni pgADMin projekt se je imenoval pgMAnager, spisan pa je bil za PostgreSQL 6.3.2.
 Podporo za pgAdmin lahko izrazite na pgadmin-support@postgresql.org dopisnem seznamu.
@@ -25,3 +25,23 @@
 Pano z definicijami vsebuje z obratnim inženiringom pridobljen SQL za izbrani objekt.
 pgAdmin III je popolnoma nova različica pgAdmina, napisana v C++ z uporabo wxWidgets okolja, ki omogoča izvajanje na
Windowsin *nix sistemih. 
 Domene se lahko uporabi za kreiranje predefiniranih podatkovnih tipov, ki temeljijo na bolj splošnih osnovnih tipih.
+pgAdmin III 1.0.0. je bil prvič izdan 26. septembra 2003.
+Procesa postmaster ni dobro končati s 'kill -9'!
+'EXPLAIN ANALYZE' ter gumb 'Razloži stavek' sta dobra prijatelja, ko je potrebno optimirati SQL stavke.
+PostgreSQLov načrtovalec (planner) bo prezrl zahtevo po pregledu indeksov, v kolikor se tipa stolpcev, po katerih
potekazdružitev, ne ujemata. 
+pgAdmin III podpira SSL kriptirane povezave.
+Novi prenos PostgreSQLa na Win32 sistem je prvič prestal vse regresivne preizkuse 24. decembra 2004.
+Windows različica PostgreSQLa je bila v prvih petih dneh po prvi izdaji prenešena več kot 45,000-krat!
+Napaka "Don't enable the OK button when setting the ACL for as-yet-uncreated objects" je bila popravljena na 12,000
metrihvišine nad Finsko, ko so se Andreas, Magnus in Dave vračali z Japonske po predstavitvi Slony-I in pgAdmina! 
+PostgreSQL 8.0 je prinesel veliko novosti, med drugim tudi točke shranjevanja, podatkovne prostore ter dolgo
pričakovanorazličico za Windows sistem. 
+EnterpriseDB so pgAdmin projektu podarili Applov Powerbook, da bi pripomogli izboljšati različico pgAdmina za Mac OS X
inza njihov poenostavljeni derivatni izdelek, EDB Studio. 
+PostgreSQL je bil uspešno pognan na različnih sistemih, kot so Microsoftov X Box, Sony Playstation II in Sharpovi
ZaurusPDA-ji! 
+Japonska skupina uporabnikov PostgreSQLa (JPUG, Japan PostgreSQL Users Group) ima preko 5000 članov in še vedno raste.
+pgAdmin 1.4 vsebuje grafično EXPLAIN orodje, ki omogoča pomaga lažje branje in razumevanje načrtov izvedbe stavkov.
+Sedeti 12 ur v letalu je zastrašujoče dolgočasno, zato tudi pišem nove namige!
+pgAgent lahko služi za izvajanje paketnih ter SQL opravil po določenem urniku. Primera opravil sta denimo ustvarjanje
časovnoodvisnih delnih indeksov ali izbris starih zapisov. 
+Nastavitev PostgreSQLa s preveč deljenega medpomnilnika lahko slabo vpliva na delovanje, ker zniža količino pomnilnika
navoljo jedru operacijskega sistema, ki ga le-ta potrebuje kot predpomnilnik datotečnega sistema. 
+pgAdmin 1.4 je podprt na več operacijskih sistemih kot prejšnje različice, med drugim na številnih Linux
distribucijah,Microsoft Windows (tm), FreeBSDju, Solarisu in na sistemu Mac OS X. 
+Dobra praksa narekuje izgradnjo aplikacijske logike na nivoju podatkovne zbirke z uporabo funkcij ter pogledov. To
pripomorek temu, da imajo različni vmesniki vedno enak vpogled na podatke in jih posodabljajo na enake načine. Kar je
šebolje, za vse vmesnike je to potrebno narediti le enkrat! 
+Za ohranitev varnosti podatkovnih zbirk je dobro v pg_hba.conf datoteki čimbolj omejiti dostope od zunaj in vedno
uporabitikriptirane povezave, razen če nimate dobrih razlogov proti temu. 
+Dostop do posameznih stolpcev v tabeli se posameznim skupinam ali uporabnikom lahko omeji z odvzemom dostopa do njih
ins kreiranjem novega pogleda, ki vsebuje le stolpce, do katerih imajo dostop. Če morajo uporabniki podatke tudi
spreminjati,se to lahko doseže z uporabo pravil, ki priredijo spremembe pogledov na ustrezne tabele.