polishpgdoc-commit Mailing List for Polish PostgreSQL Documentation
Status: Pre-Alpha
Brought to you by:
majek
Menu
▾
▴
polishpgdoc-commit — Lista commitów
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(23) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <sl...@us...> - 2003-07-14 21:40:40
|
Update of /cvsroot/polishpgdoc/nls/nls In directory sc8-pr-cvs1:/tmp/cvs-serv8365 Modified Files: pgadmin3.po Log Message: Index: pgadmin3.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/pgadmin3.po,v retrieving revision 1.1 retrieving revision 1.2 diff -C2 -d -r1.1 -r1.2 *** pgadmin3.po 3 Jul 2003 14:54:34 -0000 1.1 --- pgadmin3.po 14 Jul 2003 21:40:37 -0000 1.2 *************** *** 1,3 **** - # translation of pgadmin3.po to Polish # Copyright (C) YEAR Free Software Foundation, Inc. # Slawomir Sudnik <sl...@ic...>, 2003. --- 1,2 ---- *************** *** 7,11 **** "Project-Id-Version: pgadmin3\n" "POT-Creation-Date: 2003-06-26 11:41+0200\n" ! "PO-Revision-Date: 2003-06-29 21:09+0100\n" "Last-Translator: Slawomir Sudnik <sl...@ic...>\n" [...3383 lines suppressed...] *** 4464,4467 **** --- 5174,5178 ---- # standard + #: input:393 msgid "pgadmin3&%ID.log" msgstr "pgadmin3&%ID.log" *************** *** 4473,4480 **** --- 5184,5193 ---- # standard + #: input:343 msgid "template1" msgstr "template1" # standard + #: input:359 msgid "|" msgstr "|" |
|
From: <sl...@us...> - 2003-07-03 14:54:38
|
Update of /cvsroot/polishpgdoc/nls/nls In directory sc8-pr-cvs1:/tmp/cvs-serv18922 Added Files: pgadmin3.po Log Message: Pierwsze tlumaczenie --- NEW FILE: pgadmin3.po --- # translation of pgadmin3.po to Polish # Copyright (C) YEAR Free Software Foundation, Inc. # Slawomir Sudnik <sl...@ic...>, 2003. # msgid "" msgstr "" "Project-Id-Version: pgadmin3\n" "POT-Creation-Date: 2003-06-26 11:41+0200\n" "PO-Revision-Date: 2003-06-29 21:09+0100\n" "Last-Translator: Slawomir Sudnik <sl...@ic...>\n" "Language-Team: LANGUAGE <LL...@li...>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" #: src/ui/frmQuery.cpp:789 #: src/ui/frmQuery.cpp:813 msgid "" "\n" [...4442 lines suppressed...] msgid "pgServer object didn't initialise because the user aborted." msgstr "Z powodu przerwania przez użytkownika, nie nastÄ piÅo zainicjowanie obiektu pgServer. " # standard msgid "pgadmin3&%ID.log" msgstr "pgadmin3&%ID.log" #: src/ui/frmQuery.cpp:148 #: src/ui/frmQueryBuilder.cpp:158 msgid "ready" msgstr "gotowy" # standard msgid "template1" msgstr "template1" # standard msgid "|" msgstr "|" |
|
From: <sl...@us...> - 2003-07-01 20:35:23
|
Update of /cvsroot/polishpgdoc/nls In directory sc8-pr-cvs1:/tmp/cvs-serv27084 Log Message: Initial import. Status: Vendor Tag: vendor Release Tags: start No conflicts created by this import ***** Bogus filespec: - Imported sources |
|
From: <sl...@us...> - 2003-07-01 15:29:10
|
Update of /cvsroot/polishpgdoc/nls In directory sc8-pr-cvs1:/tmp/cvs-serv4298 Log Message: Initial import. Status: Vendor Tag: vendor Release Tags: start No conflicts created by this import ***** Bogus filespec: - Imported sources |
|
From: <ma...@us...> - 2002-06-17 20:27:16
|
Update of /cvsroot/polishpgdoc/doc/sgml
In directory usw-pr-cvs1:/tmp/cvs-serv17999
Modified Files:
advanced.sgml biblio.sgml query.sgml
Log Message:
A.L.E.C. czuwa!
Index: advanced.sgml
===================================================================
RCS file: /cvsroot/polishpgdoc/doc/sgml/advanced.sgml,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** advanced.sgml 27 Apr 2002 18:30:38 -0000 1.1.1.1
--- advanced.sgml 17 Jun 2002 20:27:07 -0000 1.2
***************
*** 4,31 ****
<chapter id="tutorial-advanced">
! <title>Advanced Features</title>
<sect1 id="tutorial-advanced-intro">
! <title>Introduction</title>
<para>
! In the previous chapter we have covered the basics of using
! <acronym>SQL</acronym> to store and access your data in
! <productname>PostgreSQL</productname>. We will now discuss some
! more advanced features of <acronym>SQL</acronym> that simplify
! management and prevent loss or corruption of your data. Finally,
! we will look at some <productname>PostgreSQL</productname>
! extensions.
</para>
<para>
! This chapter will on occasion refer to examples found in <xref
! linkend="tutorial-sql"> to change or improve them, so it will be
! of advantage if you have read that chapter. Some examples from
! this chapter can also be found in
! <filename>advanced.sql</filename> in the tutorial directory. This
! file also contains some example data to load, which is not
! repeated here. (Refer to <xref linkend="tutorial-sql-intro"> for
! how to use the file.)
</para>
</sect1>
--- 4,29 ----
<chapter id="tutorial-advanced">
! <title>Zaawansowane w³a¶ciwo¶ci</title>
<sect1 id="tutorial-advanced-intro">
! <title>Wprowadzenie</title>
<para>
! W poprzednim rozdziale poznali¶my podstawy zastosowania
! <acronym>SQL'a</acronym> do przechowywania danych i dostêpu do nich
! w <productname>PostgreSQL'u</productname>. Teraz omówimy bardziej zaawansowane
! w³a¶ciwo¶ci jêzyka <acronym>SQL</acronym>, które u³atwiaj± zarz±dzanie oraz
! zabezpieczaj± przed utrat± lub uszkodzeniem danych. W koñcu
! poznamy niektóre rozszerzenia <productname>PostgreSQL'a</productname>.
</para>
<para>
! Niniejszy rozdzia³ bêdzie odwo³ywa³ siê do przyk³adów
! zamieszczonych w <xref
! linkend="tutorial-sql"> w celu ich zmiany i ulepszeñ, wiêc
! wskazane jest zapoznanie siê z tym rozdzia³em. Niektóre
! z przyk³adów mo¿na znale¼æ w <filename>advanced.sql</filename> w katalogu
! z tutorialem. Plik ten zawiera te¿ inne przyk³ady wprowadzania
! danych, nie wspomniane tutaj. (Zobacz jak u¿yæ ten plik w <xref linkend="tutorial-sql-intro">).
</para>
</sect1>
***************
*** 33,49 ****
<sect1 id="tutorial-views">
! <title>Views</title>
<indexterm zone="tutorial-views">
! <primary>view</primary>
</indexterm>
<para>
! Refer back to the queries in <xref linkend="tutorial-join">.
! Suppose the combined listing of weather records and city location
! is of particular interest to your application, but you don't want
! to type the query each time you need it. You can create a
! <firstterm>view</firstterm> over the query, which gives a name to
! the query that you can refer to like an ordinary table.
<programlisting>
--- 31,47 ----
<sect1 id="tutorial-views">
! <title>Widoki</title>
<indexterm zone="tutorial-views">
! <primary>widok</primary>
</indexterm>
<para>
! Odwo³ajmy siê do zapytañ z <xref linkend="tutorial-join">.
! Zak³adamy, ¿e ³±czona lista rekordów pogody oraz po³o¿enia miast
! jest szczególnie wa¿na w naszej aplikacji ale nie chcemy wprowadzaæ
! zapytania za ka¿dym razem, gdy jest potrzebne. Mo¿emy stworzyæ
! <firstterm>widok</firstterm> oparty na zapytaniu, nadaj±c mu nazwê do której bêdziemy
! mogli odwo³ywaæ siê jak do zwyk³ej tabeli.
<programlisting>
***************
*** 58,70 ****
<para>
! Making liberal use of views is a key aspect of good SQL database
! design. Views allow you to encapsulate the details of the
! structure of your tables, which may change as your application
! evolves, behind consistent interfaces.
</para>
<para>
! Views can be used in almost any place a real table can be used.
! Building views upon other views is not uncommon.
</para>
</sect1>
--- 56,70 ----
<para>
! Tworzenie widoków o szerokim zastosowaniu jest kluczowym
! aspektem dobrego projektowania SQL'owych baz danych.
! Widoki pozwalaj± odseparowaæ szczegó³ow± strukturê tabel,
! która mo¿e siê zmieniaæ wraz z rozwojem aplikacji, niezale¿nie
! od zastosowanych interfejsów.
</para>
<para>
! Widoku mog± byæ stosowane prawie zawsze w miejsce
! rzeczywistych tabel. Budowanie widoków z innych widoków
! nie jest niczym niezwyk³ym.
</para>
</sect1>
***************
*** 72,112 ****
<sect1 id="tutorial-fk">
! <title>Foreign Keys</title>
<indexterm zone="tutorial-fk">
! <primary>foreign key</primary>
</indexterm>
<indexterm zone="tutorial-fk">
! <primary>referential integrity</primary>
</indexterm>
<para>
! Recall the <classname>weather</classname> and
! <classname>cities</classname> tables from <xref
! linkend="tutorial-sql">. Consider the following problem: You
! want to make sure that no one can insert rows in the
! <classname>weather</classname> table that do not have a matching
! entry in the <classname>cities</classname> table. This is called
! maintaining the <firstterm>referential integrity</firstterm> of
! your data. In simplistic database systems this would be
! implemented (if at all) by first looking at the
! <classname>cities</classname> table to check if a matching record
! exists, and then inserting or rejecting the new
! <classname>weather</classname> records. This approach has a
! number of problems and is very inconvenient, so
! <productname>PostgreSQL</productname> can do this for you.
</para>
<para>
! The new declaration of the tables would look like this:
<programlisting>
! CREATE TABLE cities (
city varchar(80) primary key,
location point
);
! CREATE TABLE weather (
city varchar(80) references cities,
temp_lo int,
--- 72,111 ----
<sect1 id="tutorial-fk">
! <title>Klucze obce</title>
<indexterm zone="tutorial-fk">
! <primary>klucz obcy</primary>
</indexterm>
<indexterm zone="tutorial-fk">
! <primary>integralno¶æ referencyjna</primary>
</indexterm>
<para>
! Wracaj±c do tabel <classname>weather</classname> i <classname>cities</classname> z <xref
! linkend="tutorial-sql">. Rozwa¿my
! nastêpuj±cy problem: Chcieliby¶my mieæ pewno¶æ, ¿e
! nikt nie mo¿e wstawiæ wierszy do tabeli <classname>weather</classname>,
! który nie ma odpowiedniego wpisu w tabeli <classname>cities</classname>.
! Jest to nazywane <firstterm>integralno¶ci± referencyjn±</firstterm> danych.
! W prymitywnych systemach baz danych mo¿na by³oby to
! zaimplementowaæ przez sprawdzenie, czy pasuj±cy rekord istnieje w tabeli
! <classname>cities</classname>, a nastêpnie wstawienie lub odrzucenie nowych rekordów
! tabeli <classname>weather</classname>. To podej¶cie napotyka wiele trudno¶ci
! i jest bardzo k³opotliwe, dlatego <productname>PostgreSQL</productname> robi to za nas.
</para>
<para>
! Nowa deklaracja tabel powinna wygl±daæ tak:
<programlisting>
! CREATE TABLE cities
! (
city varchar(80) primary key,
location point
);
! CREATE TABLE weather
! (
city varchar(80) references cities,
temp_lo int,
***************
*** 118,122 ****
</programlisting>
! Now try inserting an invalid record:
<programlisting>
--- 117,121 ----
</programlisting>
! Teraz spróbuj wstawiæ niepoprawne dane:
<programlisting>
***************
*** 125,129 ****
<screen>
! ERROR: <unnamed> referential integrity violation - key referenced from weather not found in cities
</screen>
--- 124,128 ----
<screen>
! ERROR: <unnamed> naruszenie integralno¶ci referencyjnej - klucz odnosz±cy siê do weather nie znaleziony w cities
</screen>
***************
*** 131,140 ****
<para>
! The behavior of foreign keys can be finely tuned to your
! application. We will not go beyond this simple example in this
! tutorial, but just refer you to the <citetitle>Reference
! Manual</citetitle> for more information. Making correct use of
! foreign keys will definitely improve the quality of your database
! applications, so you are strongly encouraged to learn about them.
</para>
</sect1>
--- 130,139 ----
<para>
! Dzia³anie kluczy obcych mo¿e mieæ zastosowanie w twoich aplikacjach.
! Nie bêdziemy wychodziæ poza ten prosty przyk³ad, po wiêcej informacji
! odsy³amy Ciê do <citetitle>Podrêcznika u¿ytkownika</citetitle>. Prawid³owe zastosowanie
! kluczy obcych zdecydowanie podniesie jako¶æ Twoich aplikacji
! bazodanowych, dlatego zachêcamy do lepszego poznania tego
! zagadnienia.
</para>
</sect1>
***************
*** 142,166 ****
<sect1 id="tutorial-transactions">
! <title>Transactions</title>
<indexterm zone="tutorial-transactions">
! <primary>transactions</primary>
</indexterm>
<para>
! <firstterm>Transactions</> are a fundamental concept of all database
! systems. The essential point of a transaction is that it bundles
! multiple steps into a single, all-or-nothing operation. The intermediate
! states between the steps are not visible to other concurrent transactions,
! and if some failure occurs that prevents the transaction from completing,
! then none of the steps affect the database at all.
</para>
<para>
! For example, consider a bank database that contains balances for various
! customer accounts, as well as total deposit balances for branches.
! Suppose that we want to record a payment of $100.00 from Alice's account
! to Bob's account. Simplifying outrageously, the SQL commands for this
! might look like
<programlisting>
UPDATE accounts SET balance = balance - 100.00
--- 141,165 ----
<sect1 id="tutorial-transactions">
! <title>Transakcje</title>
<indexterm zone="tutorial-transactions">
! <primary>transakcje</primary>
</indexterm>
<para>
! <firstterm>Transakcje</> s± podstawow± w³asno¶ci± wszystkich systemów
! baz danych. Istot± transakcji jest ³±czenie nieograniczonej ilo¶ci
! operacji w jedn±. Stany po¶rednie miêdzy operacjami jednej
! transakcji nie s± widoczne dla innych transakcji i je¶li wyst±pi b³±d,
! uniemo¿liwiaj±cy ukoñczenie transakcji, wtedy ¿adna z operacji
! nie jest zapisywana do bazy.
</para>
<para>
! Na przyk³ad, we¼my bankow± bazê danych, zawieraj±c± salda na
! kontach ró¿nych klientów, jako ca³kowity depozyt wszystkich oddzia³ów
! banku. Przypu¶æmy, ¿e chcemy przelaæ 100.00 $ z konta Alice
! na konto Boba. Bardzo upraszczaj±c, polecenia SQL mog±
! wygl±daæ tak:
<programlisting>
UPDATE accounts SET balance = balance - 100.00
***************
*** 173,252 ****
WHERE name = (SELECT branch_name FROM accounts WHERE name = 'Bob');
</programlisting>
! The details of these commands are not important here; the important
! point is that there are several separate updates involved to accomplish
! this rather simple operation. Our bank's officers will want to be
! assured that either all these updates happen, or none of them happen.
! It would certainly not do for a system failure to result in Bob
! receiving $100.00 that was not debited from Alice. Nor would Alice long
! remain a happy customer if she was debited without Bob being credited.
! We need a guarantee that if something goes wrong partway through the
! operation, none of the steps executed so far will take effect. Grouping
! the updates into a <firstterm>transaction</> gives us this guarantee.
! A transaction is said to be <firstterm>atomic</>: from the point of
! view of other transactions, it either happens completely or not at all.
</para>
<para>
! We also want a
! guarantee that once a transaction is completed and acknowledged by
! the database system, it has indeed been permanently recorded
! and won't be lost even if a crash ensues shortly thereafter.
! For example, if we are recording a cash withdrawal by Bob,
! we do not want any chance that the debit to his account will
! disappear in a crash just as he walks out the bank door.
! A transactional database guarantees that all the updates made by
! a transaction are logged in permanent storage (i.e., on disk) before
! the transaction is reported complete.
</para>
<para>
! Another important property of transactional databases is closely
! related to the notion of atomic updates: when multiple transactions
! are running concurrently, each one should not be able to see the
! incomplete changes made by others. For example, if one transaction
! is busy totalling all the branch balances, it would not do for it
! to include the debit from Alice's branch but not the credit to
! Bob's branch, nor vice versa. So transactions must be all-or-nothing
! not only in terms of their permanent effect on the database, but
! also in terms of their visibility as they happen. The updates made
! so far by an open transaction are invisible to other transactions
! until the transaction completes, whereupon all the updates become
! visible simultaneously.
</para>
<para>
! In <productname>PostgreSQL</>, a transaction is set up by surrounding
! the SQL commands of the transaction with
! <command>BEGIN</> and <command>COMMIT</> commands. So our banking
! transaction would actually look like
<programlisting>
BEGIN;
UPDATE accounts SET balance = balance - 100.00
WHERE name = 'Alice';
! -- etc etc
COMMIT;
</programlisting>
! If, partway through the transaction, we decide we don't want to
! commit (perhaps we just noticed that Alice's balance went negative),
! we can issue the command <command>ROLLBACK</> instead of
! <command>COMMIT</>, and all our updates so far will be canceled.
</para>
<para>
! <productname>PostgreSQL</> actually treats every SQL statement as being
! executed within a transaction. If you don't issue a <command>BEGIN</>
! command,
! then each individual statement has an implicit <command>BEGIN</> and
! (if successful) <command>COMMIT</> wrapped around it. A group of
! statements surrounded by <command>BEGIN</> and <command>COMMIT</>
! is sometimes called a <firstterm>transaction block</>.
</para>
<note>
<para>
! Some client libraries issue <command>BEGIN</> and <command>COMMIT</>
! commands automatically, so that you may get the effect of transaction
! blocks without asking. Check the documentation for the interface
! you are using.
</para>
</note>
--- 172,253 ----
WHERE name = (SELECT branch_name FROM accounts WHERE name = 'Bob');
</programlisting>
! Szczegó³y tych poleceñ nie s± tutaj wa¿ne; istotne jest, ¿e mamy
! tutaj ³±czymy wiele poleceñ aktualizuj±cych w celu realizacji
! tej jak¿e prostej operacji. Pracownicy naszego banku chcieliby
! mieæ pewno¶æ, ¿e ka¿da z tych operacji powiod³a siê albo ¿adna
! nie odnios³a skutku. Nie do przyjêcia jest sytuacja, gdy Bob otrzymuje
! 100.00 $, bez potr±cenia tej kwoty z konta Alice, ani te¿ nie bêdzie
! zachwycona Alice, gdy pieni±dze zostan± jej potr±cone,
! a Bob nie zostanie sp³acony. Musimy mieæ gwarancjê, ¿e
! gdyby która¶ czê¶æ operacji nie powiod³a siê, to ¿aden z kroków
! wykonanych wcze¶niej nie da efektu. Grupowanie uaktualnieñ w
! jedn± <firstterm>transaction</> daje nam t± gwarancjê. Mówi siê, ¿e transakcja
! jest <firstterm>atomowa</>: z punktu widzenia transakcji, jest wykonywana w
! ca³o¶ci albo w ogóle.
</para>
<para>
! Chcemy równie¿ zagwarantowania, ¿e transakcja zosta³a
! wykonana przez potwierdzenie z systemu bazodanowego.
! To znaczy, ¿e zosta³a rzeczywi¶cie zapisana na sta³e i nie
! zostanie utracona nawet gdyby wkrótce pó¼niej nast±pi³a
! awaria. Na przyk³ad je¶li zapisujemy podjêcie pieniêdzy przez
! Boba, to nie chcemy ¿eby potr±cenie z jego konta zginê³o, tak
! jakby po prostu wyszed³ z banku przez drzwi. Transakcyjna baza
! danych daje gwarancjê, ¿e wszystkie operacje wewn±trz transakcji
! zostan± zapisane na trwa³ym no¶niku (np. dysku) zanim
! transakcja zostanie wykonana w ca³o¶ci.
</para>
<para>
! Inn± wa¿n± w³a¶ciwo¶ci± transakcyjnych baz danych jest bliski
! zwi±zek z zapisem operacji cz±stkowych: gdy wykonuje siê wiele
! transakcji, ¿adna nie powinna widzieæ niekompletnych zmian
! dokonanych przez inne transakcje. Na przyk³ad, je¶li jedna
! transakcja jest zajêta sumowaniem depozytów w ka¿dym
! oddziale, nie powinna braæ pod uwagê debetu w oddziale Alice
! bez uwzglêdniania zwy¿ki w oddziale Boba, ani odwrotnie.
! Transakcje musz± byæ wykonywane jako wszystko-lub-nic nie
! tylko z punktu widzenia trwa³ego efektu na bazie danych, ale
! równie¿ z punktu widzenia ich dzia³ania. Operacje jednej
! transakcji s± niewidoczne dla innych dopóki nie zostanie ona
! wykonana w ca³o¶ci, potem efekt tych operacji stanie siê widoczny
! rónocze¶nie.
</para>
<para>
! W <productname>PostgreSQL'u</> transakcjê stanowi± polecenia SQL
! otoczone komendami
! <command>BEGIN</> i <command>COMMIT</>. Tak wiêc, nasza transakcja
! bankowa bêdzie wygl±daæ nastêpuj±co:
<programlisting>
BEGIN;
UPDATE accounts SET balance = balance - 100.00
WHERE name = 'Alice';
! -- itd.
COMMIT;
</programlisting>
! Je¶li podczas wykonywania transakcji zdecydujemy, ¿e nie
! chcemy jej zatwierdziæ (na przyk³ad stwierdzili¶my, ¿e saldo Alice
! jest ujeme), mo¿emy u¿yæ komendê <command>ROLLBACK</> w miejsce
! <command>COMMIT</> i wtedy wszystkie operacje wykonane dotychczas
! zostana odwo³ane.
</para>
<para>
! Obecnie <productname>PostgreSQL</> traktuje ka¿de polecenie SQL
! jak wykonywane wewn±trz transakcji. Je¶li nie wprowadzisz
! polecenia <command>BEGIN</>, wtedy ka¿da indywidualna operacja
! zostanie otoczona <command>BEGIN</> i (je¶li siê powiod³a) <command>COMMIT</>
! wokó³ niej. Grupa poleceñ otoczonych przez <command>BEGIN</> i <command>COMMIT</>
! czasami nazywana jest <firstterm>blokiem transakcji</>.
</para>
<note>
<para>
! Niektóre biblioteki klienckie do³±czaj± komendy <command>BEGIN</>
! i <command>COMMIT</> automatycznie, wiêc mo¿esz otrzymaæ efekt
! transakcji nie wiedz±c o tym. Sprawd¼ dokumentacjê
! interfejsów, których u¿ywasz.
</para>
</note>
***************
*** 255,275 ****
<sect1 id="tutorial-inheritance">
! <title>Inheritance</title>
<indexterm zone="tutorial-inheritance">
! <primary>inheritance</primary>
</indexterm>
<para>
! Inheritance is a concept from object-oriented databases. It opens
! up interesting new possibilities of database design.
</para>
<para>
! Let's create two tables: A table <classname>cities</classname>
! and a table <classname>capitals</classname>. Naturally, capitals
! are also cities, so you want some way to show the capitals
! implicitly when you list all cities. If you're really clever you
! might invent some scheme like this:
<programlisting>
--- 256,276 ----
<sect1 id="tutorial-inheritance">
! <title>Dziedziczenie</title>
<indexterm zone="tutorial-inheritance">
! <primary>dziedziczenie</primary>
</indexterm>
<para>
! Dziedziczenie jest w³a¶ciwo¶ci± obiektowo zorientowanych
! baz danych, która daje nowe interesuj±ce mo¿liwo¶ci projektowania
! baz danych.
</para>
<para>
! Utwórzmy dwie tabele: tabelê <classname>cities</classname> (miasta)
! i tabelê <classname>capitals</classname> (stolice). Naturalnie, stolice s± równie¿ miastami
! wiêc musimy w jaki¶ sposób je wyró¿niæ w¶ród miast.
! Mo¿na zastosowaæ nastêpuj±cy schemat:
<programlisting>
***************
*** 293,302 ****
</programlisting>
! This works OK as far as querying goes, but it gets ugly when you
! need to update several rows, to name one thing.
</para>
<para>
! A better solution is this:
<programlisting>
--- 294,304 ----
</programlisting>
! Bêdzie to dzia³aæ dopóki wyszukujemy dane, ale je¶li bêdziemy
! chcieli zaktualizowaæ kilka wierszy, aby zmieniæ jedn± rzecz, nie bêdzie
! to wygl±daæ ³adnie.
</para>
<para>
! Lepszym rozwi±zaniem bêdzie:
<programlisting>
***************
*** 312,331 ****
</programlisting>
! In this case, a row of <classname>capitals</classname>
! <firstterm>inherits</firstterm> all columns (<structfield>name</>,
! <structfield>population</>, and <structfield>altitude</>) from its
! <firstterm>parent</firstterm>, <classname>cities</classname>. The
! type of the column <structfield>name</structfield> is
! <type>text</type>, a native <productname>PostgreSQL</productname>
! type for variable length character strings. State capitals have
! an extra column, state, that shows their state. In
! <productname>PostgreSQL</productname>, a table can inherit from
! zero or more other tables.
</para>
<para>
! For example, the following query finds the names of all cities,
! including state capitals, that are located at an altitude
! over 500 ft.:
<programlisting>
--- 314,330 ----
</programlisting>
! W tym wypadku wiersz tabeli <classname>capitals</classname>
! <firstterm>dziedziczy</firstterm> wszystkie kolumny (<structfield>name</>,
! <structfield>population</>, and <structfield>altitude</>) od swojego rodzica
! <firstterm>parent</firstterm>, tabeli <classname>cities</classname>. Kolumna <structfield>name</structfield> jest
! typu <type>text</type>, przeznaczonego w <productname>PostgreSQL'u</productname>
! dla ci±gów znakowych zmiennej d³ugo¶ci. Stolice stanów
! posiadaj± dodatkow± kolumnê state opisuj±c± w którym s± stanie.
! W <productname>PostgreSQL'u</productname> tabela mo¿e dziedziczyæ z wiêcej ni¿ jednej tabeli.
</para>
<para>
! Dla przyk³adu, nastêpuj±ce zapytanie wyszukuje nazwy wszystkich miast
! w³±cznie ze stolicami po³o¿onymi na wysoko¶ci powy¿ej 500 ft.:
<programlisting>
***************
*** 335,339 ****
</programlisting>
! which returns:
<screen>
--- 334,338 ----
</programlisting>
! a zwraca:
<screen>
***************
*** 343,354 ****
Mariposa | 1953
Madison | 845
! (3 rows)
</screen>
</para>
<para>
! On the other hand, the following query finds
! all the cities that are not state capitals and
! are situated at an altitude of 500 ft. or higher:
<programlisting>
--- 342,352 ----
Mariposa | 1953
Madison | 845
! (3 rek.)
</screen>
</para>
<para>
! Z drugiej strony, poni¿sze zapytanie wy¶wietli wszystkie miasta, nie bêd±ce
! stolicami, usytuowane na wysoko¶ci powy¿ej 500 ft.:
<programlisting>
***************
*** 363,379 ****
Las Vegas | 2174
Mariposa | 1953
! (2 rows)
</screen>
</para>
<para>
! Here the <literal>ONLY</literal> before <literal>cities</literal>
! indicates that the query should be run over only the
! <classname>cities</classname> table, and not tables below
! <classname>cities</classname> in the inheritance hierarchy. Many
! of the commands that we have already discussed --
! <command>SELECT</command>, <command>UPDATE</command> and
! <command>DELETE</command> -- support this <literal>ONLY</literal>
! notation.
</para>
</sect1>
--- 361,376 ----
Las Vegas | 2174
Mariposa | 1953
! (2 rek.)
</screen>
</para>
<para>
! Klauzula <literal>ONLY</literal> przed <literal>cities</literal>
! oznacza, ¿e zapytanie powinno byæ wykonane tylko
! na tabeli <classname>cities</classname>, a nie na tabelach dziedzicz±cych po
! <classname>cities</classname>.
! Do wielu komend, które ju¿ omówili¶my --
! <command>SELECT</command>, <command>UPDATE</command> oraz
! <command>DELETE</command> mo¿na stosowaæ klauzulê <literal>ONLY</literal>.
</para>
</sect1>
***************
*** 381,399 ****
<sect1 id="tutorial-conclusion">
! <title>Conclusion</title>
<para>
! <productname>PostgreSQL</productname> has many features not
! touched upon in this tutorial introduction, which has been
! oriented toward newer users of <acronym>SQL</acronym>. These
! features are discussed in more detail in both the
! <citetitle>User's Guide</citetitle> and the
! <citetitle>Programmer's Guide</citetitle>.
</para>
<para>
! If you feel you need more introductory material, please visit the
! <ulink url="http://www.postgresql.org">PostgreSQL web
! site</ulink> for links to more resources.
</para>
</sect1>
--- 378,395 ----
<sect1 id="tutorial-conclusion">
! <title>Podsumowanie</title>
<para>
! <productname>PostgreSQL</productname> posiada wiele w³a¶ciwo¶ci nie wyszczególnionych
! w tej czê¶ci dokumentacji, przeznaczonych dla bardziej
! zaawansowanych u¿ytkowników <acronym>SQL'a</acronym>. W³a¶ciwo¶ci te
! s± opisane bardziej szczegó³owo w <citetitle>Podrêczniku u¿ytkownika</citetitle>
! oraz <citetitle>Podrêczniku programisty</citetitle>.
</para>
<para>
! Je¶li potrzebujesz wiêcej materia³ów wprowadzaj±cych odwied¼
! <ulink url="http://www.postgresql.org">stronê PostgreSQL w Internecie</ulink>, na której znajdziesz wiele
! odno¶ników do dokumentacji.
</para>
</sect1>
Index: biblio.sgml
===================================================================
RCS file: /cvsroot/polishpgdoc/doc/sgml/biblio.sgml,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** biblio.sgml 27 Apr 2002 18:30:41 -0000 1.1.1.1
--- biblio.sgml 17 Jun 2002 20:27:08 -0000 1.2
***************
*** 4,26 ****
<bibliography id="biblio">
! <title>Bibliography</title>
<para>
! Selected references and readings for <acronym>SQL</acronym>
! and <productname>PostgreSQL</productname>.
</para>
<para>
! Some white papers and technical reports from the original
! <productname>POSTGRES</productname> development team
! are available at
<ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/papers/">
! the University of California, Berkeley, Computer Science
! Department web site</ulink>
</para>
<bibliodiv>
! <title><acronym>SQL</acronym> Reference Books</title>
! <para>Reference texts for <acronym>SQL</acronym> features.</para>
<biblioentry id="BOWMAN93">
--- 4,25 ----
<bibliography id="biblio">
! <title>Bibliografia</title>
<para>
! Wybrane podrêczniki i opracowania na temat <acronym>SQL</acronym>
! i <productname>PostgreSQL</productname>.
</para>
<para>
! Wiele technicznych opracowañ zespo³u twórców
! <productname>POSTGRES</productname> jest dostêpnych na stronie
<ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/papers/">
! University of California, Berkeley, Computer Science
! Department</ulink>
</para>
<bibliodiv>
! <title>Podrêczniki<acronym>SQL</acronym></title>
! <para>Opis w³a¶ciwo¶ci<acronym>SQL</acronym>.</para>
<biblioentry id="BOWMAN93">
***************
*** 166,171 ****
<bibliodiv>
! <title>PostgreSQL-Specific Documentation</title>
! <para>This section is for related documentation.</para>
<biblioentry id="SIM98">
--- 165,170 ----
<bibliodiv>
! <title>Dokumentacja PostgreSQL</title>
! <para>Ta czê¶æ dotyczy dokumentacji ¶ci¶le dotycz±cej postgresa.</para>
<biblioentry id="SIM98">
***************
*** 184,191 ****
</author>
</authorgroup>
! <!--
! <othercredit>
<contrib>
! with support by
</contrib>
<honorific>O. Univ. Prof. Dr.</honorific>
--- 183,189 ----
</author>
</authorgroup>
! <othercredit>
<contrib>
! przy wspó³pracy
</contrib>
<honorific>O. Univ. Prof. Dr.</honorific>
***************
*** 196,207 ****
<surname>Seyr</surname>
</othercredit>
! -->
<abstract>
<para>
! Discusses SQL history and syntax, and describes the addition of
! <literal>INTERSECT</> and <literal>EXCEPT</> constructs into
! <productname>PostgreSQL</productname>. Prepared as a Master's
! Thesis with the support of O. Univ. Prof. Dr. Georg Gottlob and
! Univ. Ass. Mag. Katrin Seyr at Vienna University of Technology.
</para>
</abstract>
--- 194,205 ----
<surname>Seyr</surname>
</othercredit>
! --</indexterm>
<abstract>
<para>
! Omawia historiê i sk³adniê SQL oraz opisuje u¿ycie konstrukcji
! <literal>INTERSECT</> i <literal>EXCEPT</> w <productname>PostgreSQL</productname>.
! Stworzona jako Tezy G³ówne z pomoc±
! O. Univ. Prof. Dr. Georg Gottlob i
! Univ. Ass. Mag. Katrin Seyr z Vienna University of Technology.
</para>
</abstract>
***************
*** 257,262 ****
<bibliodiv>
! <title>Proceedings and Articles</title>
! <para>This section is for articles and newsletters.</para>
<biblioentry id="OLSON93">
--- 255,260 ----
<bibliodiv>
! <title>Artyku³y i sprawozdania</title>
! <para>W tej czê¶ci s± artyku³y i biuletyny.</para>
<biblioentry id="OLSON93">
Index: query.sgml
===================================================================
RCS file: /cvsroot/polishpgdoc/doc/sgml/query.sgml,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** query.sgml 27 Apr 2002 18:31:02 -0000 1.1.1.1
--- query.sgml 17 Jun 2002 20:27:08 -0000 1.2
***************
*** 1,819 ****
! <!--
! $Header$
! -->
!
! <chapter id="tutorial-sql">
! <title>The <acronym>SQL</acronym> Language</title>
!
! <sect1 id="tutorial-sql-intro">
! <title>Introduction</title>
!
[...1584 lines suppressed...]
! </sect1>
!
! </chapter>
!
! <!-- Keep this comment at the end of the file
! Local variables:
! mode:sgml
! sgml-omittag:nil
! sgml-shorttag:t
! sgml-minimize-attributes:nil
! sgml-always-quote-attributes:t
! sgml-indent-step:1
! sgml-indent-data:t
! sgml-parent-document:nil
! sgml-default-dtd-file:"./reference.ced"
! sgml-exposed-tags:nil
! sgml-local-catalogs:("/usr/lib/sgml/catalog")
! sgml-local-ecat-files:nil
! End:
! -->
|
|
From: <ma...@us...> - 2002-06-07 06:24:25
|
Update of /cvsroot/polishpgdoc/doc/sgml
In directory usw-pr-cvs1:/tmp/cvs-serv1093
Modified Files:
start.sgml
Log Message:
pierwsze tlumaczenie a.l.k.a
Index: start.sgml
===================================================================
RCS file: /cvsroot/polishpgdoc/doc/sgml/start.sgml,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** start.sgml 27 Apr 2002 18:31:13 -0000 1.1.1.1
--- start.sgml 7 Jun 2002 06:24:22 -0000 1.2
***************
*** 4,54 ****
<chapter id="tutorial-start">
! <title>Getting Started</title>
<sect1 id="tutorial-install">
! <title>Installation</title>
<para>
! Before you can use <productname>PostgreSQL</productname> you need
! to install it, of course. It is possible that
! <productname>PostgreSQL</productname> is already installed at your
! site, either because it was included in your operating system
! distribution or because the system administrator already installed
! it. If that is the case, you should obtain information from the
! operating system documentation or your system administrator about
! how to access <productname>PostgreSQL</productname>.
</para>
<para>
! If you are not sure whether <productname>PostgreSQL</productname>
! is already available or whether you can use it for your
! experimentation then you can install it yourself. Doing so is not
! hard and it can be a good exercise.
! <productname>PostgreSQL</productname> can be installed by any
! unprivileged user, no superuser (<systemitem>root</systemitem>)
! access is required.
</para>
<para>
! If you are installing <productname>PostgreSQL</productname>
! yourself, then refer to the <citetitle>Administrator's
! Guide</citetitle> for instructions on installation, and return to
! this guide when the installation is complete. Be sure to follow
! closely the section about setting up the appropriate environment
! variables.
</para>
<para>
! If your site administrator has not set things up in the default
! way, you may have some more work to do. For example, if the
! database server machine is a remote machine, you will need to set
! the <envar>PGHOST</envar> environment variable to the name of the
! database server machine. The environment variable
! <envar>PGPORT</envar> may also have to be set. The bottom line is
! this: if you try to start an application program and it complains
! that it cannot connect to the database, you should consult your
! site administrator or, if that is you, the documentation to make
! sure that your environment is properly set up. If you did not
! understand the preceding paragraph then read the next section.
</para>
</sect1>
--- 4,49 ----
<chapter id="tutorial-start">
! <title>Pierwsze kroki</title>
<sect1 id="tutorial-install">
! <title>Instalacja</title>
<para>
! Zanim zabierzesz siê za <productname>PostgreSQL</productname> musisz go oczywi¶cie
! zainstalowaæ. Mo¿liwe, ¿e ju¿ masz zainstalowanego
! <productname>PostgreSQL'a</productname>, bo byæ mo¿e by³ do³±czony do twojego systemu
! operacyjnego lub twój administrator go zainstalowa³.
! W takim wypadku mo¿esz otrzymaæ informacje o dostêpie
! do <productname>PostgreSQL</productname> od administratora lub znale¼æ je w dokumentacji
! systemu operacyjnego.
</para>
<para>
! Je¶li nie jeste¶ pewien czy <productname>PostgreSQL</productname> jest dostêpny
! albo czy mo¿esz go u¿ywaæ do swoich eksperymentów,
! powiniene¶ go zainstalowaæ sam. Nie jest to trudna, a mo¿e
! byæ dobrym æwiczeniem.
! <productname>PostgreSQL'a</productname> mo¿e instalowaæ ka¿dy nieuprzywilejowany
! u¿ytkownik, prawa superu¿ytkownika (<systemitem>roota</systemitem>) nie s± konieczne.
</para>
<para>
! Gdy sam zamierzasz zainstalowaæ <productname>PostgreSQL'a</productname>,
! zacznij od <citetitle>Podrêcznika administratora</citetitle>, a po instalacji mo¿esz
! wróciæ do niniejszej czê¶ci. Musisz postêpowaæ zgodnie z tym
! rozdzia³em, aby prawid³owo ustawiæ w³a¶ciwe zmienne ¶rodowiskowe.
</para>
<para>
! Je¿eli administrator systemu nie stosuje ustawieñ domy¶lnych,
! byæ mo¿e bêdziesz musia³ ustawiæ inne rzeczy, np. je¿eli
! serwer jest komputerem zdalnym trzeba ustawiæ zmienn±
! <envar>PGHOST</envar> na nazwê tego komputera. Mo¿na równie¿
! ustawiæ zmienn± <envar>PGPORT</envar>. Zasada jest taka: gdy
! spróbujesz uruchomiæ program i nie bêdziesz móg³ po³aczyæ
! siê z baz± danych, powiniene¶ skonsultowaæ siê z administratorem,
! je¿eli to ty, z dokumentacj± by upewniæ siê, ¿e ¶rodowisko jest
! ustawione prawid³owo. Je¶li nie rozumiesz tego akapitu przeczytaj
! nastêpny rozdzia³.
</para>
</sect1>
***************
*** 56,83 ****
<sect1 id="tutorial-arch">
! <title>Architectural Fundamentals</title>
<para>
! Before we proceed, you should understand the basic
! <productname>PostgreSQL</productname> system architecture.
! Understanding how the parts of
! <productname>PostgreSQL</productname> interact will make this
! chapter somewhat clearer.
</para>
<para>
! In database jargon, <productname>PostgreSQL</productname> uses a
! client/server model. A <productname>PostgreSQL</productname>
! session consists of the following cooperating processes
! (programs):
<itemizedlist>
<listitem>
<para>
! A server process, which manages the database files, accepts
! connections to the database from client applications, and
! performs actions on the database on behalf of the clients. The
! database server program is called
! <filename>postmaster</filename>.
<indexterm><primary>postmaster</primary></indexterm>
</para>
--- 51,75 ----
<sect1 id="tutorial-arch">
! <title>Podstawy architektury</title>
<para>
! Zanim rozpoczniemy powiniene¶ poznaæ podstawow±
! architekturê systemu <productname>PostgreSQL</productname>.
! Ten rozdzia³ wyja¶nia jak wspó³pracuj± elementy bazy
! <productname>PostgreSQL</productname>.
</para>
<para>
! <productname>PostgreSQL</productname> u¿ywa modelu klient/serwer.
! Sesja <productname>PostgreSQL</productname>zawiera nastêpuj±ce wspó³pracuj±ce
! procesy (programy):
<itemizedlist>
<listitem>
<para>
! Proces serwera, który zarz±dza plikami bazy danych, zatwierdza
! po³±czenia z baz± od aplikacji klienckich i na ¿±danie klienta
! przeprowadza operacje na bazie danych. Program ten nosi
! nazwê <filename>postmaster</filename>.
<indexterm><primary>postmaster</primary></indexterm>
</para>
***************
*** 86,97 ****
<listitem>
<para>
! The user's client (frontend) application that wants to perform
! database operations. Client applications can be very diverse
! in nature: They could be a text-oriented tool, a graphical
! application, a web server that accesses the database to
! display web pages, or a specialized database maintenance tool.
! Some client applications are supplied with the
! <productname>PostgreSQL</productname> distribution, most are
! developed by users.
</para>
</listitem>
--- 78,87 ----
<listitem>
<para>
! Aplikacja u¿ytkownika (frontend) ¿±daj±ca przeprowadzenia
! operacji na bazie. Mo¿e byæ narzêdziem tekstowym, aplikacj±
! graficzn±, serwerem internetowym z dostêpem poprzez strony
! internetowe lub specjalizowanym programem do zarz±dzania baz±.
! Niektóre aplikacje klienckie s± dostarczane wraz z dystrybucj±
! <productname>PostgreSQL</productname>, ale wiêkszo¶æ jest tworzona przez u¿ytkowników.
</para>
</listitem>
***************
*** 101,123 ****
<para>
! As is typical of client/server applications, the client and the
! server can be on different hosts. In that case they communicate
! over a TCP/IP network connection. You should keep this in mind,
! because the files that can be accessed on a client machine might
! not be accessible (or might only be accessible using a different
! file name) on the database server machine.
</para>
<para>
! The <productname>PostgreSQL</productname> server can handle
! multiple concurrent connections from clients. For that purpose it
! starts (<quote>forks</quote>) a new process for each connection.
! From that point on, the client and the new server process
! communicate without intervention by the original
! <filename>postmaster</filename> process. Thus, the
! <filename>postmaster</filename> is always running, waiting for
! client connections, whereas client and associated server processes
! come and go. (All of this is of course invisible to the user. We
! only mention it here for completeness.)
</para>
</sect1>
--- 91,110 ----
<para>
! Jak w typowych aplikacjach klient/serwer, klient oraz serwer mog±
! znajdowaæ siê na ró¿nych komputerach. W takim wypadku korzystaj±
! z po³±czenia TCP/IP. Nale¿y o tym pamiêtaæ, gdy¿ pliki dostêpne na
! komputerze klienta mog± byæ niedostêpne na serwerze bazy danych
! (lub mog± byæ dostêpne pod inn± nazw±).
</para>
<para>
! Serwer <productname>PostgreSQL'a</productname> mo¿e odbieraæ wiele ¿±dañ
! od ró¿nych klientów. W tym celu rozpoczyna (<quote>forks</quote>) nowy
! proces dla ka¿dego po³±czenia. Od tego momentu klient i nowy
! proces serwera komunikuj± siê bez udzia³u oryginalnego
! procesu <filename>postmaster'a</filename>. Tak wiêc <filename>postmaster</filename> jest zawsze
! uruchomiony i czeka na po³±czenia od klientów, podczas gdy
! przydzielony klientowi proces serwera istnieje tylko przez pewien czas.
! (Wszystko to jest oczywi¶cie niewidoczne dla u¿ytkownika).
</para>
</sect1>
***************
*** 125,129 ****
<sect1 id="tutorial-createdb">
! <title>Creating a Database</title>
<indexterm zone="tutorial-createdb">
--- 112,116 ----
<sect1 id="tutorial-createdb">
! <title>Tworzenie bazy danych</title>
<indexterm zone="tutorial-createdb">
***************
*** 137,186 ****
<para>
! The first test to see whether you can access the database server
! is to try to create a database. A running
! <productname>PostgreSQL</productname> server can manage many
! databases. Typically, a separate database is used for each
! project or for each user.
</para>
<para>
! Possibly, your site administrator has already created a database
! for your use. He should have told you what the name of your
! database is. In this case you can omit this step and skip ahead
! to the next section.
</para>
<para>
! To create a new database, in this example named
! <literal>mydb</literal>, you use the following command:
<screen>
<prompt>$</prompt> <userinput>createdb mydb</userinput>
</screen>
! This should produce as response:
<screen>
CREATE DATABASE
</screen>
! If so, this step was successful and you can skip over the
! remainder of this section.
</para>
<para>
! If you see a message similar to
<screen>
createdb: command not found
</screen>
! then <productname>PostgreSQL</> was not installed properly. Either it was not
! installed at all or the search path was not set correctly. Try
! calling the command with an absolute path instead:
<screen>
<prompt>$</prompt> <userinput>/usr/local/pgsql/bin/createdb mydb</userinput>
</screen>
! The path at your site might be different. Contact your site
! administrator or check back in the installation instructions to
! correct the situation.
</para>
<para>
! Another response could be this:
<screen>
psql: could not connect to server: Connection refused
--- 124,170 ----
<para>
! Pierwszym sposobem sprawdzenia dostêpu do serwera jest próba
! utworzenia bazy danych. Uruchomiony serwer <productname>PostgreSQL</productname> mo¿e
! zarz±dzaæ wieloma bazami. Zazwyczaj osobne bazy s± stosowane dla
! ró¿nych projektów albo ró¿nych u¿ytkowników.
</para>
<para>
! Prawdopodobnie twój administrator ju¿ utworzy³ bazê danych dla Ciebie.
! Powinien on powiedzieæ Ci jaka jest nazwa tej bazy. W takim wypadku
! mo¿esz przej¶æ do nastêpnego rozdzia³u.
</para>
<para>
! Aby utworzyæ now± bazê danych, w tym przyk³adzie nazwan±
! <literal>mydb</literal>, zastosuj nastêpuj±ce polecenie:
<screen>
<prompt>$</prompt> <userinput>createdb mydb</userinput>
</screen>
! Powiniene¶ otrzymaæ nastêpuj±c± odpowied¼:
<screen>
CREATE DATABASE
</screen>
! Je¿eli ten krok zakoñczy³ siê powodzeniem mo¿esz opu¶ciæ resztê
! tego rozdzia³u.
</para>
<para>
! Je¿eli zobaczysz nastêpuj±cy komunikat:
<screen>
createdb: command not found
</screen>
! to <productname>PostgreSQL</> nie zosta³ zainstalowany prawid³owo. Ewentualnie
! nie w ca³o¶ci, albo ¶cie¿ka dostêpu zosta³a ¼le ustawiona. Spróbuj
! wywo³aæ polecenie podaj±c ca³± ¶cie¿kê dostêpu:
<screen>
<prompt>$</prompt> <userinput>/usr/local/pgsql/bin/createdb mydb</userinput>
</screen>
! U Ciebie ¶cie¿ka mo¿e byæ inna. Skontaktuj siê z administratorem
! lub zagl±dnij do opisu instalacji aby poprawiæ t± sytuacjê.
</para>
<para>
! Mo¿e wyst±piæ równie¿ taki komunikat:
<screen>
psql: could not connect to server: Connection refused
***************
*** 189,227 ****
createdb: database creation failed
</screen>
! This means that the server was not started, or it was not started
! where <command>createdb</command> expected it. Again, check the
! installation instructions or consult the administrator.
</para>
<para>
! If you do not have the privileges required to create a database,
! you will see the following:
<screen>
ERROR: CREATE DATABASE: permission denied
createdb: database creation failed
</screen>
! Not every user has authorization to create new databases. If
! <productname>PostgreSQL</productname> refuses to create databases
! for you then the site administrator needs to grant you permission
! to create databases. Consult your site administrator if this
! occurs. If you installed <productname>PostgreSQL</productname>
! yourself then you should log in for the purposes of this tutorial
! under the user account that you started the server as.
!
<footnote>
<para>
! As an explanation for why this works:
! <productname>PostgreSQL</productname> user names are separate
! from operating system user accounts. If you connect to a
! database, you can choose what
! <productname>PostgreSQL</productname> user name to connect as;
! if you don't, it will default to the same name as your current
! operating system account. As it happens, there will always be a
! <productname>PostgreSQL</productname> user account that has the
! same name as the operating system user that started the server,
! and it also happens that that user always has permission to
! create databases. Instead of logging in as that user you can
! also specify the <option>-U</option> option everywhere to select
! a <productname>PostgreSQL</productname> user name to connect as.
</para>
</footnote>
--- 173,209 ----
createdb: database creation failed
</screen>
! Oznacza to, ¿e serwer nie wystartowa³ albo nie zosta³
! uruchomiony tam gdzie spodziewa³ siê <command>createdb</command>.
! Sprawd¼ ponownie opis instalacji lub skonsultuj siê z
! administratorem.
</para>
<para>
! Je¿eli nie posiadasz uprawnieñ wymaganych do utworzenia bazy
! danych zobaczysz nastêpuj±cy komunikat:
<screen>
ERROR: CREATE DATABASE: permission denied
createdb: database creation failed
</screen>
! Nie ka¿dy u¿ytkownik ma uprawnienia do tworzenia baz danych.
! Je¶li <productname>PostgreSQL</productname> odmawia utworzenia bazy, wtedy administrator
! powinien nadaæ Ci takie uprawnienia. Je¿eli zajdzie taka potrzeba
! skontaktuj siê z administratorem. W przypadku gdy sam instalowa³e¶
! <productname>PostgreSQL'a</productname> powiniene¶ u¿yæ konta, na którym uruchomi³e¶
! serwer.
<footnote>
<para>
! Wyja¶nijmy zasadê dzia³ania:
! Nazwy u¿ytkowników <productname>PostgreSQL'a </productname> s± niezale¿ne od
! kont u¿ytkowników systemu operacyjnego. Gdy ³±czysz siê z baz±
! mo¿esz wybraæ na jakie konto <productname>PostgreSQL'a</productname> siê zalogujesz;
! Je¶li nie podasz nazwy u¿ytkownika, domy¶lnie zostanie
! przyjêta nazwa aktualnie zalogowanego w systemie
! operacyjnym u¿ytkownika. W takim wypadku, zawsze bêdzie
! konto <productname>PostgreSQL'a</productname> o nazwie takiej jak u¿ytkownik systemu
! operacyjnego, który uruchomi³ serwer. Najczê¶ciej bêdzie on mia³
! uprawnienia do tworzenia baz. Aby zalogowaæ siê do bazy jako
! wybrany u¿ytkownik nale¿y skorzystaæ z opcji <option>-U</option>
! i podaæ nazwê u¿ytkownika <productname>PostgreSQL'a</productname>.
</para>
</footnote>
***************
*** 229,240 ****
<para>
! You can also create databases with other names.
! <productname>PostgreSQL</productname> allows you to create any
! number of databases at a given site. Database names must have an
! alphabetic first character and are limited to 31 characters in
! length. A convenient choice is to create a database with the same
! name as your current user name. Many tools assume that database
! name as the default, so it can save you some typing. To create
! that database, simply type
<screen>
<prompt>$</prompt> <userinput>createdb</userinput>
--- 211,221 ----
<para>
! Mo¿esz równie¿ tworzyæ bazy z innymi nazwami.
! <productname>PostgreSQL</productname> zezwala ci na utworzenie dowolnej liczby baz na
! jednym serwerze. Nazwy baz danych musz± zaczynaæ siê od
! litery i s± ograniczone do 31 znaków. Wygodnym sposobem jest
! tworzenie baz danych z nazwami odpowiadaj±cymi nazwie
! u¿ytkownika. Wiele narzêdzi przyjmuje tak± nazwê domy¶lnie.
! Aby w prosty sposób utworzyæ bazê, wpisz:
<screen>
<prompt>$</prompt> <userinput>createdb</userinput>
***************
*** 243,258 ****
<para>
! If you don't want to use your database anymore you can remove it.
! For example, if you are the owner (creator) of the database
! <literal>mydb</literal>, you can destroy it using the following
! command:
<screen>
<prompt>$</prompt> <userinput>dropdb mydb</userinput>
</screen>
! (For this command, the database name does not default to the user
! account name. You always need to specify it.) This action
! physically removes all files associated with the database and
! cannot be undone, so this should only be done with a great deal of
! forethought.
</para>
</sect1>
--- 224,237 ----
<para>
! Gdy nie bêdziesz ju¿ chcia³ u¿ywaæ swojej bazy mo¿esz j± usun±æ.
! Na przyk³ad, je¶li jestej w³a¶cicielem (tym który j± utworzy³) bazy
! <literal>mydb</literal>, mo¿esz j± usun±æ przy u¿yciu nastêpuj±cego polecenia:
<screen>
<prompt>$</prompt> <userinput>dropdb mydb</userinput>
</screen>
! (To polecenie nie przyjmuje domy¶lnie nazwy bazy danych,
! zawsze musisz j± podawaæ wprost). Czynno¶æ ta fizycznie
! usuwa wszystkie pliki nale¿±ce do bazy i jest nieodwracalna,
! wiêc nale¿y j± stosowaæ z ostro¿no¶ci±.
</para>
</sect1>
***************
*** 260,264 ****
<sect1 id="tutorial-accessdb">
! <title>Accessing a Database</title>
<indexterm zone="tutorial-accessdb">
--- 239,243 ----
<sect1 id="tutorial-accessdb">
! <title>Dostêp do bazy danych</title>
<indexterm zone="tutorial-accessdb">
***************
*** 267,279 ****
<para>
! Once you have created a database, you can access it by:
<itemizedlist spacing="compact" mark="bullet">
<listitem>
<para>
! Running the <productname>PostgreSQL</productname> interactive
! terminal program, called <application><firstterm>psql</></application>, which allows you
! to interactively enter, edit, and execute
! <acronym>SQL</acronym> commands.
</para>
</listitem>
--- 246,257 ----
<para>
! Po utworzenie bazy mo¿esz mieæ do niej dostêp przez:
<itemizedlist spacing="compact" mark="bullet">
<listitem>
<para>
! Uruchomienie interaktywnego terminala <productname>PostgreSQL</productname>
! o nazwie <application><firstterm>psql</></application>, który zezwala na wprowadzanie, edycjê
! i wykonywanie poleceñ <acronym>SQL</acronym>.
</para>
</listitem>
***************
*** 281,289 ****
<listitem>
<para>
! Using an existing graphical frontend tool like
! <application>PgAccess</application> or
! <application>ApplixWare</application> (via
! <acronym>ODBC</acronym>) to create and manipulate a database.
! These possibilities are not covered in this tutorial.
</para>
</listitem>
--- 259,266 ----
<listitem>
<para>
! U¿ycie istniej±cych narzêdzi graficznych jak <application>PgAccess</application>
! or <application>ApplixWare</application> (przez <acronym>ODBC</acronym>) do tworzenia i zarz±dzania
! baz± danych. Ich mo¿liwo¶ci nie s± opisane w niniejszym
! opracowaniu.
</para>
</listitem>
***************
*** 291,352 ****
<listitem>
<para>
! Writing a custom application, using one of the several
! available language bindings. These possibilities are discussed
! further in <citetitle>The PostgreSQL Programmer's
! Guide</citetitle>.
</para>
</listitem>
</itemizedlist>
! You probably want to start up <command>psql</command>, to try out
! the examples in this tutorial. It can be activated for the
! <literal>mydb</literal> database by typing the command:
<screen>
<prompt>$</prompt> <userinput>psql mydb</userinput>
</screen>
! If you leave off the database name then it will default to your
! user account name. You already discovered this scheme in the
! previous section.
</para>
<para>
! In <command>psql</command>, you will be greeted with the following
! message:
<screen>
! Welcome to psql, the PostgreSQL interactive terminal.
!
! Type: \copyright for distribution terms
! \h for help with SQL commands
! \? for help on internal slash commands
! \g or terminate with semicolon to execute query
! \q to quit
mydb=>
</screen>
<indexterm><primary>superuser</primary></indexterm>
! The last line could also be
<screen>
mydb=#
</screen>
! That would mean you are a database superuser, which is most likely
! the case if you installed <productname>PostgreSQL</productname>
! yourself. Being a superuser means that you are not subject to
! access controls. For the purpose of this tutorial this is not of
! importance.
</para>
<para>
! If you have encountered problems starting <command>psql</command>
! then go back to the previous section. The diagnostics of
! <command>psql</command> and <command>createdb</command> are
! similar, and if the latter worked the former should work as well.
</para>
<para>
! The last line printed out by <command>psql</command> is the
! prompt, and it indicates that <command>psql</command> is listening
! to you and that you can type <acronym>SQL</acronym> queries into a
! work space maintained by <command>psql</command>. Try out these
! commands:
<indexterm><primary>version</primary></indexterm>
<screen>
--- 268,324 ----
<listitem>
<para>
! Napisanie w³asnej aplikacji przy zastosowaniu jednego z wielu
! dostêpnych wbudowanych jêzyków. Ta mo¿liwo¶æ jest opisana
! szerzej w <citetitle>Podrêczniku Programisty</citetitle>.
</para>
</listitem>
</itemizedlist>
! Prawdopodobnie zechcesz uruchomiæ <command>psql</command>, aby sprawdziæ
! przyk³ady podane w tym podrêczniku. Bazê <literal>mydb</literal>
! mo¿na uruchomiæ poleceniem:
<screen>
<prompt>$</prompt> <userinput>psql mydb</userinput>
</screen>
! Gdy nie podasz nazwy bazy zostanie przyjêta domy¶lnie nazwa
! twojego konta. Powiniene¶ o tym przeczytaæ w poprzednim rozdziale.
</para>
<para>
! Program <command>psql</command> powita Ciê komunikatem:
<screen>
! Witamy w psql, interaktywnym programie do komunikowania siê z serwerem PostgreSQL.
!
! Wpisz: \copyright aby przeczytaæ informacje prawne
! \h aby uzyskaæ pomoc do poleceñ SQL
! \? aby uzyskaæ pomoc do poleceñ wewnêtrznych
! \g lub ¶rednik, aby zakoñczyæ i wykonaæ zapytanie SQL
! \q aby wyj¶æ
mydb=>
</screen>
<indexterm><primary>superuser</primary></indexterm>
! Ostatnia linia mo¿e równie¿ wygl±daæ tak:
<screen>
mydb=#
</screen>
! Oznacza to, ¿e jeste¶ administratorem tej bazy, co jest
! bardzo prawdopodobne je¶li to ty instalowa³e¶ <productname>PostgreSQL</productname>.
! Bycie administratorem oznacza, ¿e nie podlegasz kontroli dostêpu.
! Z punktu widzenia niniejszego opracowania nie jest to istotne.
</para>
<para>
! Je¶li napotka³e¶ problemy podczas uruchomienia <command>psql</command>
! wróæ do wcze¶niejszego rozdzia³u. Diagnozowanie <command>psql</command>
! i <command>createdb</command> jest podobne, je¶li dzia³a drugie, to pierwsze
! te¿ bêdzie dzia³aæ.
</para>
<para>
! Ostatnia linia wy¶wietlona przez <command>psql</command> jest znakiem
! zachêty i oznacza, ¿e <command>psql</command> oczekuje na wprowadzenie
! zapytañ <acronym>SQL</acronym> do obszaru roboczego utworzonego przez
! <command>psql</command>. Spróbuj wpisaæ poni¿sze polecenia:
<indexterm><primary>version</primary></indexterm>
<screen>
***************
*** 372,382 ****
<para>
! The <command>psql</command> program has a number of internal
! commands that are not SQL commands. They begin with the backslash
! character, <quote><literal>\</literal></quote>. Some of these
! commands were listed in the welcome message. For example,
! you can get help on the syntax of various
! <productname>PostgreSQL</productname> <acronym>SQL</acronym>
! commands by typing:
<screen>
<prompt>mydb=></prompt> <userinput>\h</userinput>
--- 344,352 ----
<para>
! Program <command>psql</command> posiada pewn± liczbê poleceñ, które nie s±
! poleceniami SQL. Zaczynaj± siê znakiem <quote><literal>\</literal></quote>. Niektóre
! z nich s± zawarte w powitalnym komunikacie. Na przyk³ad, mo¿esz
! przegl±daæ pomoc na temat sk³adni ró¿nych komend
! <productname>Postgresowego</productname> <acronym>SQL</acronym> po wpisaniu:
<screen>
<prompt>mydb=></prompt> <userinput>\h</userinput>
***************
*** 385,402 ****
<para>
! To get out of <command>psql</command>, type
<screen>
<prompt>mydb=></prompt> <userinput>\q</userinput>
</screen>
! and <command>psql</command> will quit and return you to your
! command shell. (For more internal commands, type
! <literal>\?</literal> at the <command>psql</command> prompt.) The
! full capabilities of <command>psql</command> are documented in the
! <citetitle>Reference Manual</citetitle>. If <productname>PostgreSQL</> is
! installed correctly you can also type <literal>man psql</literal>
! at the operating system shell prompt to see the documentation. In
! this tutorial we will not use these features explicitly, but you
! can use them yourself when you see fit.
! </para>
</sect1>
--- 355,369 ----
<para>
! Aby zakoñczyæ <command>psql</command>, wpisz:
<screen>
<prompt>mydb=></prompt> <userinput>\q</userinput>
</screen>
! a <command>psql</command> zakoñczy pracê i powróci do wiersza poleceñ.
! (Wiêcej wewnêtrznych poleceñ poznasz wpisuj±c <literal>\?</literal>
! w wierszu poleceñ <command>psql'a</command>.) Wszystkie mo¿liwo¶ci
! <command>psql'a</command> s± opisane w <citetitle>Podrêczniku U¿ytkownika</citetitle>.
! Je¶li <productname>PostgreSQL</> zosta³ zainstalowany prawid³owo mo¿esz
! tak¿e u¿ywaæ <literal>man psql</literal> w lini poleceñ systemu operacyjnego.
! </para>
</sect1>
|
|
From: <ma...@us...> - 2002-06-07 06:23:01
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv483 Modified Files: postgres.po Log Message: komunikaty od a.l.k.a Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.18 retrieving revision 1.19 diff -C2 -d -r1.18 -r1.19 *** postgres.po 26 May 2002 18:06:35 -0000 1.18 --- postgres.po 7 Jun 2002 06:22:54 -0000 1.19 *************** *** 7,11 **** "POT-Creation-Date: 2002-05-06 18:20-0200\n" "PO-Revision-Date: 2002-05-07 18:16-0200\n" ! "Last-Translator: Marcin Marurek <m.m...@ne...>\n" "Language-Team: polishpgdoc\n" "MIME-Version: 1.0\n" --- 7,11 ---- "POT-Creation-Date: 2002-05-06 18:20-0200\n" "PO-Revision-Date: 2002-05-07 18:16-0200\n" ! "Last-Translator: Aleksander Machniak (A.L.E.C) ama...@go...\n" "Language-Team: polishpgdoc\n" [...1721 lines suppressed...] msgid "ANALYZE: there is no attribute %s in %s" ! msgstr "" #: ../commands/analyze.c:417 ../utils/adt/ruleutils.c:1880 --- 5427,5441 ---- #, c-format msgid "Skipping \"%s\" --- only table or database owner can ANALYZE it" ! msgstr "Opuszczam \"%s\" --- tylko w³aciciel tabeli lub bazy mo¿e j¹ ANALIZOWAÆ" #: ../commands/analyze.c:217 #, c-format msgid "Analyzing %s" ! msgstr "Analizowanie %s" #: ../commands/analyze.c:244 #, c-format msgid "ANALYZE: there is no attribute %s in %s" ! msgstr "ANALYZE: nie ma atrybutu %s w %s" #: ../commands/analyze.c:417 ../utils/adt/ruleutils.c:1880 |
|
From: <ma...@us...> - 2002-05-26 18:06:43
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv3384 Modified Files: postgres.po Log Message: kolejne... Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.17 retrieving revision 1.18 diff -C2 -d -r1.17 -r1.18 *** postgres.po 26 May 2002 13:50:49 -0000 1.17 --- postgres.po 26 May 2002 18:06:35 -0000 1.18 *************** *** 431,435 **** #, c-format msgid "SignalChildren: sending signal %d to process %d" ! msgstr "SignalChildren: wysy³am sygna³ %s do procesu %d" #: ../postmaster/postmaster.c:1842 --- 431,435 ---- #, c-format msgid "SignalChildren: sending signal %d to process %d" ! msgstr "SignalChildren: wysy³am sygna³ %d do procesu %d" #: ../postmaster/postmaster.c:1842 *************** *** 453,457 **** #: ../postmaster/postmaster.c:1935 msgid "Server process fork() failed: " ! msgstr "" #: ../postmaster/postmaster.c:2060 --- 453,457 ---- #: ../postmaster/postmaster.c:1935 msgid "Server process fork() failed: " ! msgstr "fork() procesu serwera nie powiód³ siê: " #: ../postmaster/postmaster.c:2060 *************** *** 471,505 **** #, c-format msgid "failed to create SSL context: %s" ! msgstr "" #: ../postmaster/postmaster.c:2451 #, c-format msgid "failed to load server certificate (%s): %s" ! msgstr "" #: ../postmaster/postmaster.c:2458 #, c-format msgid "failed to load private key file (%s): %s" ! msgstr "" #: ../postmaster/postmaster.c:2464 #, c-format msgid "check of private key failed: %s" ! msgstr "" #: ../postmaster/postmaster.c:2593 #, c-format msgid "could not launch startup process (fork failure): %s" ! msgstr "" #: ../postmaster/postmaster.c:2597 #, c-format msgid "could not launch checkpoint process (fork failure): %s" ! msgstr "" #: ../postmaster/postmaster.c:2602 #, c-format msgid "could not launch shutdown process (fork failure): %s" ! msgstr "" #: ../postmaster/postmaster.c:2625 --- 471,505 ---- #, c-format msgid "failed to create SSL context: %s" ! msgstr "nie uda³o siê stworzyæ kontekstu SSL: %s" #: ../postmaster/postmaster.c:2451 #, c-format msgid "failed to load server certificate (%s): %s" ! msgstr "nie uda³o siê za³adowaæ certyfikatu serwera (%s): %s" #: ../postmaster/postmaster.c:2458 #, c-format msgid "failed to load private key file (%s): %s" ! msgstr "nie uda³o siê za³adowaæ pliku klucza prywatnego (%s): %s" #: ../postmaster/postmaster.c:2464 #, c-format msgid "check of private key failed: %s" ! msgstr "sprawdzanie klucza prywatnego nie powiod³o siê: %s" #: ../postmaster/postmaster.c:2593 #, c-format msgid "could not launch startup process (fork failure): %s" ! msgstr "nie mo¿na uruchomiæ procesu startowego (b³±d fork): %s" #: ../postmaster/postmaster.c:2597 #, c-format msgid "could not launch checkpoint process (fork failure): %s" ! msgstr "nie mo¿na uruchomiæ procesu checkpoint (b³±d fork): %s" #: ../postmaster/postmaster.c:2602 #, c-format msgid "could not launch shutdown process (fork failure): %s" ! msgstr "nie mo¿na uruchomiæ procesu zamykaj±cego (b³±d fork): %s" #: ../postmaster/postmaster.c:2625 *************** *** 520,534 **** #, c-format msgid "coerce_type: conversion function %s produced %s" ! msgstr "" #: ../parser/parse_coerce.c:388 #, c-format msgid "%s types \"%s\" and \"%s\" not matched" ! msgstr "" #: ../parser/parse_coerce.c:443 #, c-format msgid "%s unable to convert to type \"%s\"" ! msgstr "" #: ../parser/parse_clause.c:189 --- 520,534 ---- #, c-format msgid "coerce_type: conversion function %s produced %s" ! msgstr "coerce_type: funkcja konwersji %s zwróci³a %s" #: ../parser/parse_coerce.c:388 #, c-format msgid "%s types \"%s\" and \"%s\" not matched" ! msgstr "%s typy \"%s\" oraz \"%s\" nie zgadaj± siê" #: ../parser/parse_coerce.c:443 #, c-format msgid "%s unable to convert to type \"%s\"" ! msgstr "%s nie mo¿na dokonaæ konwersji do typu \"%s\"" #: ../parser/parse_clause.c:189 *************** *** 549,589 **** #, c-format msgid "JOIN/ON clause refers to \"%s\", which is not part of JOIN" ! msgstr "" #: ../parser/parse_clause.c:412 msgid "sub-select in FROM must have an alias" ! msgstr "" #: ../parser/parse_clause.c:434 ../parser/parse_clause.c:437 msgid "Unexpected parse analysis result for subselect in FROM" ! msgstr "" #: ../parser/parse_clause.c:440 msgid "Expected SELECT query from subselect in FROM" ! msgstr "" #: ../parser/parse_clause.c:442 msgid "Subselect in FROM may not have SELECT INTO" ! msgstr "" #: ../parser/parse_clause.c:642 #, c-format msgid "Common column name \"%s\" appears more than once in left table" ! msgstr "" #: ../parser/parse_clause.c:648 #, c-format msgid "JOIN/USING column \"%s\" not found in left table" ! msgstr "" #: ../parser/parse_clause.c:659 #, c-format msgid "Common column name \"%s\" appears more than once in right table" ! msgstr "" #: ../parser/parse_clause.c:665 #, c-format msgid "JOIN/USING column \"%s\" not found in right table" ! msgstr "" #: ../parser/parse_clause.c:743 --- 549,589 ---- #, c-format msgid "JOIN/ON clause refers to \"%s\", which is not part of JOIN" ! msgstr "JOIN/ON odnosi siê do \"%s\", który nie jest czê¶ci± JOIN" #: ../parser/parse_clause.c:412 msgid "sub-select in FROM must have an alias" ! msgstr "podzapytanie we FROM musi mieæ alias" #: ../parser/parse_clause.c:434 ../parser/parse_clause.c:437 msgid "Unexpected parse analysis result for subselect in FROM" ! msgstr "Nieoczekiwane wyniki analizy parsowania podzapytania we FROM" #: ../parser/parse_clause.c:440 msgid "Expected SELECT query from subselect in FROM" ! msgstr "Oczekiwano zapytania SELECT w podzapytaniu we FROM" #: ../parser/parse_clause.c:442 msgid "Subselect in FROM may not have SELECT INTO" ! msgstr "Podzapytanie we FROM nie mo¿a zawieraæ SELECT INTO" #: ../parser/parse_clause.c:642 #, c-format msgid "Common column name \"%s\" appears more than once in left table" ! msgstr "Nazwa kolumny \"%s\" pojawia siê wiêcej ni¿ raz w lewej tabeli" #: ../parser/parse_clause.c:648 #, c-format msgid "JOIN/USING column \"%s\" not found in left table" ! msgstr "Kolumna \"%s\" w JOIN/USING nie zosta³a odnaleziona w lewej tabeli" #: ../parser/parse_clause.c:659 #, c-format msgid "Common column name \"%s\" appears more than once in right table" ! msgstr "Nazwa kolumny \"%s\" pojawia siê wiêcej ni¿ raz w prawej tabeli" #: ../parser/parse_clause.c:665 #, c-format msgid "JOIN/USING column \"%s\" not found in right table" ! msgstr "Kolumna \"%s\" w JOIN/USING nie zosta³a odnaleziona w prawej tabeli" #: ../parser/parse_clause.c:743 *************** *** 11782,11786 **** #, c-format msgid "ProcedureCreate: you do not have permission to replace function %s" ! msgstr ""ProcedureCreate: nie masz uprawnieñ do zamiany funkcji %s" #: ../catalog/pg_proc.c:320 --- 11782,11786 ---- #, c-format msgid "ProcedureCreate: you do not have permission to replace function %s" ! msgstr "ProcedureCreate: nie masz uprawnieñ do zamiany funkcji %s" #: ../catalog/pg_proc.c:320 |
|
From: <ma...@us...> - 2002-05-26 13:50:57
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv10981 Modified Files: postgres.po Log Message: Kilka komunikatów. Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.16 retrieving revision 1.17 diff -C2 -d -r1.16 -r1.17 *** postgres.po 25 May 2002 17:43:24 -0000 1.16 --- postgres.po 26 May 2002 13:50:49 -0000 1.17 *************** *** 358,366 **** #: ../postmaster/postmaster.c:1469 msgid "aborting any active transactions" ! msgstr "" #: ../postmaster/postmaster.c:1505 msgid "immediate shutdown request" ! msgstr "" #: ../postmaster/postmaster.c:1541 --- 358,366 ---- #: ../postmaster/postmaster.c:1469 msgid "aborting any active transactions" ! msgstr "przerwanie wszystkich aktywnych transakcji" #: ../postmaster/postmaster.c:1505 msgid "immediate shutdown request" ! msgstr "¿adanie natychmiastowego zamkniêcia" #: ../postmaster/postmaster.c:1541 *************** *** 374,382 **** #: ../postmaster/postmaster.c:1571 msgid "shutdown process" ! msgstr "" #: ../postmaster/postmaster.c:1582 msgid "startup process" ! msgstr "" #: ../postmaster/postmaster.c:1584 --- 374,382 ---- #: ../postmaster/postmaster.c:1571 msgid "shutdown process" ! msgstr "zamykanie procesu" #: ../postmaster/postmaster.c:1582 msgid "startup process" ! msgstr "start procesu" #: ../postmaster/postmaster.c:1584 *************** *** 393,396 **** --- 393,398 ---- "all server processes terminated; reinitializing shared memory and semaphores" msgstr "" + "wszystkie procesy serwera zosta³y przerwane;\n" + "reinicjalizacja pamiêci dzielonej oraz semaforów" #: ../postmaster/postmaster.c:1664 *************** *** 503,517 **** #: ../postmaster/postmaster.c:2625 msgid "CheckPointDataBase: malloc failed" ! msgstr "" #: ../postmaster/postmaster.c:2665 #, c-format msgid "cannot create file %s: %s" ! msgstr "" #: ../postmaster/postmaster.c:2677 #, c-format msgid "writing file %s failed" ! msgstr "" #: ../parser/parse_coerce.c:136 --- 505,519 ---- #: ../postmaster/postmaster.c:2625 msgid "CheckPointDataBase: malloc failed" ! msgstr "CheckPointDataBase: wykonanie funkcji malloc nie powiod³o siê" #: ../postmaster/postmaster.c:2665 #, c-format msgid "cannot create file %s: %s" ! msgstr "nie mo¿na utworzyæ pliku %s: %s" #: ../postmaster/postmaster.c:2677 #, c-format msgid "writing file %s failed" ! msgstr "zapis pliku %s nie powiód³ siê" #: ../parser/parse_coerce.c:136 *************** *** 537,546 **** #, c-format msgid "JOIN/USING clause must return type boolean, not type %s" ! msgstr "" #: ../parser/parse_clause.c:332 #, c-format msgid "JOIN/ON clause must return type boolean, not type %s" ! msgstr "" #: ../parser/parse_clause.c:352 --- 539,548 ---- #, c-format msgid "JOIN/USING clause must return type boolean, not type %s" ! msgstr "JOIN/USING musi zwracaæ warto¶æ typu boolean, a nie %s" #: ../parser/parse_clause.c:332 #, c-format msgid "JOIN/ON clause must return type boolean, not type %s" ! msgstr "JOIN/ON musi zwracaæ warto¶æ typu boolean, a nie %s" #: ../parser/parse_clause.c:352 *************** *** 600,604 **** #, c-format msgid "WHERE clause must return type boolean, not type %s" ! msgstr "" #: ../parser/parse_clause.c:873 --- 602,606 ---- #, c-format msgid "WHERE clause must return type boolean, not type %s" ! msgstr "WHERE musi zwracaæ warto¶æ typu boolean, a nie %s" #: ../parser/parse_clause.c:873 *************** *** 635,643 **** #, c-format msgid "%s" ! msgstr "" #: scan.l:283 msgid "Unterminated /* comment" ! msgstr "" #: scan.l:293 --- 637,645 ---- #, c-format msgid "%s" ! msgstr "%s" #: scan.l:283 msgid "Unterminated /* comment" ! msgstr "Niezakoñczony /* komentarz" #: scan.l:293 *************** *** 892,900 **** #: gram.y:741 msgid "ALTER SCHEMA not yet supported" ! msgstr "" #: gram.y:851 msgid "SET must have at least one argument" ! msgstr "" #: gram.y:896 gram.y:907 --- 894,902 ---- #: gram.y:741 msgid "ALTER SCHEMA not yet supported" ! msgstr "ALTER SCHEMA nie jest jeszcze wspierane" #: gram.y:851 msgid "SET must have at least one argument" ! msgstr "SET musi mieæ przynajmniej jeden argument" #: gram.y:896 gram.y:907 *************** *** 904,917 **** #: gram.y:1276 gram.y:1281 gram.y:3614 gram.y:3619 msgid "GLOBAL TEMPORARY TABLE is not currently supported" ! msgstr "" #: gram.y:1316 #, c-format msgid "CREATE TABLE / COLLATE %s not yet implemented; clause ignored" ! msgstr "" #: gram.y:1572 msgid "FOREIGN KEY/MATCH PARTIAL not yet implemented" ! msgstr "" #: gram.y:1627 --- 906,919 ---- #: gram.y:1276 gram.y:1281 gram.y:3614 gram.y:3619 msgid "GLOBAL TEMPORARY TABLE is not currently supported" ! msgstr "GLOBAL TEMPORARY TABLE nie jest jeszcze wspierane" #: gram.y:1316 #, c-format msgid "CREATE TABLE / COLLATE %s not yet implemented; clause ignored" ! msgstr "CREATE TABLE / COLLATE %s nie jest jeszcze wspierane; zignorowane" #: gram.y:1572 msgid "FOREIGN KEY/MATCH PARTIAL not yet implemented" ! msgstr "FOREIGN KEY/MATCH PARTIAL nie jest jeszcze wspierane" #: gram.y:1627 *************** *** 921,925 **** #: gram.y:1927 gram.y:1940 ../parser/analyze.c:3141 ../parser/analyze.c:3159 msgid "INITIALLY DEFERRED constraint must be DEFERRABLE" ! msgstr "" #: gram.y:2186 --- 923,927 ---- #: gram.y:1927 gram.y:1940 ../parser/analyze.c:3141 ../parser/analyze.c:3159 msgid "INITIALLY DEFERRED constraint must be DEFERRABLE" ! msgstr "Ograniczenie INITIALLY DEFERRED musi byæ DEFERRABLE" #: gram.y:2186 |
|
From: <ma...@us...> - 2002-05-25 17:43:27
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv27524 Modified Files: postgres.po Log Message: kolejna paczka Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.15 retrieving revision 1.16 diff -C2 -d -r1.15 -r1.16 *** postgres.po 25 May 2002 17:30:15 -0000 1.15 --- postgres.po 25 May 2002 17:43:24 -0000 1.16 *************** *** 295,358 **** #: ../postmaster/postmaster.c:1170 msgid "no PostgreSQL user name specified in startup packet" ! msgstr "" #: ../postmaster/postmaster.c:1182 msgid "The database system is starting up" ! msgstr "" #: ../postmaster/postmaster.c:1185 msgid "The database system is shutting down" ! msgstr "" #: ../postmaster/postmaster.c:1188 msgid "The database system is in recovery mode" ! msgstr "" #: ../postmaster/postmaster.c:1191 ../storage/ipc/sinval.c:53 #: ../storage/lmgr/proc.c:1098 msgid "Sorry, too many clients already" ! msgstr "" #: ../postmaster/postmaster.c:1222 #, c-format msgid "processCancelRequest: CheckPointPID in cancel request for process %d" ! msgstr "" #: ../postmaster/postmaster.c:1237 #, c-format msgid "processing cancel request: sending SIGINT to process %d" ! msgstr "" #: ../postmaster/postmaster.c:1245 #, c-format msgid "bad key in cancel request for process %d" ! msgstr "" #: ../postmaster/postmaster.c:1254 #, c-format msgid "bad pid in cancel request for process %d" ! msgstr "" #: ../postmaster/postmaster.c:1297 msgid "ConnCreate: malloc failed" ! msgstr "" #: ../postmaster/postmaster.c:1419 #, c-format msgid "pmdie %d" ! msgstr "" #: ../postmaster/postmaster.c:1433 msgid "smart shutdown request" ! msgstr "" #: ../postmaster/postmaster.c:1445 ../postmaster/postmaster.c:1489 #, c-format msgid "shutdown process %d already running" ! msgstr "" #: ../postmaster/postmaster.c:1463 msgid "fast shutdown request" ! msgstr "" #: ../postmaster/postmaster.c:1469 --- 295,358 ---- #: ../postmaster/postmaster.c:1170 msgid "no PostgreSQL user name specified in startup packet" ! msgstr "nie podano nazwy u¿ytkownika PostgreSQL w pakiecie startowym" #: ../postmaster/postmaster.c:1182 msgid "The database system is starting up" ! msgstr "Baza danych uruchamia siê" #: ../postmaster/postmaster.c:1185 msgid "The database system is shutting down" ! msgstr "Baza danych zamyka siê" #: ../postmaster/postmaster.c:1188 msgid "The database system is in recovery mode" ! msgstr "BAza danych jest w trybie odzyskiwania" #: ../postmaster/postmaster.c:1191 ../storage/ipc/sinval.c:53 #: ../storage/lmgr/proc.c:1098 msgid "Sorry, too many clients already" ! msgstr "Przykro mi, jest ju¿ za du¿o klientów" #: ../postmaster/postmaster.c:1222 #, c-format msgid "processCancelRequest: CheckPointPID in cancel request for process %d" ! msgstr "processCancelReques: CheckPointPID w ¿±daniu anulowania dla procesu %d" #: ../postmaster/postmaster.c:1237 #, c-format msgid "processing cancel request: sending SIGINT to process %d" ! msgstr "przetwarzanie ¿±danie anulowania: wysy³anie sygna³u SIGINT do procesu %d" #: ../postmaster/postmaster.c:1245 #, c-format msgid "bad key in cancel request for process %d" ! msgstr "z³y klucz w ¿adaniu anulowania dla procesu %d" #: ../postmaster/postmaster.c:1254 #, c-format msgid "bad pid in cancel request for process %d" ! msgstr "z³y pid w ¿±daniu anulowania dla procesu %d" #: ../postmaster/postmaster.c:1297 msgid "ConnCreate: malloc failed" ! msgstr "ConnCreate: malloc nie powiód³ siê" #: ../postmaster/postmaster.c:1419 #, c-format msgid "pmdie %d" ! msgstr "pmdie %d" #: ../postmaster/postmaster.c:1433 msgid "smart shutdown request" ! msgstr "¿±danie sprytnego zamkniêcia" #: ../postmaster/postmaster.c:1445 ../postmaster/postmaster.c:1489 #, c-format msgid "shutdown process %d already running" ! msgstr "proces zamykania %d jest ju¿ uruchomiony" #: ../postmaster/postmaster.c:1463 msgid "fast shutdown request" ! msgstr "¿±danie szybkiego zamkniêcia" #: ../postmaster/postmaster.c:1469 |
|
From: <ma...@us...> - 2002-05-25 17:30:21
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv25617 Modified Files: postgres.po Log Message: kolejna paczka Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.14 retrieving revision 1.15 diff -C2 -d -r1.14 -r1.15 *** postgres.po 24 May 2002 17:42:38 -0000 1.14 --- postgres.po 25 May 2002 17:30:15 -0000 1.15 *************** *** 231,235 **** " -S silent mode (start in background without logging output)\n" msgstr "" ! " -S tyb cichy (startuje w tle bez logowania wyniku)\n" #: ../postmaster/postmaster.c:852 --- 231,235 ---- " -S silent mode (start in background without logging output)\n" msgstr "" ! " -S tryb cichy (startuje w tle bez logowania wyniku)\n" #: ../postmaster/postmaster.c:852 *************** *** 245,252 **** " -n do not reinitialize shared memory after abnormal exit\n" msgstr "" #: ../postmaster/postmaster.c:854 msgid " -s send SIGSTOP to all backend servers if one dies\n" ! msgstr "" #: ../postmaster/postmaster.c:856 --- 245,253 ---- " -n do not reinitialize shared memory after abnormal exit\n" msgstr "" + " -n nie inicjuj ponownie pamiêci dzielonej po nienormalnym zakoñczeniu pracy\n" #: ../postmaster/postmaster.c:854 msgid " -s send SIGSTOP to all backend servers if one dies\n" ! msgstr " -s wy¶lij sygna³ SIGSTOP do wszystkich serwerów, je¿eli jeden zginie\n" #: ../postmaster/postmaster.c:856 *************** *** 259,289 **** "Report bugs to <pgs...@po...>.\n" msgstr "" #: ../postmaster/postmaster.c:938 #, c-format msgid "ServerLoop: select failed: %m" ! msgstr "" #: ../postmaster/postmaster.c:1064 ../postmaster/postmaster.c:1078 msgid "incomplete startup packet" ! msgstr "" #: ../postmaster/postmaster.c:1072 msgid "invalid length of startup packet" ! msgstr "" #: ../postmaster/postmaster.c:1111 #, c-format msgid "failed to send SSL negotiation response: %s" ! msgstr "" #: ../postmaster/postmaster.c:1123 #, c-format msgid "failed to initialize SSL connection: %s (%m)" ! msgstr "" #: ../postmaster/postmaster.c:1143 msgid "unsupported frontend protocol" ! msgstr "" #: ../postmaster/postmaster.c:1170 --- 260,295 ---- "Report bugs to <pgs...@po...>.\n" msgstr "" + "\n" + "Proszê przeczytaæ dokumentacjê, aby poznaæ kompletn± listê opcji\n" + "konfiguracyjnych oraz jak je ustawiaæ zarówno z linii poleceñ jak i\n" + "w pliku konfiguracyjnym.\n" + "\n" #: ../postmaster/postmaster.c:938 #, c-format msgid "ServerLoop: select failed: %m" ! msgstr "ServerLoop: select nie powiód³ siê: %m" #: ../postmaster/postmaster.c:1064 ../postmaster/postmaster.c:1078 msgid "incomplete startup packet" ! msgstr "niepe³ny pakiet startowy" #: ../postmaster/postmaster.c:1072 msgid "invalid length of startup packet" ! msgstr "nieprawid³owa d³ugo¶æ pakietu startowego" #: ../postmaster/postmaster.c:1111 #, c-format msgid "failed to send SSL negotiation response: %s" ! msgstr "nie uda³o siê wys³aæ odpowiedzi negocjacyjnej SSL: %s" #: ../postmaster/postmaster.c:1123 #, c-format msgid "failed to initialize SSL connection: %s (%m)" ! msgstr "nie uda³o siê zainicjowaæ po³±czenia SSL: %s (%m)" #: ../postmaster/postmaster.c:1143 msgid "unsupported frontend protocol" ! msgstr "protokó³ klienta nie jest obs³ugiwany" #: ../postmaster/postmaster.c:1170 |
|
From: <ma...@us...> - 2002-05-24 17:42:42
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv2997 Modified Files: postgres.po Log Message: Kolejne komunikaty. Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.13 retrieving revision 1.14 diff -C2 -d -r1.13 -r1.14 *** postgres.po 24 May 2002 17:34:43 -0000 1.13 --- postgres.po 24 May 2002 17:42:38 -0000 1.14 *************** *** 390,440 **** #: ../postmaster/postmaster.c:1664 msgid "child process" ! msgstr "" #: ../postmaster/postmaster.c:1709 msgid "server process" ! msgstr "" #: ../postmaster/postmaster.c:1710 msgid "terminating any other active server processes" ! msgstr "" #: ../postmaster/postmaster.c:1732 #, c-format msgid "CleanupProc: sending %s to process %d" ! msgstr "" #: ../postmaster/postmaster.c:1777 #, c-format msgid "%s (pid %d) exited with exit code %d" ! msgstr "" #: ../postmaster/postmaster.c:1780 #, c-format msgid "%s (pid %d) was terminated by signal %d" ! msgstr "" #: ../postmaster/postmaster.c:1783 #, c-format msgid "%s (pid %d) exited with unexpected status %d" ! msgstr "" #: ../postmaster/postmaster.c:1807 #, c-format msgid "SignalChildren: sending signal %d to process %d" ! msgstr "" #: ../postmaster/postmaster.c:1842 msgid "out of memory; connection startup aborted" ! msgstr "" #: ../postmaster/postmaster.c:1877 msgid "connection startup failed" ! msgstr "" #: ../postmaster/postmaster.c:1894 #, c-format msgid "connection startup failed (fork failure): %s" ! msgstr "" #: ../postmaster/postmaster.c:1902 --- 390,440 ---- #: ../postmaster/postmaster.c:1664 msgid "child process" ! msgstr "proces potomny" #: ../postmaster/postmaster.c:1709 msgid "server process" ! msgstr "porces serwera" #: ../postmaster/postmaster.c:1710 msgid "terminating any other active server processes" ! msgstr "przerywane s± wszystkie aktywne procesy serwera" #: ../postmaster/postmaster.c:1732 #, c-format msgid "CleanupProc: sending %s to process %d" ! msgstr "CleanupProc: wysy³am %s do procesu %d" #: ../postmaster/postmaster.c:1777 #, c-format msgid "%s (pid %d) exited with exit code %d" ! msgstr "%s (pid %d) zakoñczy³ siê z kodem wyj¶cia %d" #: ../postmaster/postmaster.c:1780 #, c-format msgid "%s (pid %d) was terminated by signal %d" ! msgstr "%s (pid %d) zosta³ przerwany przez sygna³ %d" #: ../postmaster/postmaster.c:1783 #, c-format msgid "%s (pid %d) exited with unexpected status %d" ! msgstr "%s (pid %d) zakoñczy³ siê z nieoczekiwanym statusem %d" #: ../postmaster/postmaster.c:1807 #, c-format msgid "SignalChildren: sending signal %d to process %d" ! msgstr "SignalChildren: wysy³am sygna³ %s do procesu %d" #: ../postmaster/postmaster.c:1842 msgid "out of memory; connection startup aborted" ! msgstr "brak pamiêci; otworzenie po³±czenia zosta³o przerwane" #: ../postmaster/postmaster.c:1877 msgid "connection startup failed" ! msgstr "otworzenia po³±czenia nie powiod³o siê" #: ../postmaster/postmaster.c:1894 #, c-format msgid "connection startup failed (fork failure): %s" ! msgstr "otworzenia po³±czenia nie powiod³o siê (b³±d funkcji fork): %s" #: ../postmaster/postmaster.c:1902 *************** *** 458,462 **** #, c-format msgid "connection: host=%s user=%s database=%s" ! msgstr "" #: ../postmaster/postmaster.c:2444 --- 458,462 ---- #, c-format msgid "connection: host=%s user=%s database=%s" ! msgstr "po³±czenie: host=%s u¿ytkownik=%s baza=%s" #: ../postmaster/postmaster.c:2444 |
|
From: <ma...@us...> - 2002-05-24 17:34:51
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv896/nls/nls Modified Files: postgres.po Log Message: Kilka komunikatów. Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.12 retrieving revision 1.13 diff -C2 -d -r1.12 -r1.13 *** postgres.po 19 May 2002 17:20:55 -0000 1.12 --- postgres.po 24 May 2002 17:34:43 -0000 1.13 *************** *** 11431,11435 **** #, c-format msgid "\"%s\" is not a valid operator name" ! msgstr "" #: ../catalog/pg_operator.c:312 --- 11431,11435 ---- #, c-format msgid "\"%s\" is not a valid operator name" ! msgstr "\"%s\" jest niepoprawn± nazw± operatora" #: ../catalog/pg_operator.c:312 *************** *** 11468,11472 **** #, c-format msgid "OperatorDef: operator %u not found" ! msgstr "" #: ../catalog/pg_operator.c:1057 --- 11468,11472 ---- #, c-format msgid "OperatorDef: operator %u not found" ! msgstr "OperatorDef: operator %u nie zosta³ znaleziony" #: ../catalog/pg_operator.c:1057 *************** *** 11493,11502 **** #, c-format msgid "CatalogIndexInsert: index %u not found" ! msgstr "" #: ../catalog/pg_type.c:307 ../catalog/pg_type.c:538 #, c-format msgid "type named %s already exists" ! msgstr "" #: ../catalog/pg_type.c:317 ../catalog/pg_type.c:533 --- 11493,11502 ---- #, c-format msgid "CatalogIndexInsert: index %u not found" ! msgstr "CatalogIndexInsert: indeks %u nie zosta³ znaleziony" #: ../catalog/pg_type.c:307 ../catalog/pg_type.c:538 #, c-format msgid "type named %s already exists" ! msgstr "typ nazwany %s ju¿ istnieje" #: ../catalog/pg_type.c:317 ../catalog/pg_type.c:533 *************** *** 11522,11526 **** #, c-format msgid "type %s already exists" ! msgstr "" #: ../catalog/pg_aggregate.c:75 --- 11522,11526 ---- #, c-format msgid "type %s already exists" ! msgstr "typ %s ju¿ istnieje" #: ../catalog/pg_aggregate.c:75 *************** *** 11535,11539 **** #, fuzzy, c-format msgid "data type %s does not exist" ! msgstr "Relacja \"%s\" nie istnieje" #: ../catalog/pg_aggregate.c:102 --- 11535,11539 ---- #, fuzzy, c-format msgid "data type %s does not exist" ! msgstr "typ danych \"%s\" nie istnieje" #: ../catalog/pg_aggregate.c:102 *************** *** 11545,11549 **** #, fuzzy, c-format msgid "data type %s does not exit" ! msgstr "Relacja \"%s\" nie istnieje" #: ../catalog/pg_aggregate.c:133 --- 11545,11549 ---- #, fuzzy, c-format msgid "data type %s does not exit" ! msgstr "typ danych \"%s\" nie istnieje" #: ../catalog/pg_aggregate.c:133 *************** *** 11581,11590 **** #, c-format msgid "acl size = %d, # acls = %d" ! msgstr "" #: ../catalog/aclchk.c:60 #, c-format msgid "\tacl[%d]: %s" ! msgstr "" #: ../catalog/aclchk.c:107 --- 11581,11590 ---- #, c-format msgid "acl size = %d, # acls = %d" ! msgstr "rozmiar acl = %d, # acls = %d" #: ../catalog/aclchk.c:60 #, c-format msgid "\tacl[%d]: %s" ! msgstr "\tacl[%d]: %s" #: ../catalog/aclchk.c:107 *************** *** 11596,11610 **** #, c-format msgid "\"%s\" is an index" ! msgstr "" #: ../catalog/aclchk.c:209 #, c-format msgid "non-existent group \"%s\"" ! msgstr "" #: ../catalog/aclchk.c:279 #, c-format msgid "in_group: group %u not found" ! msgstr "" #: ../catalog/aclchk.c:306 --- 11596,11610 ---- #, c-format msgid "\"%s\" is an index" ! msgstr "\"%s\" jest indeksem" #: ../catalog/aclchk.c:209 #, c-format msgid "non-existent group \"%s\"" ! msgstr "nieistniej±ca grupa \"%s\"" #: ../catalog/aclchk.c:279 #, c-format msgid "in_group: group %u not found" ! msgstr "in_group: grupa %u nie zosta³a znaleziona" #: ../catalog/aclchk.c:306 *************** *** 11628,11637 **** #, c-format msgid "aclcheck: found user %u/%d" ! msgstr "" #: ../catalog/aclchk.c:367 ../catalog/aclchk.c:388 #, c-format msgid "aclcheck: found group %u/%d" ! msgstr "" #: ../catalog/aclchk.c:400 --- 11628,11637 ---- #, c-format msgid "aclcheck: found user %u/%d" ! msgstr "aclcheck: znaleziono u¿ytkownika %u/%d" #: ../catalog/aclchk.c:367 ../catalog/aclchk.c:388 #, c-format msgid "aclcheck: found group %u/%d" ! msgstr "aclcheck: znaleziono funkcjê %u/%d" #: ../catalog/aclchk.c:400 *************** *** 11643,11647 **** #, c-format msgid "pg_aclcheck: invalid user id %u" ! msgstr "" #: ../catalog/aclchk.c:446 --- 11643,11647 ---- #, c-format msgid "pg_aclcheck: invalid user id %u" ! msgstr "pg_aclcheck: niew³a¶ciwe id u¿ytkownika %u" #: ../catalog/aclchk.c:446 *************** *** 11774,11778 **** #, c-format msgid "ProcedureCreate: you do not have permission to replace function %s" ! msgstr "" #: ../catalog/pg_proc.c:320 --- 11774,11778 ---- #, c-format msgid "ProcedureCreate: you do not have permission to replace function %s" ! msgstr ""ProcedureCreate: nie masz uprawnieñ do zamiany funkcji %s" #: ../catalog/pg_proc.c:320 *************** *** 11781,11784 **** --- 11781,11787 ---- "\tUse DROP FUNCTION first." msgstr "" + "ProcedureCreate: nie mo¿na zmieniaæ typu wyniku zwracanego przez\n" + "istniej±c± funkcjê.\n" + "\tNajpierw u¿yj DROP FUNCTION." #: ../catalog/pg_proc.c:381 |
|
From: <ma...@us...> - 2002-05-19 17:21:01
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv3851 Modified Files: postgres.po Log Message: Kolejne przetlumaczone komunikaty Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.11 retrieving revision 1.12 diff -C2 -d -r1.11 -r1.12 *** postgres.po 18 May 2002 11:58:19 -0000 1.11 --- postgres.po 19 May 2002 17:20:55 -0000 1.12 *************** *** 164,226 **** "\n" msgstr "" #: ../postmaster/postmaster.c:831 msgid "Options:\n" ! msgstr "" #: ../postmaster/postmaster.c:833 msgid " -A 1|0 enable/disable run-time assert checking\n" ! msgstr "" #: ../postmaster/postmaster.c:835 #, c-format msgid " -B NBUFFERS number of shared buffers (default %d)\n" ! msgstr "" #: ../postmaster/postmaster.c:836 msgid " -c NAME=VALUE set run-time parameter\n" ! msgstr "" #: ../postmaster/postmaster.c:837 msgid " -d 1-5 debugging level\n" ! msgstr "" #: ../postmaster/postmaster.c:838 msgid " -D DATADIR database directory\n" ! msgstr "" #: ../postmaster/postmaster.c:839 msgid " -F turn fsync off\n" ! msgstr "" #: ../postmaster/postmaster.c:840 msgid " -h HOSTNAME host name or IP address to listen on\n" ! msgstr "" #: ../postmaster/postmaster.c:841 msgid " -i enable TCP/IP connections\n" ! msgstr "" #: ../postmaster/postmaster.c:842 msgid " -k DIRECTORY Unix-domain socket location\n" ! msgstr "" #: ../postmaster/postmaster.c:844 msgid " -l enable SSL connections\n" ! msgstr "" #: ../postmaster/postmaster.c:846 #, c-format msgid " -N MAX-CONNECT maximum number of allowed connections (default %d)\n" ! msgstr "" #: ../postmaster/postmaster.c:848 msgid " -o OPTIONS pass 'OPTIONS' to each backend server\n" ! msgstr "" #: ../postmaster/postmaster.c:849 #, c-format msgid " -p PORT port number to listen on (default %d)\n" ! msgstr "" #: ../postmaster/postmaster.c:850 --- 164,229 ---- "\n" msgstr "" + "U¿ycie:\n" + " %s [opcje...]\n" + "\n" #: ../postmaster/postmaster.c:831 msgid "Options:\n" ! msgstr "Opcje: \n" #: ../postmaster/postmaster.c:833 msgid " -A 1|0 enable/disable run-time assert checking\n" ! msgstr " -A 1|0 w³±cza/wy³±cza sprawdzanie asercji w czasie wykonania\n" #: ../postmaster/postmaster.c:835 #, c-format msgid " -B NBUFFERS number of shared buffers (default %d)\n" ! msgstr " -B NBUFFERS liczba buforów dzielonych (domy¶lnie %d)\n" #: ../postmaster/postmaster.c:836 msgid " -c NAME=VALUE set run-time parameter\n" ! msgstr " -c NAZWA=WARTO¦Æ ustawia parametr wykonania\n" #: ../postmaster/postmaster.c:837 msgid " -d 1-5 debugging level\n" ! msgstr " -d 1-5 poziom debugowania\n" #: ../postmaster/postmaster.c:838 msgid " -D DATADIR database directory\n" ! msgstr " -D KATALOG katalog bazy danych\n" #: ../postmaster/postmaster.c:839 msgid " -F turn fsync off\n" ! msgstr " -F wy³±cz opcjê fsync\n" #: ../postmaster/postmaster.c:840 msgid " -h HOSTNAME host name or IP address to listen on\n" ! msgstr " -h HOSTNAME nazwa lub adres IP serwera do nas³uchu\n" #: ../postmaster/postmaster.c:841 msgid " -i enable TCP/IP connections\n" ! msgstr " -i umo¿liwia po³±czenia TCP/IP\n" #: ../postmaster/postmaster.c:842 msgid " -k DIRECTORY Unix-domain socket location\n" ! msgstr " -k KATALOG lokalizacja gniazda Unix-domain\n" #: ../postmaster/postmaster.c:844 msgid " -l enable SSL connections\n" ! msgstr " -l w³±cza po³±czenia SSL\n" #: ../postmaster/postmaster.c:846 #, c-format msgid " -N MAX-CONNECT maximum number of allowed connections (default %d)\n" ! msgstr " -N MAX-PO£¡CZEÑ maksymalna liczba dozwolonych po³±czeñ (domy¶lnie %d)\n" #: ../postmaster/postmaster.c:848 msgid " -o OPTIONS pass 'OPTIONS' to each backend server\n" ! msgstr " -o OPCJE przeka¿ 'OPCJE' do ka¿dego serwera\n" #: ../postmaster/postmaster.c:849 #, c-format msgid " -p PORT port number to listen on (default %d)\n" ! msgstr " -p PORT numer portu do nas³uchu (domy¶lnie %d)\n" #: ../postmaster/postmaster.c:850 *************** *** 228,231 **** --- 231,235 ---- " -S silent mode (start in background without logging output)\n" msgstr "" + " -S tyb cichy (startuje w tle bez logowania wyniku)\n" #: ../postmaster/postmaster.c:852 *************** *** 234,237 **** --- 238,243 ---- "Developer options:\n" msgstr "" + "\n" + "Opcje developerskie\n" #: ../postmaster/postmaster.c:853 |
|
From: <ma...@us...> - 2002-05-18 11:58:24
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv463 Modified Files: postgres.po Log Message: kolejne przet³umaczone komunikaty Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.10 retrieving revision 1.11 diff -C2 -d -r1.10 -r1.11 *** postgres.po 16 May 2002 19:38:07 -0000 1.10 --- postgres.po 18 May 2002 11:58:19 -0000 1.11 *************** *** 101,115 **** #: ../postmaster/postmaster.c:469 msgid "Assert checking is not compiled in." ! msgstr "" #: ../postmaster/postmaster.c:571 ../tcop/postgres.c:1508 #, c-format msgid "--%s requires argument" ! msgstr "" #: ../postmaster/postmaster.c:573 ../tcop/postgres.c:1510 #, c-format msgid "-c %s requires argument" ! msgstr "" #: ../postmaster/postmaster.c:600 --- 101,115 ---- #: ../postmaster/postmaster.c:469 msgid "Assert checking is not compiled in." ! msgstr "Sprawdzanie asercji nie jest wkompilowane." #: ../postmaster/postmaster.c:571 ../tcop/postgres.c:1508 #, c-format msgid "--%s requires argument" ! msgstr "--%s wymaga argumentu" #: ../postmaster/postmaster.c:573 ../tcop/postgres.c:1510 #, c-format msgid "-c %s requires argument" ! msgstr "-c %s wymaga argumentu" #: ../postmaster/postmaster.c:600 *************** *** 118,148 **** "connections (-N) and at least 16." msgstr "" #: ../postmaster/postmaster.c:631 ../tcop/postgres.c:1641 #, c-format msgid "%s: could not locate executable, bailing out..." ! msgstr "" #: ../postmaster/postmaster.c:640 msgid "For SSL, TCP/IP connections must be enabled." ! msgstr "" #: ../postmaster/postmaster.c:687 msgid "cannot create INET stream port" ! msgstr "" #: ../postmaster/postmaster.c:699 msgid "cannot create UNIX stream port" ! msgstr "" #: ../postmaster/postmaster.c:791 #, c-format msgid "fork failed: %s" ! msgstr "" #: ../postmaster/postmaster.c:809 #, c-format msgid "cannot disassociate from controlling TTY: %s" ! msgstr "" #: ../postmaster/postmaster.c:829 --- 118,150 ---- "connections (-N) and at least 16." msgstr "" + "Liczba buforów (-B) musi byæ przynajmniej dwukrotnie wiêksza ni¿ liczba " + "dozwolonych po³±czeñ (-N) oraz wiêksza od 16." #: ../postmaster/postmaster.c:631 ../tcop/postgres.c:1641 #, c-format msgid "%s: could not locate executable, bailing out..." ! msgstr "%s: nie mo¿na zlokalizowaæ plików wykonywalnych, brrr ..." #: ../postmaster/postmaster.c:640 msgid "For SSL, TCP/IP connections must be enabled." ! msgstr "Dla po³±czeñ SSL musz± byæ w³±czone po³±czenia TCP/IP." #: ../postmaster/postmaster.c:687 msgid "cannot create INET stream port" ! msgstr "nie mo¿na utworzyæ portu strumienia INET" #: ../postmaster/postmaster.c:699 msgid "cannot create UNIX stream port" ! msgstr "nie mo¿na utworzyæ portu strumienia UNIX" #: ../postmaster/postmaster.c:791 #, c-format msgid "fork failed: %s" ! msgstr "fork nie powiód³ siê: %s" #: ../postmaster/postmaster.c:809 #, c-format msgid "cannot disassociate from controlling TTY: %s" ! msgstr "nie mo¿na od³±czyæ siê od terminala kontroluj±cego: %s" #: ../postmaster/postmaster.c:829 *************** *** 152,155 **** --- 154,159 ---- "\n" msgstr "" + "%s jest serwerem PostgreSQL.\n" + "\n" #: ../postmaster/postmaster.c:830 |
|
From: <ma...@us...> - 2002-05-16 19:38:16
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv30023 Modified Files: postgres.po Log Message: kolejne komunikaty i poprawki Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.9 retrieving revision 1.10 diff -C2 -d -r1.9 -r1.10 *** postgres.po 16 May 2002 13:18:17 -0000 1.9 --- postgres.po 16 May 2002 19:38:07 -0000 1.10 *************** *** 64,68 **** #, c-format msgid "could not read permissions of directory %s: %m" ! msgstr "" #: ../postmaster/postmaster.c:318 --- 64,68 ---- #, c-format msgid "could not read permissions of directory %s: %m" ! msgstr "nie mo¿na odczytaæ uprawnieñ katalogu %s: %m" #: ../postmaster/postmaster.c:318 *************** *** 72,75 **** --- 72,77 ---- "(0700)" msgstr "" + "katalog danych %s jest dostêpny dla grupy lub innych; oczekiwane uprawnienia u=rwx " + "(0700)" #: ../postmaster/postmaster.c:332 *************** *** 81,84 **** --- 83,90 ---- "\n" msgstr "" + "%s nie mo¿e odnale¼æ katalogu bazy danych.\n" + "Oczekiwano go w katalogu PGDATA \"%s\",\n" + "ale nie mo¿na otworzyæ pliku \"%s\": %s\n" + "\n" #: ../postmaster/postmaster.c:432 ../postmaster/postmaster.c:443 *************** *** 86,95 **** #, c-format msgid "Try '%s --help' for more information.\n" ! msgstr "" #: ../postmaster/postmaster.c:442 #, c-format msgid "invalid argument -- %s" ! msgstr "" #: ../postmaster/postmaster.c:469 --- 92,101 ---- #, c-format msgid "Try '%s --help' for more information.\n" ! msgstr "Wpisz '%s --help', aby uzyskaæ wiêcej informacji.\n" #: ../postmaster/postmaster.c:442 #, c-format msgid "invalid argument -- %s" ! msgstr "nieprawid³owy argument -- %s" #: ../postmaster/postmaster.c:469 *************** *** 12130,12136 **** "statistics are on." msgstr "" ! "Statystyki zapytañ s± wy³±czone poniewa¿ w³±czone s± statystyki parsera, ! planera lub executora. ! " #: ../tcop/postgres.c:1611 ../tcop/postgres.c:1623 --- 12136,12141 ---- "statistics are on." msgstr "" ! "Statystyki zapytañ s± wy³±czone poniewa¿ w³±czone s± statystyki parsera," ! "planera lub executora." #: ../tcop/postgres.c:1611 ../tcop/postgres.c:1623 *************** *** 12196,12200 **** msgid "" "HandleFunctionRequest: actual arguments (%d) != registered arguments (%d)" ! msgstr "HandleFunctionRequest: bie¿±ce argumenty (%d) != zarejestrowane argumenty (%d)"" #: ../tcop/fastpath.c:291 ../tcop/fastpath.c:303 --- 12201,12206 ---- msgid "" "HandleFunctionRequest: actual arguments (%d) != registered arguments (%d)" ! msgstr "" ! "HandleFunctionRequest: bie¿±ce argumenty (%d) != zarejestrowane argumenty (%d)" #: ../tcop/fastpath.c:291 ../tcop/fastpath.c:303 |
|
From: <ma...@us...> - 2002-05-16 13:18:20
|
Update of /cvsroot/polishpgdoc/nls/nls
In directory usw-pr-cvs1:/tmp/cvs-serv19459
Modified Files:
postgres.po
Log Message:
Kilka przet³umaczoncyh msgstr
Index: postgres.po
===================================================================
RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** postgres.po 16 May 2002 12:34:14 -0000 1.8
--- postgres.po 16 May 2002 13:18:17 -0000 1.9
***************
*** 11805,11814 ****
#, c-format
msgid "LargeObjectDrop: large object %u not found"
! msgstr ""
#: ../catalog/index.c:117
#, c-format
msgid "index named \"%s\" already exists"
! msgstr ""
#: ../catalog/index.c:123
--- 11805,11814 ----
#, c-format
msgid "LargeObjectDrop: large object %u not found"
! msgstr "LargeObjectDrop: du¿y obiekt %u nie zosta³ znaleziony"
#: ../catalog/index.c:117
#, c-format
msgid "index named \"%s\" already exists"
! msgstr "indeks o nazwie \"%s\" ju¿ istnieje"
#: ../catalog/index.c:123
***************
*** 11820,11824 ****
#, c-format
msgid "Function %u does not exist"
! msgstr ""
#: ../catalog/index.c:172 ../catalog/index.c:306
--- 11820,11824 ----
#, c-format
msgid "Function %u does not exist"
! msgstr "Funkcja %u nie istnieje"
#: ../catalog/index.c:172 ../catalog/index.c:306
***************
*** 11830,11834 ****
#, c-format
msgid "Type %u does not exist"
! msgstr ""
#: ../catalog/index.c:266
--- 11830,11834 ----
#, c-format
msgid "Type %u does not exist"
! msgstr "Typ %u nie istnieje"
#: ../catalog/index.c:266
***************
*** 11853,11862 ****
#, c-format
msgid "index_drop: FlushRelationBuffers returned %d"
! msgstr ""
#: ../catalog/index.c:1142
#, c-format
msgid "LockClassinfoForUpdate couldn't lock relid %u"
! msgstr ""
#: ../catalog/index.c:1153
--- 11853,11862 ----
#, c-format
msgid "index_drop: FlushRelationBuffers returned %d"
! msgstr "index_drop: FlushRelationBuffers zwróci³o %d"
#: ../catalog/index.c:1142
#, c-format
msgid "LockClassinfoForUpdate couldn't lock relid %u"
! msgstr "LockClassinfoForUpdate nie zablokowa³o relid %u"
#: ../catalog/index.c:1153
***************
*** 11866,11870 ****
#: ../catalog/index.c:1156
msgid "The tuple is already deleted"
! msgstr ""
#: ../catalog/index.c:1177
--- 11866,11870 ----
#: ../catalog/index.c:1156
msgid "The tuple is already deleted"
! msgstr "Krotka zosta³a ju¿ usuniêta"
#: ../catalog/index.c:1177
***************
*** 11907,11911 ****
#: ../catalog/index.c:1883
msgid "REINDEX cannot run inside a transaction block"
! msgstr ""
#: ../catalog/index.c:1897
--- 11907,11911 ----
#: ../catalog/index.c:1883
msgid "REINDEX cannot run inside a transaction block"
! msgstr "REINDEX nie mo¿e byæ uruchamiany w bloku transkacji"
#: ../catalog/index.c:1897
***************
*** 11935,11954 ****
#, c-format
msgid "\"%s\" is not %s %s. Use DROP %s to remove %s %s"
! msgstr ""
#: ../tcop/utility.c:92
#, c-format
msgid "\"%s\" is not %s %s"
! msgstr ""
#: ../tcop/utility.c:112
#, c-format
msgid "%s \"%s\" does not exist"
! msgstr ""
#: ../tcop/utility.c:120
#, c-format
msgid "you do not own %s \"%s\""
! msgstr ""
#: ../tcop/utility.c:125
--- 11935,11954 ----
#, c-format
msgid "\"%s\" is not %s %s. Use DROP %s to remove %s %s"
! msgstr "\"%s\" nie jest %s %s. U¿yj DROP %s aby usun±æ %s %s"
#: ../tcop/utility.c:92
#, c-format
msgid "\"%s\" is not %s %s"
! msgstr "\"%s\" nie jest %s %s"
#: ../tcop/utility.c:112
#, c-format
msgid "%s \"%s\" does not exist"
! msgstr "%s \"%s\" nie istnieje"
#: ../tcop/utility.c:120
#, c-format
msgid "you do not own %s \"%s\""
! msgstr "nie jeste¶ w³a¶cicielem %s \"%s\""
#: ../tcop/utility.c:125
***************
*** 11960,11979 ****
#, c-format
msgid "TRUNCATE cannot be used on system tables. '%s' is a system table"
! msgstr ""
#: ../tcop/utility.c:309
#, c-format
msgid "TRUNCATE cannot be used on sequences. '%s' is a sequence"
! msgstr ""
#: ../tcop/utility.c:312
#, c-format
msgid "TRUNCATE cannot be used on views. '%s' is a view"
! msgstr ""
#: ../tcop/utility.c:317
#, c-format
msgid "you do not own class \"%s\""
! msgstr ""
#: ../tcop/utility.c:459
--- 11960,11979 ----
#, c-format
msgid "TRUNCATE cannot be used on system tables. '%s' is a system table"
! msgstr "TRUNCATE nie mo¿e byæ u¿ywane na tabelach systemowych. '%s' jest tabel± systemow±"
#: ../tcop/utility.c:309
#, c-format
msgid "TRUNCATE cannot be used on sequences. '%s' is a sequence"
! msgstr "TRUNCATE nie mo¿e byæ u¿ywane na sekwencjach. '%s' jest sekwencj±"
#: ../tcop/utility.c:312
#, c-format
msgid "TRUNCATE cannot be used on views. '%s' is a view"
! msgstr "TRUNCATE nie mo¿e byæ u¿ywane na widokach. '%s' jest widokiem"
#: ../tcop/utility.c:317
#, c-format
msgid "you do not own class \"%s\""
! msgstr "nie jeste¶ w³a¶cicielem klasy \"%s\""
#: ../tcop/utility.c:459
***************
*** 11988,11992 ****
#: ../tcop/utility.c:590
msgid "CREATE VERSION is not currently implemented"
! msgstr ""
#: ../tcop/utility.c:654
--- 11988,11992 ----
#: ../tcop/utility.c:590
msgid "CREATE VERSION is not currently implemented"
! msgstr "CREATE VERSION jest obecnie nie zaimplementowane"
#: ../tcop/utility.c:654
***************
*** 12011,12019 ****
#: ../tcop/utility.c:812
msgid "must be called under standalone postgres with -O -P options"
! msgstr ""
#: ../tcop/utility.c:814
msgid "must be called under standalone postgres with -P -O options"
! msgstr ""
#: ../tcop/utility.c:827
--- 12011,12019 ----
#: ../tcop/utility.c:812
msgid "must be called under standalone postgres with -O -P options"
! msgstr "musi byæ wywo³ane z uruchomionym postgres'em z opcjami -P -O"
#: ../tcop/utility.c:814
msgid "must be called under standalone postgres with -P -O options"
! msgstr "musi byæ wywo³ane z uruchomionym postgres'em z opcjami -P -O"
#: ../tcop/utility.c:827
***************
*** 12030,12043 ****
#, c-format
msgid "query: %s"
! msgstr ""
#: ../tcop/postgres.c:432
msgid "parse tree:"
! msgstr ""
#: ../tcop/postgres.c:436
#, c-format
msgid "parse tree: %s"
! msgstr ""
#: ../tcop/postgres.c:467
--- 12030,12043 ----
#, c-format
msgid "query: %s"
! msgstr "zapytanie: %s"
#: ../tcop/postgres.c:432
msgid "parse tree:"
! msgstr "drzewo parsowania:"
#: ../tcop/postgres.c:436
#, c-format
msgid "parse tree: %s"
! msgstr "drzewo parsowania: %s"
#: ../tcop/postgres.c:467
***************
*** 12047,12051 ****
#: ../tcop/postgres.c:476 ../tcop/postgres.c:486
msgid "rewritten parse tree:"
! msgstr ""
#: ../tcop/postgres.c:530
--- 12047,12051 ----
#: ../tcop/postgres.c:476 ../tcop/postgres.c:486
msgid "rewritten parse tree:"
! msgstr "przepisane drzewo parsowania:"
#: ../tcop/postgres.c:530
***************
*** 12055,12064 ****
#: ../tcop/postgres.c:544
msgid "plan:"
! msgstr ""
#: ../tcop/postgres.c:548
#, c-format
msgid "plan: %s"
! msgstr ""
#: ../tcop/postgres.c:686 ../tcop/fastpath.c:334
--- 12055,12064 ----
#: ../tcop/postgres.c:544
msgid "plan:"
! msgstr "plan:"
#: ../tcop/postgres.c:548
#, c-format
msgid "plan: %s"
! msgstr "plan: %s"
#: ../tcop/postgres.c:686 ../tcop/fastpath.c:334
***************
*** 12107,12115 ****
#: ../tcop/postgres.c:1106
msgid "This connection has been terminated by the administrator."
! msgstr ""
#: ../tcop/postgres.c:1112
msgid "Query was cancelled."
! msgstr ""
#: ../tcop/postgres.c:1253
--- 12107,12115 ----
#: ../tcop/postgres.c:1106
msgid "This connection has been terminated by the administrator."
! msgstr "To po³±czenie zosta³o przerwane przeaz adinistratora"
#: ../tcop/postgres.c:1112
msgid "Query was cancelled."
! msgstr "Zapytanie zosta³o anulowane"
#: ../tcop/postgres.c:1253
***************
*** 12119,12127 ****
#: ../tcop/postgres.c:1474
msgid "only one -x flag is allowed"
! msgstr ""
#: ../tcop/postgres.c:1492
msgid "use -x {off,nor,nopull,nopm,pullall,wait}"
! msgstr ""
#: ../tcop/postgres.c:1531
--- 12119,12127 ----
#: ../tcop/postgres.c:1474
msgid "only one -x flag is allowed"
! msgstr "jedynie opcja -x jest dozwolona"
#: ../tcop/postgres.c:1492
msgid "use -x {off,nor,nopull,nopm,pullall,wait}"
! msgstr "u¿yj -x {off,nor,nopull,nopm,pullall,wait}"
#: ../tcop/postgres.c:1531
***************
*** 12130,12133 ****
--- 12130,12136 ----
"statistics are on."
msgstr ""
+ "Statystyki zapytañ s± wy³±czone poniewa¿ w³±czone s± statystyki parsera,
+ planera lub executora.
+ "
#: ../tcop/postgres.c:1611 ../tcop/postgres.c:1623
***************
*** 12137,12153 ****
"Try -? for help."
msgstr ""
#: ../tcop/postgres.c:1631
#, c-format
msgid "%s: user name undefined and no database specified\n"
! msgstr ""
#: ../tcop/postgres.c:1683
msgid "InitPostgres"
! msgstr ""
#: ../tcop/postgres.c:1766
msgid "AbortCurrentTransaction"
! msgstr ""
#: ../tcop/postgres.c:1954
--- 12140,12158 ----
"Try -? for help."
msgstr ""
+ "%s: niepoprawne parametry w linii poleceñ\n"
+ "Spróbuj -? aby uzyskaæ pomoc."
#: ../tcop/postgres.c:1631
#, c-format
msgid "%s: user name undefined and no database specified\n"
! msgstr "%s: nazwa u¿ytkownika nie zosta³a okre¶lona ani baza danych\n"
#: ../tcop/postgres.c:1683
msgid "InitPostgres"
! msgstr "InicjujPostgres"
#: ../tcop/postgres.c:1766
msgid "AbortCurrentTransaction"
! msgstr "PrzerwijBie¿±c±Transakcjê"
#: ../tcop/postgres.c:1954
***************
*** 12185,12189 ****
#, c-format
msgid "fetch_fp_info: cache lookup for function %u failed"
! msgstr ""
#: ../tcop/fastpath.c:272
--- 12190,12194 ----
#, c-format
msgid "fetch_fp_info: cache lookup for function %u failed"
! msgstr "fetch_fp_info: poszukiwanie funkcji %u w cache nie powiod³o siê"
#: ../tcop/fastpath.c:272
***************
*** 12191,12203 ****
msgid ""
"HandleFunctionRequest: actual arguments (%d) != registered arguments (%d)"
! msgstr ""
#: ../tcop/fastpath.c:291 ../tcop/fastpath.c:303
#, c-format
msgid "HandleFunctionRequest: bogus argsize %d"
! msgstr ""
#: ../tcop/fastpath.c:316
#, c-format
msgid "HandleFunctionRequest: bogus argsize %d, should be %d"
! msgstr ""
--- 12196,12208 ----
msgid ""
"HandleFunctionRequest: actual arguments (%d) != registered arguments (%d)"
! msgstr "HandleFunctionRequest: bie¿±ce argumenty (%d) != zarejestrowane argumenty (%d)""
#: ../tcop/fastpath.c:291 ../tcop/fastpath.c:303
#, c-format
msgid "HandleFunctionRequest: bogus argsize %d"
! msgstr "HandleFunctionRequest: dziwny rozmiar argumentu %d"
#: ../tcop/fastpath.c:316
#, c-format
msgid "HandleFunctionRequest: bogus argsize %d, should be %d"
! msgstr "HandleFunctionRequest: dziwny rozmiar argumentu %d, powinno byæ %d"
|
|
From: <ma...@us...> - 2002-05-16 12:34:23
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv4399 Modified Files: postgres.po Log Message: Kilka przet³umaczonych komunikatow. Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** postgres.po 15 May 2002 18:11:44 -0000 1.7 --- postgres.po 16 May 2002 12:34:14 -0000 1.8 *************** *** 11637,11710 **** #, c-format msgid "pg_aclcheck: \"%s\" is superuser" ! msgstr "" #: ../catalog/aclchk.c:476 #, c-format msgid "pg_aclcheck: class \"%s\" not found" ! msgstr "" #: ../catalog/aclchk.c:526 #, c-format msgid "pg_ownercheck: invalid user id %u" ! msgstr "" #: ../catalog/aclchk.c:536 ../catalog/aclchk.c:598 ../catalog/aclchk.c:649 #, c-format msgid "pg_ownercheck: user \"%s\" is superuser" ! msgstr "" #: ../catalog/aclchk.c:553 #, c-format msgid "pg_ownercheck: class \"%s\" not found" ! msgstr "" #: ../catalog/aclchk.c:559 #, c-format msgid "pg_ownercheck: type \"%s\" not found" ! msgstr "" #: ../catalog/aclchk.c:564 #, c-format msgid "pg_ownercheck: invalid cache id: %d" ! msgstr "" #: ../catalog/aclchk.c:588 #, c-format msgid "pg_oper_ownercheck: invalid user id %u" ! msgstr "" #: ../catalog/aclchk.c:612 #, c-format msgid "pg_ownercheck: operator %u not found" ! msgstr "" #: ../catalog/aclchk.c:639 #, c-format msgid "pg_func_ownercheck: invalid user id %u" ! msgstr "" #: ../catalog/aclchk.c:691 #, c-format msgid "pg_aggr_ownercheck: invalid user id %u" ! msgstr "" #: ../catalog/aclchk.c:701 #, c-format msgid "pg_aggr_ownercheck: user \"%s\" is superuser" ! msgstr "" #: ../catalog/pg_proc.c:89 #, fuzzy, c-format msgid "language '%s' does not exist" ! msgstr "Relacja \"%s\" nie istnieje" #: ../catalog/pg_proc.c:105 msgid "SQL functions cannot have arguments of type \"opaque\"" ! msgstr "" #: ../catalog/pg_proc.c:113 #, fuzzy, c-format msgid "argument type %s does not exist" ! msgstr "Relacja \"%s\" nie istnieje" #: ../catalog/pg_proc.c:116 --- 11637,11710 ---- #, c-format msgid "pg_aclcheck: \"%s\" is superuser" ! msgstr "pg_aclcheck: \"%s\" jest superu¿ytkownikiem" #: ../catalog/aclchk.c:476 #, c-format msgid "pg_aclcheck: class \"%s\" not found" ! msgstr "pg_aclcheck: klasa \"%s\" nie zosta³a znaleziona" #: ../catalog/aclchk.c:526 #, c-format msgid "pg_ownercheck: invalid user id %u" ! msgstr "pg_ownercheck: niew³a¶ciwe id u¿ytkownika %u" #: ../catalog/aclchk.c:536 ../catalog/aclchk.c:598 ../catalog/aclchk.c:649 #, c-format msgid "pg_ownercheck: user \"%s\" is superuser" ! msgstr "pg_ownercheck: u¿ytkownik \"%s\" jest superu¿ytkownikiem" #: ../catalog/aclchk.c:553 #, c-format msgid "pg_ownercheck: class \"%s\" not found" ! msgstr "pg_ownercheck: klasa \"%s\" nie zosta³a znaleziona" #: ../catalog/aclchk.c:559 #, c-format msgid "pg_ownercheck: type \"%s\" not found" ! msgstr "pg_ownercheck: typ \"%s\" niz zosta³ znaleziony" #: ../catalog/aclchk.c:564 #, c-format msgid "pg_ownercheck: invalid cache id: %d" ! msgstr "pg_ownercheck: niepoprawny id cache: %d" #: ../catalog/aclchk.c:588 #, c-format msgid "pg_oper_ownercheck: invalid user id %u" ! msgstr "pg_oper_ownercheck: niew³a¶ciwe id u¿ytkownika %u" #: ../catalog/aclchk.c:612 #, c-format msgid "pg_ownercheck: operator %u not found" ! msgstr "pg_ownercheck: operator %u nie zosta³ znaleziony" #: ../catalog/aclchk.c:639 #, c-format msgid "pg_func_ownercheck: invalid user id %u" ! msgstr "pg_func_ownercheck: niew³a¶ciwe id u¿ytkownika %u" #: ../catalog/aclchk.c:691 #, c-format msgid "pg_aggr_ownercheck: invalid user id %u" ! msgstr "pg_aggr_ownercheck: niew³a¶ciwe id u¿ytkownika %u" #: ../catalog/aclchk.c:701 #, c-format msgid "pg_aggr_ownercheck: user \"%s\" is superuser" ! msgstr "pg_aggr_ownercheck: u¿ytkownik \"%s\" jest superu¿ytkownikiem" #: ../catalog/pg_proc.c:89 #, fuzzy, c-format msgid "language '%s' does not exist" ! msgstr "jêzyk '%s' nie istnieje" #: ../catalog/pg_proc.c:105 msgid "SQL functions cannot have arguments of type \"opaque\"" ! msgstr "funkcje SQL nie mog± mieæ argumentów typu \"opaque\"" #: ../catalog/pg_proc.c:113 #, fuzzy, c-format msgid "argument type %s does not exist" ! msgstr "argument typu %s nie istnieje" #: ../catalog/pg_proc.c:116 *************** *** 11715,11719 **** #: ../catalog/pg_proc.c:121 msgid "functions cannot accept set arguments" ! msgstr "" #: ../catalog/pg_proc.c:159 --- 11715,11719 ---- #: ../catalog/pg_proc.c:121 msgid "functions cannot accept set arguments" ! msgstr "funkcje nie mog± przymowaæ argumentów typu \"set\"" #: ../catalog/pg_proc.c:159 *************** *** 11723,11737 **** #: ../catalog/pg_proc.c:167 msgid "SQL functions cannot return type \"opaque\"" ! msgstr "" #: ../catalog/pg_proc.c:176 #, c-format msgid "ProcedureCreate: type %s is not yet defined" ! msgstr "" #: ../catalog/pg_proc.c:180 #, c-format msgid "could not create type %s" ! msgstr "" #: ../catalog/pg_proc.c:184 --- 11723,11737 ---- #: ../catalog/pg_proc.c:167 msgid "SQL functions cannot return type \"opaque\"" ! msgstr "funkcje SQL nie mog± mieæ argumentów typu \"opaque\"" #: ../catalog/pg_proc.c:176 #, c-format msgid "ProcedureCreate: type %s is not yet defined" ! msgstr "ProcedureCreate: typ %s nie zosta³ jeszcze zdefiniowany" #: ../catalog/pg_proc.c:180 #, c-format msgid "could not create type %s" ! msgstr "nie mo¿na utworzyæ typu %s" #: ../catalog/pg_proc.c:184 *************** *** 11748,11757 **** #, c-format msgid "there is no built-in function named \"%s\"" ! msgstr "" #: ../catalog/pg_proc.c:308 #, c-format msgid "function %s already exists with same argument types" ! msgstr "" #: ../catalog/pg_proc.c:311 --- 11748,11757 ---- #, c-format msgid "there is no built-in function named \"%s\"" ! msgstr "nie istnieje predefiniowana funkcja o nazwie \"%s\"" #: ../catalog/pg_proc.c:308 #, c-format msgid "function %s already exists with same argument types" ! msgstr "funkcja %s ju¿ istnieje z argumentami takiego samego typu" #: ../catalog/pg_proc.c:311 |
|
From: <ma...@us...> - 2002-05-15 18:49:35
|
Update of /cvsroot/polishpgdoc/nls/nls
In directory usw-pr-cvs1:/tmp/cvs-serv26404
Modified Files:
pg_dump.po
Log Message:
alec skonczyl tlumaczenie, prosze o lookniecie
Index: pg_dump.po
===================================================================
RCS file: /cvsroot/polishpgdoc/nls/nls/pg_dump.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** pg_dump.po 7 May 2002 19:20:00 -0000 1.3
--- pg_dump.po 15 May 2002 18:49:32 -0000 1.4
***************
*** 80,87 ****
" -d, --inserts przenosi dane jako polecenia INSERT\n"
" -D, --column-inserts przenosi dane jako polecenia INSERT z nazwami "
! "kolumn\n"
" -f, --file=FILENAME nazwa pliku wyj¶ciowego\n"
! " -F, --format {c|t|p} format pliku wyj¶ciowego (custom, tar, plain "
! "text)\n"
" -h, --host=HOSTNAME nazwa serwera bazy danych\n"
" -i, --ignore-version ignoruje niezgodno¶æ wersji serwera z wersj±\n"
--- 80,86 ----
" -d, --inserts przenosi dane jako polecenia INSERT\n"
[...1647 lines suppressed...]
+ " wy³±czenia wyzwalaczy\n"
+ " -t NAZWA odtwarza podan± tabelê\n"
+ " -T NAZWA odtwarza podany wyzwalacz\n"
+ " -U NAZWA ³±czy z baz± jako podany u¿ytkownik\n"
+ " -v w³±cza tryb opisowy\n"
+ " -W rz±da has³a (powinno dzia³aæ automatycznie)\n"
+ " -x pomija odtwarzanie praw dostêpu (grant/revoke)\n"
+ " -X use-set-session-authorization\n"
+ " stosuje komendy SET SESSION AUTHORIZATION zamiast\n"
+ " wznawiania po³±czenia, je¶li jest to mo¿liwe\n"
#: pg_restore.c:457
msgid "If no input file name is supplied, then standard input is used.\n"
! msgstr "Je¿eli nie podano nazwy pliku, wtedy jest stosowane standardowe wej¶cie.\n"
#: pg_restore.c:458
msgid "Report bugs to <pgs...@po...>."
! msgstr "B³êdy prosimy zg³aszaæ do <pgs...@po...>."
#~ msgid ""
|
|
From: <ma...@us...> - 2002-05-15 18:11:49
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv13854 Modified Files: postgres.po Log Message: kolejna porcja przet³umaczonych komunikatów Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.6 retrieving revision 1.7 diff -C2 -d -r1.6 -r1.7 *** postgres.po 6 May 2002 16:29:37 -0000 1.6 --- postgres.po 15 May 2002 18:11:44 -0000 1.7 *************** *** 15,23 **** #: ../postmaster/pgstat.c:704 msgid "Only database superusers can reset statistic counters" ! msgstr "" #: ../postmaster/pgstat.c:2108 msgid "PGSTAT: Creation of DB hash table failed" ! msgstr "" #: ../postmaster/pgstat.c:2154 ../postmaster/pgstat.c:2191 --- 15,23 ---- #: ../postmaster/pgstat.c:704 msgid "Only database superusers can reset statistic counters" ! msgstr "Tylko superu¿ytkownik mo¿e wyzerowaæ liczniki statystyk" #: ../postmaster/pgstat.c:2108 msgid "PGSTAT: Creation of DB hash table failed" ! msgstr "PGSTAT: Utworzenie tabeli asocjacyjnej DB nie powiod³o siê" #: ../postmaster/pgstat.c:2154 ../postmaster/pgstat.c:2191 *************** *** 26,42 **** #: ../postmaster/pgstat.c:2433 msgid "PGSTAT: corrupted pgstat.stat file" ! msgstr "" #: ../postmaster/pgstat.c:2176 msgid "PGSTAT: DB hash table out of memory" ! msgstr "" #: ../postmaster/pgstat.c:2229 msgid "PGSTAT: failed to initialize hash table for new database entry\n" ! msgstr "" #: ../postmaster/pgstat.c:2289 msgid "PGSTAT: Tab hash table out of memory" ! msgstr "" #: ../postmaster/postmaster.c:291 ../bootstrap/bootstrap.c:297 --- 26,42 ---- #: ../postmaster/pgstat.c:2433 msgid "PGSTAT: corrupted pgstat.stat file" ! msgstr "PGSTAT: z³a struktura pliku pgstat.stat" #: ../postmaster/pgstat.c:2176 msgid "PGSTAT: DB hash table out of memory" ! msgstr "PGSTAT: brak pamiêci na tabelê asocjacyjn± DB" #: ../postmaster/pgstat.c:2229 msgid "PGSTAT: failed to initialize hash table for new database entry\n" ! msgstr "PGSTAT: inicjacja tabeli asocjacyjnej dla nowej bazy danych nie powiod³a siê\n" #: ../postmaster/pgstat.c:2289 msgid "PGSTAT: Tab hash table out of memory" ! msgstr "PGSTAT: brak pamiêci na tabelê asocjacyjn± Tab" #: ../postmaster/postmaster.c:291 ../bootstrap/bootstrap.c:297 *************** *** 49,57 **** "\n" msgstr "" #: ../postmaster/postmaster.c:311 #, c-format msgid "data directory %s was not found" ! msgstr "" #: ../postmaster/postmaster.c:313 --- 49,63 ---- "\n" msgstr "" + "%s nie wie, gdzie szukaæ danych systemowych bazy danych.\n" + "Musisz wskazaæ katalog zawieraj±cy bazê danych\n" + "albo poprzez u¿ycie opcji -D, albo poprzez\n" + "ustawienie zmiennej ¶rodowiskowej PGDATA.\n" + "\n" + #: ../postmaster/postmaster.c:311 #, c-format msgid "data directory %s was not found" ! msgstr "katalog danych %s nie zosta³ odnaleziony" #: ../postmaster/postmaster.c:313 *************** *** 7111,7115 **** #, c-format msgid "unexpected chunk number %d for toast value %u" ! msgstr "nieoczekiwana liczba elementów dla krotki toast %u" #: ../access/heap/tuptoaster.c:1070 --- 7117,7121 ---- #, c-format msgid "unexpected chunk number %d for toast value %u" ! msgstr "nieoczekiwana liczba elementów %d dla krotki toast %u" #: ../access/heap/tuptoaster.c:1070 |
|
From: <ma...@us...> - 2002-05-09 19:11:32
|
Update of /cvsroot/polishpgdoc/nls/nls
In directory usw-pr-cvs1:/tmp/cvs-serv25941
Modified Files:
INSTALL
Log Message:
poprawione literówki
Index: INSTALL
===================================================================
RCS file: /cvsroot/polishpgdoc/nls/nls/INSTALL,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** INSTALL 1 May 2002 08:04:24 -0000 1.1
--- INSTALL 9 May 2002 19:11:27 -0000 1.2
***************
*** 38,44 ****
Po pomy¶lnym zainstalowaniu narzêdzi gettext mo¿esz skonfigurowaæ
! PostgreSQL'a, pamiêtaj±c o w³±czeniu wspracia dla NLS:
! $ ./configure --prefix=/¶cie¿ka/doeclowa --enable-nls
Kolejn± rzecz± jest odpowiednie umiejscowienie plików *.po.
--- 38,44 ----
Po pomy¶lnym zainstalowaniu narzêdzi gettext mo¿esz skonfigurowaæ
! PostgreSQL'a, pamiêtaj±c o w³±czeniu wsparcia dla NLS:
! $ ./configure --prefix=/¶cie¿ka/docelowa --enable-nls
Kolejn± rzecz± jest odpowiednie umiejscowienie plików *.po.
***************
*** 58,62 ****
AVAIL_LANGUAGES := cs de hu ru zh_CN zh_TW
! jêzyk polski, czyli "pl". Poprawna linijka powinna wygldaæ tak:
AVAIL_LANGUAGES := cs de hu ru zh_CN zh_TW pl
--- 58,62 ----
AVAIL_LANGUAGES := cs de hu ru zh_CN zh_TW
! jêzyk polski, czyli "pl". Poprawna linijka powinna wygl±daæ tak:
AVAIL_LANGUAGES := cs de hu ru zh_CN zh_TW pl
***************
*** 83,87 ****
$ make && make install
! Uruchonienie spolszczonych aplikacji
====================================
--- 83,87 ----
$ make && make install
! Uruchomienie spolszczonych aplikacji
====================================
|
|
From: <de...@us...> - 2002-05-09 06:02:46
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv24204 Modified Files: psql.po Log Message: final (?) version Index: psql.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/psql.po,v retrieving revision 1.8 retrieving revision 1.9 diff -C2 -d -r1.8 -r1.9 *** psql.po 1 May 2002 07:38:50 -0000 1.8 --- psql.po 9 May 2002 06:02:40 -0000 1.9 *************** *** 187,196 **** msgid "Showing only tuples." msgstr "Pokazywanie samych rekordów w³±czone." - #mod msgstr "Pokazywanie samych krotek w³±czone." #: command.c:1774 msgid "Tuples only is off." msgstr "Pokazywanie samych rekordów wy³±czone." - #mod msgstr "Pokazywanie samych krotek wy³±czone." #: command.c:1790 --- 187,194 ---- *************** *** 539,547 **** #: help.c:199 msgid " \\copyright show PostgreSQL usage and distribution terms\n" ! msgstr "" ! " \\copyright poka¿ prawne informacje na temat u¿ywania i dystrybucji " ! "PostgreSQL'a\n" ! #mod msgstr " \\copyright poka¿ warunki u¿ytkowania i dystrybucji PostgreSQL'a\n" ! #: help.c:200 msgid " \\d TABLE describe table (or view, index, sequence)\n" --- 537,542 ---- #: help.c:199 msgid " \\copyright show PostgreSQL usage and distribution terms\n" ! msgstr " \\copyright poka¿ warunki u¿ytkowania i dystrybucji PostgreSQL'a\n" ! #: help.c:200 msgid " \\d TABLE describe table (or view, index, sequence)\n" *************** *** 1114,1119 **** #: describe.c:861 msgid "Check constraints" ! msgstr "Funkcje sprawdzaj±ce" ! #mod msgstr "Funkcje ograniczajace" (sprawdzacze ograniczen???) #: describe.c:864 --- 1109,1113 ---- #: describe.c:861 msgid "Check constraints" ! msgstr "Funkcje sprawdzaj±ce ograniczenia" #: describe.c:864 |
|
From: <ma...@us...> - 2002-05-07 19:20:03
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv24217 Modified Files: pg_dump.po Log Message: wersja przystosowana do 7.2.1 Index: pg_dump.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/pg_dump.po,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** pg_dump.po 7 May 2002 18:48:48 -0000 1.2 --- pg_dump.po 7 May 2002 19:20:00 -0000 1.3 *************** *** 5,17 **** msgstr "" "Project-Id-Version: PostgreSQL 7.2\n" ! "POT-Creation-Date: 2002-04-25 04:16-0400\n" ! "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: Aleksander Machniak (A.L.E.C) <ama...@go...>\n" ! "Language-Team: LANGUAGE <LL...@li...>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ISO-8859-2\n" "Content-Transfer-Encoding: 8bit\n" [...2682 lines suppressed...] + #~ msgid "" + #~ "query to obtain name of primary key of table \"%s\" returned %d rows\n" + #~ msgstr "" + #~ "zapytanie o nazwê klucza g³ównego tabeli \"%s\" zwróci³o wierszy: %d\n" + + #~ msgid "" + #~ "query to obtain procedure name for trigger \"%s\" (procedure OID %s) " + #~ "returned %d rows\n" + #~ msgstr "" + #~ "zapytanie o nazwê procedury dla wyzwalacza \"%s\" (OID procedury %s) " + #~ "zwróci³o wierszy: %d\n" + + #~ msgid "query to obtain domain information failed: %s" + #~ msgstr "zapytanie o w³a¶ciwo¶ci domen nie powiod³o siê: %s" + + #~ msgid "Domain %s non-existant." + #~ msgstr "Domena %s nie istnieje" + + #~ msgid "wrote remaining %d bytes of large object data (result = %d)\n" + #~ msgstr "do zapisania pozosta³o %d bajtów danych bloba (wynik = %d)\n" |
|
From: <ma...@us...> - 2002-05-07 18:48:55
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv15754 Modified Files: pg_dump.po Log Message: wersja robocza, przed zrownaniem z 7.2.1 Index: pg_dump.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/pg_dump.po,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -C2 -d -r1.1.1.1 -r1.2 *** pg_dump.po 25 Apr 2002 18:38:01 -0000 1.1.1.1 --- pg_dump.po 7 May 2002 18:48:48 -0000 1.2 *************** *** 1,15 **** ! # SOME DESCRIPTIVE TITLE. ! # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # - #, fuzzy msgid "" msgstr "" ! "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: 2002-04-25 04:16-0400\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" ! "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" [...1851 lines suppressed...] #: pg_backup_archiver.c:1151 pg_backup_files.c:138 #, c-format msgid "could not open output file: %s\n" ! msgstr "nie mo¿na otworzyæ pliku wyj¶ciowego: %s\n" #: pg_backup_archiver.c:1167 #, c-format msgid "could not close output file: %s\n" ! msgstr "nie mo¿na zamkn±æ pliku wyj¶ciowego: %s\n" #: pg_backup_archiver.c:1254 #, c-format msgid "wrote %d bytes of large object data (result = %d)\n" ! msgstr "zapisano %d bajtów danych bloba (wynik = %d)\n" #: pg_backup_archiver.c:1273 msgid "could not write to compressed archive\n" ! msgstr "brak mo¿liwo¶ci zapisu do skompresowanego archiwum\n" #: pg_backup_archiver.c:1281 |
|
From: <ma...@us...> - 2002-05-06 16:29:44
|
Update of /cvsroot/polishpgdoc/nls/nls In directory usw-pr-cvs1:/tmp/cvs-serv7653 Modified Files: postgres.po Log Message: WAZNE!!! Merdzing z 7.2.1. Prosze wszystkich o uaktualnienie!!! Index: postgres.po =================================================================== RCS file: /cvsroot/polishpgdoc/nls/nls/postgres.po,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -d -r1.5 -r1.6 *** postgres.po 6 May 2002 16:17:27 -0000 1.5 --- postgres.po 6 May 2002 16:29:37 -0000 1.6 *************** *** 5,9 **** msgstr "" "Project-Id-Version: PostgreSQL 7.2.1\n" ! "POT-Creation-Date: 2002-04-25 04:15-0400\n" "PO-Revision-Date: 2002-05-07 18:16-0200\n" "Last-Translator: Marcin Marurek <m.m...@ne...>\n" --- 5,9 ---- msgstr "" "Project-Id-Version: PostgreSQL 7.2.1\n" ! "POT-Creation-Date: 2002-05-06 18:20-0200\n" "PO-Revision-Date: 2002-05-07 18:16-0200\n" [...24902 lines suppressed...] ! #: ../tcop/fastpath.c:172 #, c-format ! msgid "fetch_fp_info: cache lookup for function %u failed" msgstr "" ! #: ../tcop/fastpath.c:272 #, c-format msgid "" ! "HandleFunctionRequest: actual arguments (%d) != registered arguments (%d)" msgstr "" ! #: ../tcop/fastpath.c:291 ../tcop/fastpath.c:303 #, c-format ! msgid "HandleFunctionRequest: bogus argsize %d" msgstr "" ! #: ../tcop/fastpath.c:316 #, c-format ! msgid "HandleFunctionRequest: bogus argsize %d, should be %d" msgstr "" |
