- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
- 75
Statement stmt1 = null;
ResultSet rs1 = null;
try {
StringBuilder sb = new StringBuilder(2000);
String sql = "";
String ss = "";
String ss_begin = "";
String ss_middle = "";
String ss_end = "";
int xcount = 0;
String XXX_ID = "";
String XXX_NAME = "";
if (c.XLANG_ID == 1) {
sql = sql + " SELECT 99 , 'Исходные' FROM dual union all ";
sql = sql + " SELECT 1 , 'Непарные исходные' FROM dual union all ";
sql = sql + " SELECT 2 , 'Временная' FROM dual union all ";
sql = sql + " SELECT 3 , 'Встречные' FROM dual ";
//sql = sql + " SELECT 4 , 'Непарные встречные' FROM dual ";
} else if (c.XLANG_ID == 2) {
sql = sql + " SELECT 99 , 'Base BPEBs' FROM dual union all ";
sql = sql + " SELECT 1 , 'Base BPEBs unpaired' FROM dual union all ";
sql = sql + " SELECT 2 , 'Temporary BPEB' FROM dual union all ";
sql = sql + " SELECT 3 , 'Generated BPEBs' FROM dual ";
//sql = sql + " SELECT 4 , 'Generated BPEBs unpaired' FROM dual ";
}
stmt1 = this.con.createStatement();
rs1 = stmt1.executeQuery(sql);
while (rs1.next()) {
xcount = xcount + 1;
XXX_ID = rs1.getString(1);
XXX_NAME = rs1.getString(2);
sb = sb.append("<msg>")
.append("<xid>").append(XXX_ID).append("</xid>")
.append("<xname>").append(vtb.budget.osa.tools.Tools.stringToXML(XXX_NAME)).append("</xname>")
.append("</msg>");
}
rs1.close();
stmt1.close();
ss_begin = ss_begin + "<xml id='XML_table1'>"
+ "<tab1>";
ss_end = ss_end
+ "</tab1>"
+ "</xml>";
if (xcount == 0) {
ss_middle = ss_middle + "<msg>"
+ "<xid></xid>"
+ "<xcode></xcode>"
+ "<xname></xname>"
+ "</msg>";
} else {
ss_middle = sb.toString();
}
ss = ss_begin + ss_middle + ss_end;
ss_begin = null;
ss_middle = null;
ss_end = null;
sb = null;
return ss;
}
https://pikabu.ru/story/unichtozhaet_rekursiyu_10120568
ну хотя ты не обязан знать про фракталы, ты же программист, а не математик (я тоже)
https://pikabu.ru/story/transfobnoe_poslanie_10121082
Several other databases (including Microsoft SQL Server, MySQL, PostgreSQL, SQLite, and Teradata) enable one to omit the FROM clause entirely if no table is needed. This avoids the need for any dummy table.
IBM Db2 has a view that resolves DUAL when using Oracle Compatibility.[3] It also has a table called sysibm.sysdummy1 that has similar properties to the Oracle DUAL one.
Informix: Informix version 11.50 and later has a table named sysmaster:"informix".sysdual with the same functionality but a more verbose name.[4] You can use CREATE PUBLIC SYNONYM dual FOR sysmaster:"informix".sysdual to create a name dual in the current database with the same functionality.
Microsoft Access: A table named DUAL may be created and the single-row constraint enforced via ADO (Table-less UNION query in MS Access)
Microsoft SQL Server: SQL Server does not require a dummy table. Queries like 'select 1 + 1' can be run without a "from" clause/table name.[5]
MySQL allows DUAL to be specified as a table in queries that do not need data from any tables.[6] It is suitable for use in selecting a result function such as SYSDATE() or USER(), although it is not essential.
PostgreSQL: A DUAL-view can be added to ease porting from Oracle.[7]
SQLite: A VIEW named "dual" that works the same as the Oracle "dual" table can be created as follows: CREATE VIEW dual AS SELECT 'x' AS dummy;
SAP HANA has a table called DUMMY that works the same as the Oracle "dual" table.
Teradata database does not require a dummy table. Queries like 'select 1 + 1' can be run without a "from" clause/table name.
Vertica has support for a DUAL table in their official documentation.[8]
“I created the DUAL table as an underlying object in the Oracle Data Dictionary. It was never meant to be seen itself, but instead used inside a view that was expected to be queried. The idea was that you could do a JOIN to the DUAL table and create two rows in the result for every one row in your table. Then, by using GROUP BY, the resulting join could be summarized to show the amount of storage for the DATA extent and for the INDEX extent(s). The name, DUAL, seemed apt for the process of creating a pair of rows from just one.”
Какой багор )))
Возможно, правильное решение не ломать синтаксис, но плохо, что они внезапно сменили количество строк у таблицы dual. Столько кода сразу сломалось...
https://pbs.twimg.com/media/FqAPEOSWAAQtgZ6?format=jpg&name=medium
kokoon = illative singular of koko = все вместе
koko = размер (существительное) или весь (наречие)
nominative koko koot
genitive koon kokojen
partitive kokoa kokoja
illative kokoon kokoihin
-----
kokko = костёр
nominative kokko kokot
genitive kokon kokkojen
partitive kokkoa kokkoja
illative kokkoon kokkoihin
----
Kokoo и kokkoko не нашёл. Придётся учить грамматику, чтобы понять начальную форму.
У тюрков во множественном числе окончание -лар- (либо дар, тар, нар, лер, дер, тер, нер, если язык поддерживает сингармонизм) добавляется во всех падежах перед падежным окончанием.
А у финно-угров нужно учить окончание каждого падежа в обоих числах, как в индоевропейских языках, сохранивших склонения. Радует то, что у финно-угров склонение одно.
present tense perfect
person positive negative person positive negative
1st sing. kokoan en kokoa 1st sing. olen koonnut en ole koonnut
2nd sing. kokoat et kokoa 2nd sing. olet koonnut et ole koonnut
3rd sing. kokoaa ei kokoa 3rd sing. on koonnut ei ole koonnut
1st plur. kokoamme emme kokoa 1st plur. olemme koonneet emme ole koonneet
2nd plur. kokoatte ette kokoa 2nd plur. olette koonneet ette ole koonneet
3rd plur. kokoavat eivät kokoa 3rd plur. ovat koonneet eivät ole koonneet
passive kootaan
present perfect
person positive negative person positive negative
1st sing. — — 1st sing. — —
2nd sing. kokoa älä kokoa 2nd sing. ole koonnut älä ole koonnut
3rd sing. kootkoon älköön kootko 3rd sing. olkoon koonnut älköön olko koonnut
1st plur. kootkaamme älkäämme kootko 1st plur. olkaamme koonneet älkäämme olko koonneet
2nd plur. kootkaa älkää kootko 2nd plur. olkaa koonneet älkää olko koonneet
3rd plur. kootkoot älkööt kootko 3rd plur. olkoot koonneet älkööt olko koonneet
passive koottakoon älköön koottako passive olkoon koottu älköön olko koottu
1. Kokoo koko kokko kokoon. = Put together the whole bonfire (Put up the bonfire).
Kokoo = put together
Kokoo = spoken language version of kokoa. Kokoa = imperative of koota, meaning to put together
koko = all, entire
kokko = bonfire
kokoon = together, in one piece
koko = size, measure; kokoon = ilative of koko, used here as an emphasizer, meaning: in(to) one piece
koota kokoon = to put together, to build up, to put all the parts together into one piece
2. Koko kokkoko kokoon? = The whole bonfire together?
kokkoko = kokko + ko: the interrogative form, meaning that the target of the question is kokko
-ko: interrogative particle, used to emphasize the target of a question
3. Koko kokko kokoon. = The whole bonfire together (this is the answer to the previous question).
Notice that the only difference compared to the question is the missing -ko particle from kokkoko.