1 # KDE3 - kexi_database.pot Russian translation.
3 # Dimitriy Ryazantcev <DJm00n@rambler.ru>, 2006.
4 # Nick Shaforostoff <shafff@ukr.net>, 2007.
7 "Project-Id-Version: kexi_database\n"
8 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
9 "POT-Creation-Date: 2008-02-11 07:20+0000\n"
10 "PO-Revision-Date: 2007-02-05 09:16+0200\n"
11 "Last-Translator: Nick Shaforostoff <shafff@ukr.net>\n"
12 "Language-Team: Russian <kde-russian@lists.kde.ru>\n"
14 "Content-Type: text/plain; charset=UTF-8\n"
15 "Content-Transfer-Encoding: 8bit\n"
16 "X-KDE-DocBook-SVN-URL: trunk/koffice/doc/kexi/database.docbook\n"
17 "X-KDE-DocBook-SVN-Changed-Revision: 481839\n"
18 "X-Generator: KBabel 1.11.4\n"
19 "Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%"
20 "10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"
25 msgid "Introduction to Databases"
26 msgstr "Введение в базы данных"
31 msgid "What Is a Database?"
32 msgstr "Что такое база данных?"
35 #: database.docbook:10
38 "You can define a database as a collection of data on one topic. It is "
39 "organised in a way allowing to easily browse the information, make changes "
42 "Базу данных можно определить как набор данных с одной тематикой, "
43 "организованных способом, позволяющим легко их просматривать, изменять и "
47 #: database.docbook:15
50 "Look at this diagram for one of the above examples: a simple phone book."
51 msgstr "На схеме выше приведен пример базы данных: простая телефонная книга."
54 #: database.docbook:19
56 msgid "<screeninfo>A diagram of a phone number database</screeninfo>"
57 msgstr "<screeninfo>Схема базы данных телефонной книги</screeninfo>"
60 #: database.docbook:25
62 msgid "<phrase>A diagram of a phone number database</phrase>"
63 msgstr "<phrase>Схема базы данных телефонной книги</phrase>"
66 #: database.docbook:29
69 "The above picture shows a set of two contacts each of which is presented on "
70 "a separate card. It appears that such a card can constitute a single row in "
73 "На рисунке выше показаны два контакта, каждый из которых размещён на "
74 "отдельной карточке. Для каждой карточки можно выделить по одной строке в "
78 #: database.docbook:35
80 msgid "<guilabel>Contacts</guilabel> table"
81 msgstr "Таблица <guilabel>Contacts</guilabel> "
84 #: database.docbook:40
86 msgid "<guilabel>Name</guilabel>"
87 msgstr "<guilabel>Name (Имя)</guilabel>"
90 #: database.docbook:41
93 msgstr "Tel No. (номер телефона)"
96 #: database.docbook:44 database.docbook:290 database.docbook:361
102 #: database.docbook:45 database.docbook:136
105 msgstr "699 23 43 12"
108 #: database.docbook:48 database.docbook:297 database.docbook:369
114 #: database.docbook:49 database.docbook:141
117 msgstr "711 19 77 21"
120 #: database.docbook:55
123 "<emphasis>Terms and definitions</emphasis>: A single data which constitutes "
124 "a part of a greater collection can be called a <firstterm>row</firstterm> or "
125 "more professionally a <firstterm>record</firstterm>. The collection is "
126 "normally called a <firstterm>table</firstterm>. Moreover, the most natural "
127 "name for the table is one describing the data it offers/stores which is "
128 "<guilabel>Contacts</guilabel>. Furthermore, each row in the table consists "
129 "of <firstterm>columns</firstterm> often also called <firstterm>fields</"
130 "firstterm>. In the table <guilabel>Contacts</guilabel> there are two columns "
131 "(fields): <guilabel>Name</guilabel> and <guilabel>Tel No.</guilabel>."
133 "<emphasis>Термины и определения</emphasis>: <firstterm>Таблица</firstterm> - "
134 "это набор однородных данных, называемых <firstterm>строками</firstterm>, или "
135 "<firstterm>записями</firstterm> (более профессионально). Колонки в таблице - "
136 "<firstterm>поля</firstterm>. В таблице <guilabel>Contacts</guilabel> два "
137 "поля: <guilabel>Name</guilabel> (имя) и <guilabel>Tel No.</guilabel> (номер "
141 #: database.docbook:68
144 "For simple uses a single table can make up a <firstterm>database</"
145 "firstterm>. Many people consider these two equivalent. As you will see, for "
146 "real databases we usually need more than one table."
148 "В упрощённом варианте базу данных может образовывать только одна таблица. "
149 "Некоторые люди даже считают эти понятия эквивалентными. На практике вы "
150 "увидите, что для базы данных обычно требуется больше одной таблицы."
153 #: database.docbook:73
156 "To sum up, you have already got a simple database with one table "
157 "<guilabel>Contacts</guilabel>."
159 "Итак, на данный момент вы создали простую базу данных, <guilabel>Contacts</"
160 "guilabel>, состоящую из одной таблицы."
163 #: database.docbook:81
165 msgid "Database and Spreadsheet"
166 msgstr "Базы данных и электронные таблицы"
169 #: database.docbook:82
172 "It is very likely that you have already used spreadsheet applications like "
173 "KSpread, OpenOffice.org Calc or Microsoft Excel. If so, you will probably "
174 "wonder: since both spreadsheets and databases have tables, why should I use "
177 "Вероятно, вы уже знакомы с программами для работы с электронными таблицами, "
178 "например, KSpread, OpenOffice.org Calc или Microsoft Excel. Если да, то у "
179 "вас, наверное, возник вопрос: и электронные таблицы, и базы данных содержат "
180 "таблицы - зачем же нужны вторые?"
183 #: database.docbook:88
186 "While comparing spreadsheets and databases you may encounter the following "
187 "issues which you will later see in greater detail:"
189 "При сравнении таблиц и баз данных необходимо учитывать следующие вопросы "
190 "(далее мы рассмотрим их поподробнее):"
193 #: database.docbook:92
195 msgid "<link>Referential data integrity</link>"
196 msgstr "<link>Целостность связей между элементами данных</link>"
199 #: database.docbook:94
201 msgid "<link>Data redundancy</link>"
202 msgstr "<link>Избыточность данных</link>"
205 #: database.docbook:96
207 msgid "<link>Data integrity and validity</link>"
208 msgstr "<link>Целостность и допустимость вводимой информации</link>"
211 #: database.docbook:98
213 msgid "<link>Limiting data view</link>"
214 msgstr "<link>Частичный вывод данных</link>"
217 #: database.docbook:99
219 msgid "<link>Performance and capacity</link>"
221 "<link>Производительность и максимальный объём хранимой информации</link>"
224 #: database.docbook:101
226 msgid "Convenient data entry"
227 msgstr "Удобный ввод информации"
230 #: database.docbook:102
232 msgid "<link>Reports</link>"
233 msgstr "<link>Отчёты</link>"
236 #: database.docbook:103
238 msgid "<link>Programming</link>"
239 msgstr "<link>Программирование</link>"
242 #: database.docbook:104
244 msgid "<link>Multiuse</link>"
245 msgstr "<link>Параллельное использование несколькими людьми</link>"
248 #: database.docbook:105
250 msgid "<link>Security</link>"
251 msgstr "<link>Безопасность</link>"
254 #: database.docbook:109
256 msgid "How Is a Database Different From a Spreadsheet?"
257 msgstr "Чем базы данных отличаются от электронных таблиц?"
260 #: database.docbook:111
263 "Gradually exceeding the capacity of a mobile phone, expand your table "
264 "<guilabel>Contacts</guilabel> adding a column (field) <guilabel>Address</"
265 "guilabel>. Add more telephone numbers (office, home) for each person and add "
266 "surnames to names. To make it simpler we assume the following:"
268 "Если позволяет память вашего мобильного телефона, вы можете дополнить "
269 "таблицу контактов колонками (полем) <guilabel>Address</guilabel> (адрес). "
270 "Можно также добавить другие телефонные номера (офис, домашний), поле "
271 "фамилии. Для упрощения предлагается следующее:"
274 #: database.docbook:119
277 "the table is limited to two people (obviously, there could be hundreds and "
278 "thousands of them in a real database)"
280 "в таблице только два человека (что в настоящей базе их могут быть сотни и "
284 #: database.docbook:122
286 msgid "there are no two persons with the same name and surname"
287 msgstr "двух человек с одинаковыми именами и фамилиями нет"
290 #: database.docbook:125
292 msgid "Contacts table"
293 msgstr "Таблица Contacts "
296 #: database.docbook:130 database.docbook:207
298 msgid "Name and surname"
299 msgstr "Name and surname (Имя и фамилия)"
302 #: database.docbook:131
304 msgid "<emphasis>Tel</emphasis>"
305 msgstr "<emphasis>Tel (Тел. номер)</emphasis>"
308 #: database.docbook:132 database.docbook:208
311 msgstr "Address (Адрес)"
314 #: database.docbook:135 database.docbook:145 database.docbook:211
320 #: database.docbook:137 database.docbook:212
322 msgid "Western Gate 1, Warsaw"
323 msgstr "Western Gate 1, Warsaw"
326 #: database.docbook:140 database.docbook:215
329 msgstr "Adam Willson"
332 #: database.docbook:142
334 msgid "London, Frogs Drive 5"
335 msgstr "London, Frogs Drive 5"
338 #: database.docbook:146
341 msgstr "110 98 98 00"
344 #: database.docbook:147
346 msgid "Western Gate 1"
347 msgstr "Western Gate 1"
350 #: database.docbook:150
356 #: database.docbook:151
359 msgstr "312 43 42 22"
362 #: database.docbook:152
364 msgid "Warsaw, Western Gate 1"
365 msgstr "Warsaw, Western Gate 1"
368 #: database.docbook:155
371 msgstr "ADAM Willson"
374 #: database.docbook:156
377 msgstr "231 83 02 04"
380 #: database.docbook:157 database.docbook:216
382 msgid "Frogs Drive 5, London"
383 msgstr "Frogs Drive 5, London"
386 #: database.docbook:163
389 "Such a table can be made both in a spreadsheet and in a database. Using a "
390 "spreadsheet is very easy, of couse. What problems do we encounter at this "
393 "Такую таблицу можно создать в виде электронной таблицы или базы данных. "
394 "Первой пользоваться очень просто. Какие же проблемы могут возникнуть? "
397 #: database.docbook:170
399 msgid "<title>Referential data integrity</title>"
400 msgstr "<title>Целостность связей между элементами данных</title>"
403 #: database.docbook:171
406 "Suppose you are using a spreadsheet and you need to change the address of at "
407 "least one person. You have a small problem: you often have to change the "
408 "address in many rows. For example, Joan takes three rows. A real problem "
409 "will arise if you forget to change one of the rows - the address asigned to "
410 "this person will be <emphasis>ambiguous</emphasis>, hence <emphasis>your "
411 "data loses integrity</emphasis>."
413 "Предположим, вы используете электронные таблицы и вам нужно изменить адрес "
414 "как минимум одного человека. Вы столкнётесь с затруднением: придётся менять "
415 "адреса в нескольких колонках. Например, данные о Joan занимают три записи. "
416 "Настоящая проблема возникнет, если вы забудете изменить одну из строк - "
417 "адрес человека перестанет быть однозначным и ваша запись потеряет "
421 #: database.docbook:179
424 "Moreover there is no simple way of deleting a chosen person from the table "
425 "since you have to remember about deleting all rows releted to him or her."
427 "Более того, не существует простого способа удалить выбранный контакт из "
428 "таблицы, поскольку нужно удалить все строки, относящиеся к данному человеку."
431 #: database.docbook:187
433 msgid "<title>Data redundancy</title>"
434 msgstr "<title>Избыточность данных</title>"
437 #: database.docbook:188
440 "This is directly connected to the previous problem. In fields <guilabel>Name "
441 "and surname</guilabel> and <guilabel>Address</guilabel> the same data is "
442 "entered many times. This is typical of a spreadsheets' ineffective way of "
443 "storing data because the database grows unnecessarily, thus requiring more "
444 "computer resources (larger size of data and slower access)."
446 "Это вытекает из предыдущего пункта. В поля <guilabel>Name and surname</"
447 "guilabel> (имя/фамилия) и <guilabel>Address</guilabel> (адрес) несколько раз "
448 "вводится одна и та же информация. Поэтому хранить данные такого рода в "
449 "электронных таблицах неэффективно: неприемлемо увеличивается размер базы "
450 "данных и замедляется доступ к ней."
453 #: database.docbook:195
456 "How can you solve these problems with a database? You can split information "
457 "into smaller chunks by creating an additional table <emphasis>Persons</"
458 "emphasis> with only two columns: <guilabel>Name and surname</guilabel> and "
459 "<guilabel>Address</guilabel>:"
461 "Как решаются подобные вопросы в базах данных? Во-первых, данные можно "
462 "разбить на части и ввести дополнительную таблицу в двумя колонками: "
463 "<guilabel>Name and surname</guilabel> (имя/фамилия) и <guilabel>Address</"
467 #: database.docbook:202
469 msgid "<guilabel>Persons</guilabel> table"
470 msgstr "Таблица <guilabel>persons</guilabel>"
473 #: database.docbook:222
476 "Each row in the table <guilabel>Persons</guilabel> corresponds to a "
477 "<emphasis>single person</emphasis>. Table <guilabel>Contacts</guilabel> is "
478 "from now on a relation to the table <guilabel>Persons</guilabel> ."
480 "Каждая строка соответствует <emphasis>отдельному человеку</emphasis>. "
481 "Таблица <guilabel>Contacts</guilabel> связывается с <guilabel>Persons</"
485 #: database.docbook:232
487 msgid "<title>Data integrity and validity</title>"
488 msgstr "<title>Целостность и допустимость вводимой информации</title>"
491 #: database.docbook:233
494 "Note the way data is entered in the fields <guilabel>Name and surname</"
495 "guilabel> and <guilabel>Address</guilabel>. People entering data can be "
496 "fallible, sometimes even negligent. In our sample data we have both "
497 "different sequence of entering name and surname (Joan Smith and Smith Joan; "
498 "Adam and ADAM) and many more ways of entering the same address. Surely you "
499 "can think of many other ways."
501 "Обратите внимание на способ заполнения полей <guilabel>Name and surname</"
502 "guilabel> (имя/фамилия) и <guilabel>Address</guilabel> (адрес). При вводе "
503 "люди могут допускать ошибки или небрежности. В нашем примере имя и фамилию "
504 "можно ввести в разном порядке, то же касается и адреса. Могут быть и другие "
508 #: database.docbook:241
511 "The above problem shows that ⪚ when searching the telephone number of a "
512 "person whose address is \"Western Gate 1, Warsaw\" you will not get a full "
513 "result. You will get only one row instead of three. Moreover You will also "
514 "not find all the telephone numbers searching for the value \"Joan Smith\" in "
515 "the field <guilabel>Name and surname</guilabel>, because \"Smith Joan\" will "
516 "not fit to \"Joan Smith\"."
518 "Из-за данной особенности при поиске телефонных номеров по адресу \"Western "
519 "Gate 1, Warsaw\" вы в результате не получите полного результата. "
522 #: database.docbook:249
525 "How can you solve these problems using a database? You can do this by "
526 "changing the design of the table <guilabel>Persons</guilabel> by:"
528 "Как такая проблема решается в базах данных? Вы можете изменить структуру "
529 "таблицы <guilabel>Persons</guilabel>:"
532 #: database.docbook:253
535 "<emphasis>Dividing data</emphasis> in the field <guilabel>Name and surname</"
536 "guilabel> into two separate fields: <guilabel>Name</guilabel> and "
537 "<guilabel>Surname</guilabel>."
539 "<emphasis>Разделить</emphasis> поле <guilabel>Name and surname</guilabel> "
540 "(имя и фамилия) на два отдельных: поле <guilabel>Name</guilabel> (имя) и "
541 "поле <guilabel>Surname</guilabel> (фамилия)."
544 #: database.docbook:258
547 "<emphasis>Dividing data</emphasis> in the field <guilabel>Address</guilabel> "
548 "into three separate fields: <guilabel>Street</guilabel>, <guilabel>House "
549 "number</guilabel> and <guilabel>City</guilabel>."
550 msgstr "Разбить поле Адрес на три: Улица, Номер дома и Город."
553 #: database.docbook:263
556 "<emphasis>Guaranteeing data correctness:</emphasis> by ensuring that no "
557 "fields are empty, ⪚ you must always enter house number."
559 "Гарантировать корректность введенной информации можно, если не оставлять "
560 "поля незаполненными, например, вы всегда обязаны ввести номер дома."
563 #: database.docbook:269
565 msgid "A modified table looks something like this:"
566 msgstr "Модифицированная таблица будет выглядеть так:"
569 #: database.docbook:273 database.docbook:348
571 msgid "Persons table"
572 msgstr "Таблица Persons"
575 #: database.docbook:283 database.docbook:353
577 msgid "<emphasis>Name</emphasis>"
578 msgstr "<emphasis>Name (имя)</emphasis>"
581 #: database.docbook:284 database.docbook:354
584 msgstr "Surname (фамилия)"
587 #: database.docbook:285 database.docbook:355
590 msgstr "Street (улица)"
593 #: database.docbook:286 database.docbook:356
596 msgstr "House number (номер дома)"
599 #: database.docbook:287 database.docbook:357
602 msgstr "City (город)"
605 #: database.docbook:291 database.docbook:362
611 #: database.docbook:292 database.docbook:363
614 msgstr "Western Gate"
617 #: database.docbook:293 database.docbook:364
619 msgid "<entry>1</entry>"
620 msgstr "<entry>1</entry>"
623 #: database.docbook:294 database.docbook:365
629 #: database.docbook:298 database.docbook:370
635 #: database.docbook:299 database.docbook:371
641 #: database.docbook:300 database.docbook:372
643 msgid "<entry>5</entry>"
644 msgstr "<entry>5</entry>"
647 #: database.docbook:301 database.docbook:373
653 #: database.docbook:304
659 #: database.docbook:307 database.docbook:308 database.docbook:309
660 #: database.docbook:310 database.docbook:311
662 msgid "required field"
663 msgstr "необходимое поле"
666 #: database.docbook:317
669 "Thanks to introducing the condition <guilabel>required field</guilabel> we "
670 "can be sure that the entered data is complete. In case of other tables you "
671 "may of course allow omitting certain fields while entering data."
675 #: database.docbook:326
677 msgid "<title>Limiting data view</title>"
678 msgstr "<title>Частичный вывод данных</title>"
681 #: database.docbook:327
684 "A spreadsheet displays all rows and columns of the table which is bothersome "
685 "in case of very large data sheets. You may of course filter and sort rows in "
686 "spreadsheets, however you must be extra careful while doing so. Spreadsheet "
687 "users are in risk of forgetting that their data view has been filtered what "
688 "can lead to mistakes. For example, while calculating sums you may think you "
689 "have 100 rows of data while in fact there are 20 rows more hidden."
691 "Электронная таблица, в которой показаны сразу все строки и столбцы, выглядит "
692 "громоздко, особенно если она очень большая. Строки можно фильтровать и "
693 "сортировать, но делать это нужно очень осторожно. Пользователь заранее "
694 "должен помнить обо всех изменениях, иначе возникают ошибки. Например, вы "
695 "можете просуммировать 100 строк, забыв, что ещё 20 были спрятаны."
698 #: database.docbook:335
701 "If you want to work on a small subset of data, ⪚ to send it for others to "
702 "edit, you can copy and paste it to another spreadsheet and after editing "
703 "paste the changed data back to the main spreadsheet. Such \"manual\" editing "
704 "may cause data loss or incorect calculations."
706 "Если вы хотите работать только с частью данных, например, отправить кому-то "
707 "другому для редактирования, вы можете скопировать их в отдельный лист, а "
708 "после изменения поместить назад в исходную таблицу. Такое \"редактирование\" "
709 "может привести к потере данных или ошибкам в вычислениях."
712 #: database.docbook:338
715 "To limit the <emphasis>data view</emphasis> database applications offer "
716 "<emphasis>queries</emphasis>, <emphasis>forms</emphasis> and "
717 "<emphasis>reports</emphasis>."
721 #: database.docbook:343
724 "A very practical way of limitting is the following extended version of the "
725 "previously described table <guilabel>Persons</guilabel>:"
729 #: database.docbook:358
732 msgstr "Income (доход)"
735 #: database.docbook:366
741 #: database.docbook:374
747 #: database.docbook:380
750 "Let's assume that the newly introduced column <guilabel>Income</guilabel> "
751 "contains confidential data. How can you share ⪚ contact details of the "
752 "persons with your coworkers but without <emphasis>revealing their income</"
753 "emphasis>? It is possible if <emphasis>you share only a query and not the "
754 "whole table</emphasis>. The query could select all columns except for the "
755 "column <guilabel>Income</guilabel>. In database world such a query is often "
756 "known as a <guilabel>view</guilabel>."
760 #: database.docbook:393
762 msgid "<title>Performance and capacity</title>"
766 #: database.docbook:394
769 "Your computer is probably quite fast, however you will easily see that it "
770 "doesn't help with slow, large spreadsheets. Their low efficiency is first of "
771 "all due to lack of indexes accelertaing the process of data search "
772 "(databases do offer them). Moreover if you use things like system clipboard, "
773 "even copying data may become troublesome with time."
775 "У вас может быть очень быстрый компьютер, но работа с достаточно большими "
776 "электронными таблицами всё равно будет медленной. Низкая скорость "
777 "обусловлена недостатком индексов, которые обеспечивают связь между "
778 "элементами и ускоряют процесс поиска данных (в базах данных они "
779 "предусматриваются автоматически). Если используется системный буфер обмена, "
780 "то даже копирование информации будет сопряжено с трудностями."
783 #: database.docbook:401
786 "Spreadsheets containing large data sets may take ages to open. A spreadsheet "
787 "loads lots of data to the computer's memory while opening. Most of the data "
788 "loaded are probably useless/unneccessary for you at the moment. Databases "
789 "unlike spreadsheets load data from computer storage only when needed."
793 #: database.docbook:407
796 "In most cases you will not have to worry how the database stores its data. "
797 "This means that unlike spreadsheets, databases do not care about:"
801 #: database.docbook:412
804 "The sequence of rows since you can order the rows according to your needs. "
805 "Moreover, you can view the same data in many views with different orders."
809 #: database.docbook:416
811 msgid "The same goes for columns (fields) of the table."
815 #: database.docbook:421
818 "Together with <link linkend=\"data-limiting\">Limiting data view</link> "
819 "described in the previous paragraph these qualities constitute the advantage "
824 #: database.docbook:430
830 #: database.docbook:431
833 "The latest editions of applications for creating spreadsheets enable you to "
834 "design data-entry forms. Such forms are most useful if your data cannot be "
835 "conveniently displayed in tabular view, ⪚ if the text occupies too many "
836 "rows or if all the columns do not fit on the screen."
840 #: database.docbook:437
843 "In this case the very way the spreadsheet works is problematic. Fields for "
844 "data entry are placed loosely within the spreadsheet and very often are not "
845 "secure against the user's (intentional or accidental) intervention."
849 #: database.docbook:446
851 msgid "<title>Reports</title>"
852 msgstr "<title>Отчёты</title>"
855 #: database.docbook:447
858 "Databases enable grouping, limiting and summing up data in a form of a "
859 "<emphasis>report</emphasis>. Spreadsheets are usually printed in a form of "
860 "small tables without fully automatic control over page divisions and the "
865 #: database.docbook:456
867 msgid "<title>Programming</title>"
868 msgstr "<title>Программирование</title>"
871 #: database.docbook:457
874 "Applications for creating databases often contain full programming "
875 "languages. Newer spreadsheets have this capability too, however calculations "
876 "come down to modifying the spreadsheet's fields and simple data copying, "
877 "regardless of the relevance and integrity rules mentioned in previous "
882 #: database.docbook:463
885 "Data processing within a spreadsheet is usually done via a graphical user's "
886 "interface which may slow down the data processing speed. Databases are "
887 "capable of working in background, outside of graphical interfaces."
891 #: database.docbook:471
893 msgid "<title>Multiuse</title>"
894 msgstr "<title>Параллельное использование несколькими людьми</title>"
897 #: database.docbook:472
900 "It is hard to imagine a multiuse of one spreadsheet. Even if it is "
901 "technically possible in the case of the latest applications, it requires a "
902 "lot of discipline, attention and knowledge from the users, and these cannot "
907 #: database.docbook:478
910 "A classical way to sharing data saved in a spreadsheet with other person is "
911 "to send a file as a whole (usually using e-mail) or providing a spreadsheet "
912 "file in a computer network. This way of work is ineffective for larger "
913 "groups of people - data that could be needed in a particular time may be "
914 "currently locked by another person."
918 #: database.docbook:485
921 "On the other hand, databases have been designed mainly with multiuser access "
922 "in mind. Even for the simplest version locking at a particular table row's "
923 "level is possible, which enables easy sharing of table data."
927 #: database.docbook:493
929 msgid "<title>Security</title>"
933 #: database.docbook:494
936 "Securing a spreadsheet or its particular sections with a password is only "
937 "symbolic activity. After providing a spreadsheet file in a computer network, "
938 "every person being able to copy the file can try to break the password. It "
939 "is sometimes not so hard as the password is stored in the same file as the "
944 #: database.docbook:501
947 "Features for edit locking or copy locking of a spreadsheet (or its part) is "
948 "equally easy to break."
952 #: database.docbook:505
955 "Databases (except these saved in a file instead of a server) do not need to "
956 "be available in a single file. You're accessing them using a computer "
957 "network, usually by providing a user name and a password. You are gaining "
958 "access only to these areas (tables, forms or even selected rows and columns) "
959 "which were assigned to you by setting appropriate access rights."
963 #: database.docbook:512
966 "Access rights can affect ability of data editing or only data reading. If "
967 "any data is not avaliable to you, it will not be even sent to your computer, "
968 "so there is no possibility of making a copy of the data in such easy way as "
969 "in case of spreadsheet files."
973 #: database.docbook:524
975 msgid "Database Design"
976 msgstr "Проектирование баз данных"
979 #: database.docbook:525
982 "Database design needs careful planning. Note that <guilabel>Contacts</"
983 "guilabel> table redesign proposed in section 1.2 can generate problems when "
984 "the table is filled with data. For example, renaming a field is a simple "
985 "task, but splitting the <guilabel>Address</guilabel> field into separate "
986 "fields requires careful and tedious work."
990 #: database.docbook:532
993 "To avoid such situations, <emphasis>rethink your database project</emphasis> "
994 "before you create it in your computer, and before you and others will start "
995 "to use it. Thus, by investing some time initially, you will most probably "
996 "save your time on everyday use."
1000 #: database.docbook:541
1002 msgid "Who Needs a Database?"
1003 msgstr "Нужны ли мне базы данных?"
1006 #: database.docbook:543
1008 msgid "Stick to spreadsheets if:"
1012 #: database.docbook:544
1015 "Your needs are limited and your data will never grow to large volumes (can "
1016 "you actually forecast that now?)"
1020 #: database.docbook:548
1023 "You are unable to acquire the methodology of database construction. You may "
1024 "however consider either outsourcing this task to someone else or using "
1029 #: database.docbook:553
1032 "You use complicated spreadsheets and you lack time or money to switch to "
1033 "databases. Think or ask someone whether this does not lead down a blind "
1034 "alley. Don't count on magical tools that would change your spreadsheet "
1035 "(regardless how well made) into a database."
1039 #: database.docbook:562
1041 msgid "Consider using databases if:"
1045 #: database.docbook:563
1047 msgid "Your data collection expands every week."
1051 #: database.docbook:564
1054 "You often create new spreadsheets, copy within these and you feel that this "
1055 "work is getting more and more tedious. In this case the effort of switching "
1056 "to databases easily pays off."
1060 #: database.docbook:569
1063 "You create reports and statements for which the table view of a spreadsheet "
1064 "is not suitable. You can then consider switch to using a database with form "
1069 #: database.docbook:578
1071 msgid "Database Creation Software"
1072 msgstr "Программы для создания баз данных"
1075 #: database.docbook:579
1078 "So far you have learnt the general characteristics of databases without "
1079 "going into much detail about specific applications for designing them."
1083 #: database.docbook:583
1086 "The first databases were built together with large mainframe computers in "
1087 "the 60s, ⪚ IBM System/360. Those were not the days of PCs, therefore "
1088 "these databases required a highly specialized personnel. Although the old "
1089 "computers' hardware was unreliable, they were immeasurably slower and had "
1090 "less storage capacity, one feature of databases still remains most "
1091 "attractive: the data access by many users through a network."
1095 #: database.docbook:591
1098 "In the 70s scientists formed the theory of relational databases (terms like: "
1099 "<firstterm>table</firstterm>, <firstterm>record</firstterm>, "
1100 "<firstterm>column (field)</firstterm> and <firstterm>relationality</"
1101 "firstterm> and many others). On the basis of this theory IBM DB2 and Oracle "
1102 "databases were created, which have been developed and used till today. In "
1103 "the late 70s the first PCs were constructed. Their users could (gradually) "
1104 "utilize many types of applications, including those for database "
1109 #: database.docbook:601
1112 "When it comes to large databases in companies, the situation hasn't changed: "
1113 "they still require powerful computers or computer complexes called "
1114 "<firstterm>clusters</firstterm>. This goes, however, beyond the topic of "
1119 #: database.docbook:607
1122 "In the area of \"accessible\" databases with graphic user interface for PCs "
1123 "you can choose from the following:"
1127 #: database.docbook:613
1130 "<ulink url=\"http://www.dbase.com/\">DBase</ulink> - a tool for databases "
1131 "operation for DOS popular in the 80s. Files in DBase format are still used "
1132 "in some specific cases due to their simplicity."
1136 #: database.docbook:618
1139 "<ulink url=\"http://msdn.microsoft.com/vfoxpro/productinfo/overview/"
1140 "\">FoxPro</ulink> - an application similar to DBase (early 90s). After being "
1141 "taken over by Microsoft, graphic user interfaces were introduced and "
1142 "therefore it is used for creating databases on PCs. This product is still "
1143 "offered, though seems a bit obsolete."
1147 #: database.docbook:625
1150 "<ulink url=\"http://office.microsoft.com/access/\">Microsoft Access</ulink> "
1151 "- an application for databases (data and graphic interface design) with many "
1152 "simplifications, therefore suitable for beginners, designed in the late 80s, "
1153 "based on 16-Bit Architecture. This product is offered and widely used till "
1154 "today, especially by small companies, where efficiency and multiuser "
1155 "requirements are not very demanding."
1159 #: database.docbook:632
1162 "<ulink url=\"http://www.filemaker.com/\">FileMaker</ulink> - popular "
1163 "application similar to MS Access in simplicity, operating on Windows and "
1164 "Macintosh platforms, offered since 1985."
1168 #: database.docbook:637
1171 "<ulink url=\"http://www.kexi.pl/\">&kexi;</ulink> - a multiplatform "
1172 "application (Unix/Linux, Windows, Mac OS X) designed in 2003, developed "
1173 "according to OpenSource principles, part of the global <ulink url=\"http://"
1174 "www.kde.org/\">K Desktop Environment</ulink> project, &ie; graphic "
1175 "environment for Unix/Linux systems. A significant contributor to &kexi;'s "
1176 "development is the OpenOffice Poland company."