issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-19 10:11:53 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2004-08-19 10:13:40 +0200
## Comment 1678
Date: 2004-08-19 22:11:53 +0200
From: @grobian
Argh!!!!
After I managed to build MonetDB (swig doesn't produce
compilable code on my Gentoo system, it probably hasn't
that old software as CWI systems), a connect to the
database fails immediately with an end of stream
reached for the client, and an assertion on the server.
$ run_monet_sql
Monet Database Server V4.3.19
Copyright (c) 1993-2004, CWI. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
monet>Mserver:
/nfs/poseidon/Temp/monet/sql/src/server/sql_mvc.mx:2977:
mvc_bind: Assertion `t' failed.
Killed
Grrrr.
## Comment 1679
Date: 2004-08-19 22:13:40 +0200
From: @grobian
Logged In: YES
user_id=963970
It is not as worse as it sounds.
Niels forgot to increment the DB version counter. Removing
the dbfarm helps.
## Comment 1680
Date: 2005-10-06 17:20:24 +0200
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-10-06: Claimed by jennie
BugDay_2005-10-06: Done.
BugDay_2005-10-06: NO TEST
Bug caused by wrong DB version number
## Comment 1681
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1012460 at http://sourceforge.net/support/tracker.php?aid=1012460
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-sql@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| SQL: Monet crashes on JDBC connect | https://api.github.com/repos/MonetDB/MonetDB/issues/310/comments | 0 | 2020-11-30T08:28:22Z | 2024-06-28T13:36:27Z | https://github.com/MonetDB/MonetDB/issues/310 | 753,268,531 | 310 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-19 11:34:43 +0200
From: @arjan
To: @sjoerdmullender
Version: -- development
Last updated: 2004-08-19 02:56:03 +0200
## Comment 1673
Date: 2004-08-19 11:34:43 +0200
From: @arjan
Executing a invalid query apparently does not set
mapi_error() anymore.
Attached is a test C program, compile with
gcc `monet-config --cflags --libs` -lMapi mapitest.c -o
mapitest
Output of the program at my machine is
--
crater:~> ./mapitest
We should not have gotten here :-(
--
Or am i missing something here?
## Comment 1674
Date: 2004-08-19 12:59:04 +0200
From: @arjan
Logged In: YES
user_id=20087
maybe the problem is that a - header is printed before the
error. MapiClient demo:
sql>fjsdlfdsa;
-
MAPI = monetdb@localhost:45123
QUERY = fjsdlfdsa;
ERROR = !ERROR syntax error at token (259) in statement:
fjsdlfdsa
## Comment 1675
Date: 2004-08-19 14:56:03 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I guess you didn't read the last paragraph of the checkin
message for revision 1.121 of Mapi.mx. ;-)
The relevant bit is: "There is a function char *
mapi_result_error(MapiHdl hdl) which should be called after
a successful mapi_next_result which returns any errors from
the server for the new result set."
If there is a bug, it's that the documentation is lagging
behind.
## Comment 1676
Date: 2005-10-06 17:17:19 +0200
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-10-06: Claimed by jennie
BugDay_2005-10-06: Done.
BugDay_2005-10-06: NO TEST / INVALID BUG
## Comment 1677
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1012062 at http://sourceforge.net/support/tracker.php?aid=1012062
| mapi_error broken? | https://api.github.com/repos/MonetDB/MonetDB/issues/309/comments | 0 | 2020-11-30T08:28:19Z | 2024-06-28T13:36:26Z | https://github.com/MonetDB/MonetDB/issues/309 | 753,268,491 | 309 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-18 07:10:43 +0200
From: @mlkersten
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2004-09-08 06:57:07 +0200
## Comment 1665
Date: 2004-08-18 19:10:43 +0200
From: @mlkersten
MIL has grown from a simple debugging language into a
scripting language where the parser is intimately aware
of the system state.
To avoid difficult to grasp programming errors and to
ease future use of MIL as a source/target language, a
cleanup of the language is needed. The following
changes are proposed:
- clearly separate function calls from variable
references, i.e. all function calls have a parameter list
- proc definitions always have a parameterlist and
a sequential/parallel block
- assignment construct in a proc definition should be
removed (proc f := return 1; -> proc f(){ return 1;}
- all variables in a proc header are typed
- variables do not change their type, the first
concrete typs freezes it
- no automatic dereference of a variable name to a BAT
in the bbp, e.g. b:= mybat; -> b:=bat("mybat');
- nil constants should be typed where appropriate
- while() S0 and if() S1; else S2. Allow only proper
sequential/parallel blocks
- introduce variables explicitly with 'var'
- Explicitly introduce the batloop variables as part of
the constructuct, e.g. k@batloop() {.... $h....} ->
k@batloop(H,T){ .....H....}
- can we get rid of all template variables? they
introduce a context dependent subspace of the variable
space
well, I certainly have forgotten one or more 'baroque'
syntax extension with minimal use to justify its
existence.
## Comment 1666
Date: 2004-08-18 20:46:54 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Further wishes:
- [~1 const b] use proper functions to indicate the
algebraic actions taken, e.g. concat(1,b) or even
[bun](1,b) to produce buns by glueing a constant with a tail
value.
- similar for the if-then-else constructions
## Comment 1667
Date: 2004-09-08 18:57:07 +0200
From: @peterboncz
Logged In: YES
user_id=591107
The following changes have been made:
- by improving the context-awareness of the parser, the
namespace for variables has been made independent of the
namespace for commands/procs.
Thus, you can have variables and commands with the same
name. All function invocation conventions work, and behave
as expected:
fcn(x,y);
x.fcn(y);
fcn(x);
x.fcn();
x.fcn;
fcn();
fcn;
The last one will *not* work, only if there is a variable
called 'fcn'. In that case (as to be expected), use of the
identifier 'fcn' in MIL referes to the variable.
- by improving the context-awareness of the parser, i := i-1;
now works!!!
That is, from the context, the parser decides whether the - is
part of a following constant, or an infix operator.
- proc definitions now always must have a full signature. This
means that all parameters must be specified. A return type is
obligatory; if there none one must write 'void'. The MEL
syntax is used here; including variable-number of arguments.
e.g.
proc fcn(str a) : void { ls(a); }
proc fcn(any a) : void ls(a);
proc fcn(any::1 a) : any::1 return a
proc fcn(..int...) : int return $($0);
proc fcn(int pos, ..any::1..) : any::1 return $(pos);
note that the ugly := syntax is no longer supported
note that the function body can be any valid MIL statement
(not necessarily a sequential block).
so, we can still type: ls;
- automatic identifier to bat reference conversion is scrapped.
To alleviate sys.mx, I have introducted variables for all
monet_* system bats, so you can refer to those still with an
identifier.
- variables must now be introduced explicitly.
this leaves the following issues not tacked:
- nil constants must be typed ==> this is already the case.
The 'nil' is strongly typed to oid (the most often used
instance of nil). I think leaving that is handy.
- implict batloop variables. Iterators can have paremeters,
therfore we cannot use the proposed syntax. Actually, we
need multi-bat iterators; the current single-bat iterator is not
so useful (you always do a batloop one one bat, and fetches
on other bats -- ugly).
- template variables cannot easily be removed , as we still
support procs with variable number of arguments.
- enforcing sequential blocks (both if- while- and proc-
statements). As a C-guy, I do not see the need.
- variables that do not change type. Maybe a good idea, but
only in conjunction with procs/commands always returning
the same (predictable) type. Doing only the variable-side
would break a lot of stuff now, without good workarounds.
Too much work now.
## Comment 1668
Date: 2004-09-09 10:35:33 +0200
From: @peterboncz
Logged In: YES
user_id=591107
A final change that I forgot oto mention is the assign-over-
operator construct:
i :+= 1;
or more generic
i :OP= ....
meaning:
i := OP(i,...);
in the past was also tolerated in the form
i OP= ...
(without semicolon).
CHANGE: assign-over without ':' is no longer permitted!
## Comment 1669
Date: 2004-09-09 10:42:22 +0200
From: @peterboncz
Logged In: YES
user_id=591107
ONE MORE CHANGE MADE:
accelerator names (hash,index) were removed from the
global namespace. The accbuild() and other commands now
just expect strings, if you specify an accelerator.
These are additional measures to separate the naming
spaces. Only the atom names claim identifiers both from the
command/proc and variables spaces.
## Comment 1670
Date: 2004-09-09 11:58:51 +0200
From: @peterboncz
Logged In: YES
user_id=591107
ORE CONSTRUCT REMOVED:
(1) [b~], you should use b.mark(nil)
(2) [~b], you should use b.reverse.mark(nil).reverse
(3) [b~42], you should use b.project(42)
(4) [42~b], you should use b.reverse.project(42).reverse
(5) [a?b:c], you should use [ifthenelse](a,b,c)
(6) [a?b:], you should use [ifthen](a,b)
(7) [a?:c], you should use [ifelse](a,c)
## Comment 1671
Date: 2005-10-06 17:13:09 +0200
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-10-06: Claimed by jennie
BugDay_2005-10-06: Done.
BugDay_2005-10-06: NO TEST/ changes on MIL syntax
definitions/restrictions
## Comment 1672
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1011596 at http://sourceforge.net/support/tracker.php?aid=1011596
| MIL language cleanup | https://api.github.com/repos/MonetDB/MonetDB/issues/308/comments | 0 | 2020-11-30T08:28:15Z | 2024-06-28T13:36:26Z | https://github.com/MonetDB/MonetDB/issues/308 | 753,268,463 | 308 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-18 05:25:41 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-12-04 09:01:15 +0100
## Comment 1640
Date: 2004-08-18 17:25:41 +0200
From: @grobian
Tonights mTest revealed this bug, but when testing
batching more closely it seems that the server
consistantly crashes on an assertion when the client
gets killed in the middle of a batch transaction with
the server:
monet>Mserver:
/nfs/poseidon/Temp/monet/MonetDB/src/common/stream.mx:1739:
bs_write: Assertion `s->nr < sizeof(s->buf)' failed
Killed
Monet should not crash on evil outside world clients.
(If Microsoft would implement a client, they would let
it simply close the socket if they thought they were
done (see Outlook Express), thus crash Monet every
time. I think this wouldn't surprise them, but I'd say
we should be robust against this kind of torture.)
## Comment 1641
Date: 2004-09-21 17:55:34 +0200
From: @grobian
Logged In: YES
user_id=963970
this is fixed in CVS head.
## Comment 1642
Date: 2005-03-25 15:00:22 +0100
From: @peterboncz
Logged In: YES
user_id=591107
I get this error with the xquery server-side execution.
Mserver
> module(pathfinder); pfstart();
cd /ufs/boncz/xmark
while true; do for i in ??.xq; do MapiClient -lx -T $i | tail -7; echo
$i; done; done
interrupt the above (repeat a couple of times if necessary), and
you get:
Mserver: ../../../src/common/stream.mx:1832: bs_write: Assertion
`s->nr < sizeof(s->buf)' failed.
maybe it is xquery_server specific
(pathfinder/runtime/pathfinder.mx), maybe I should be
somehow "careful" in using stream_read??
problem is that the boehm garbage collector makes it a bit
difficult to debug this.
## Comment 1643
Date: 2005-03-25 15:03:00 +0100
From: @peterboncz
Logged In: YES
user_id=591107
ah, to test the pathfinder stuff, in this case you need to run in
Mserver (only once):
shred_doc("/ufs/boncz/xmark/auctions/auctions10MB.xml",
"auctions10MB.xml");
but I actually doubt it is pathfinder specific
## Comment 1644
Date: 2005-03-25 15:20:19 +0100
From: @grobian
Logged In: YES
user_id=963970
in bs_write, either before the assert should be checked
whether ss->errnr = WRITE_ERROR and act appropriately, or
lateron in the function upon actual write, the s->nr field
should also be reset upon error.
## Comment 1645
Date: 2005-04-13 20:10:20 +0200
From: @grobian
Logged In: YES
user_id=963970
peter, can you check whether this problem is fixed now?
(I don't seem to be able to start pathfinder: Error:
libgc.so.1: cannot open shared object file: No such file or
directory)
## Comment 1646
Date: 2005-04-18 18:06:02 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Hi,
the problem is *not* fixed. tested today with clean checkout and
build (on sn-1):
Monet Database Server V4.7.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>module(pathfinder); pfstart();
MonetDB>threadcnt(1);
MonetDB>shred_doc
("/data/home/boncz/xmark/auctions/auctions100MB.xml","auctions
100MB.xml");
Shredded XML doc("auctions100MB.xml"), total time after
commit=51.127s
MonetDB>Mserver: ../../../src/common/stream.mx:1836: bs_write:
Assertion `s->nr < sizeof(s->buf)' failed.
Aborted
-bash-2.05b$ Mserver
## Comment 1647
Date: 2005-05-03 18:28:09 +0200
From: @peterboncz
Logged In: YES
user_id=591107
any hope of this getting fixed, before the pathfinder release?
## Comment 1648
Date: 2005-05-03 18:43:30 +0200
From: @grobian
Logged In: YES
user_id=963970
I think you should just make your own code correct, as this
seemed not to be fixable the easy way.
## Comment 1649
Date: 2005-05-03 19:02:27 +0200
From: @peterboncz
Logged In: YES
user_id=591107
can you enlighten me what you mean with 'make your own code
correct' ?
rewrite all OS-es on which monet runs in order to abolish the
concept of CTRL-C (SIGINT)? Prohibit by law network failures?
## Comment 1650
Date: 2005-05-03 19:11:03 +0200
From: @grobian
Logged In: YES
user_id=963970
I'm sorry. I didn't mean to sound harsh or attacking at all.
As far as I understand it the assert is raised because you
are trying to write on a dead stream. The only way to avoid
this, is to evaluate the return value of each write. This
value should equal the length you put in, or be bigger than
0. As soon as this is not the case your program should
break out of whatever it is doing, close the stream and
abort or something. Have a look at the Monet4 SQL code, it
has all writes wrapped in a if statement to break out and
avoid the assert.
## Comment 1651
Date: 2005-05-03 19:50:01 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Er is nogal wat code die op GDKout schrijft. MIL commands die
dat doen hebben typisch geen voorkennis van eerder falen van
writes in andere commando invocaties. Dus zou je de error
handling moeten gaan doen middels explicite MIL. Als je dit dus
niet doet, krijg je een crash. Zowieso mag het niet zo zijn dat
ingetypte MIL (behalve dan quit();) leidt tot het termineren van de
server.
In het geval van XQuery, is het MIL command dat het meeste
schrijft print_result(), uit pathfinder/runtime/serialize.mx
Deze code doet veel stream_write() en stream_printf(); zonder
het resultaat te checken (overigens is dit niet "mijn code", maar
die van Jan Flokstra).
Ik vind een assert bij schrijven op een stream die een fout heeft
onwenselijk, omdat een simpele uitweg bestaat: -1 terug geven.
De assert die er nu inzit kan tijdelijk gedaan worden als doel om
evt bugs in de stream code op te sporen. Dwz als we zouden
denken dat de condities->nr < sizeof(s->buf) optreedt omdat er
iets mis zit in stream zelf.
Als de reden extern is, dwz in het gebruik van streams, dwz
writen na een eerdere failure, vind ik het correct om
catastrofisch te falen (voor een eindgebruiker is er geen verschil
tussen SEGV en assert).
Positief nieuws nu...
Door het niet meer gebruiken van Boehm, kan ik nu debuggen,
en heb dan ook deze trace weten te produceren (door tijdens
xquery evaluatie op ctrl-c te drukken in het MapiClient window):
(gdb) bt
0 0x000000365ee2dc45 in raise () from /lib64/tls/libc.so.6
1 0x000000365ee2f6ce in abort () from /lib64/tls/libc.so.6
2 0x000000365ee27862 in __assert_fail ()
from /lib64/tls/libc.so.6
3 0x0000002a964924f1 in bs_write (ss=0x2a9fcdbf60,
buf=0x2aaf8cbd28, elmsize=116, cnt=1) at stream.mx:1836
4 0x0000002a96490492 in stream_write (s=0x2a9fcdbf60,
buf=0x2aaf8cbd28, elmsize=116, cnt=1) at stream.mx:412
5 0x0000002a95aa016b in print_format (
format=0x2aadc94c88 "\nTrans 79.449 msec\nFetch %
7d.000 msec\nShred % 7d.000 msec\nQuery % 7d.000
msec\nPrint % 7d.000 msec\n") at builtin.mx:1275
6 0x0000002a95a9b836 in print_format_unpack1699905556
(argc=6, argv=0x2a9fcdaf68) at builtin.glue.c:420
7 0x0000002a95568eae in interpret (stk=617,
lt=0x2aaec30608, res=0x2a9fc31e18) at
monet_interpreter.mx:1148
8 0x0000002a95570b3d in interpret_seqblock (stk=617,
lt=0x2aae0543d8, res=0x2a9fc31e18, scope=1)
at monet_interpreter.mx:1769
9 0x0000002a95567339 in interpret (stk=3, lt=0x2aae005d48,
res=0x2a9fc31e18) at monet_interpreter.mx:756
10 0x0000002a95570b3d in interpret_seqblock (stk=3,
lt=0x2aaec30ad8, res=0x2a9fc31e18, scope=0)
at monet_interpreter.mx:1769
11 0x0000002a95567339 in interpret (stk=3, lt=0x2aaec30ad8,
res=0x2a9fc31e18) at monet_interpreter.mx:756
12 0x0000002a95565bdd in interpret_str (stk=0,
buf=0x2aaffcb010 "\n\n MAIN MIL QUERY\n{var ws :=
create_ws();\nvar loop000 := bat(void,oid,1).seqbase(0@0).insert
(0@0, 1@0).access(BAT_READ);\nvar vu_fid;\nvar vu_vid;\nvar
inner000 ;\nvar outer000 ;\nvar v_vid000 := bat(void"...,
res=0x2a9fc31e18) at monet_interpreter.mx:246
13 0x0000002a955639c0 in monet_eval (
mil_script=0x2aaffcb010 "\n\n MAIN MIL QUERY\n{var ws :=
create_ws();\nvar loop000 := bat(void,oid,1).seqbase(0@0).insert
(0@0, 1@0).access(BAT_READ);\nvar vu_fid;\nvar vu_vid;\nvar
inner000 ;\nvar outer000 ;\nvar v_vid000 := bat(void"...,
ret_type=0x403ff4a4) at monet.mx:592
14 0x0000002a95563bd7 in monet_exec (
mil_script=0x2aaffcb010 "\n\n MAIN MIL QUERY\n{var ws :=
create_ws();\nvar loop000 := bat(void,oid,1).seqbase(0@0).insert
(0@0, 1@0).access(BAT_READ);\nvar vu_fid;\nvar vu_vid;\nvar
inner000 ;\nvar outer000 ;\nvar v_vid000 := bat(void"...) at
monet.mx:627
15 0x0000002a9f01c3f6 in CMDxquery
(mode=0x2aadcc9f38 "timing-dm-mapi",
xquery=0x2aadcc9f47 "let $auction := doc
('auctions100MB.xml')\nfor $b in
$auction/site/open_auctions/open_auction\nwhere exactly-one
($b/bidder[1]/increase/text()) * 2 <= $b/bidder[last()]/increase/text
()\nreturn <increas"...)
at pathfinder.mx:2383
16 0x0000002a9f01ca9a in CMDxquery_server (stk=4,
lt=0x2aae0055b8, res=0x403ff7b0) at pathfinder.mx:2526
17 0x0000002a95567bcf in interpret (stk=4, lt=0x2aae0055b8,
res=0x403ff7b0) at monet_interpreter.mx:846
18 0x0000002a955833b4 in handleRequest (t=0x2a96472128,
q=0x1ce47d8, res=0x403ff7b0) at monet_queue.mx:534
19 0x0000002a955837ee in doRequest (t=0x2a96472128,
preference=0x0) at monet_queue.mx:560
20 0x0000002a955cffc8 in monetInterpreter
(status=0x7fbfffef54) at monet_process.mx:112
21 0x000000365f9057fb in start_thread ()
from /lib64/tls/libpthread.so.0
22 0x000000365eebab03 in thread_start ()
from /lib64/tls/libc.so.6
We zien hier dat het tarcing MIL statement in de genegeneerde
vertaling van XQuery naar MIL (print_format) de boosdoender is.
Dus zlefs als Jan Flokstra al zijn print_result code zou
aanpassen, zou dat niet genoeg zijn. Het is heel moeilijk om het
executerende MIl programma te laten weten dat de connectie
waaronder het executeerd eruit ligt.
Als iemand oplossingen heeft, hoor ik het graag, mara mijn
suggestie is om de assert om te toveren in een conditional die
stream_write -1 laat retourneren.
## Comment 1652
Date: 2005-05-03 19:56:18 +0200
From: @grobian
Logged In: YES
user_id=963970
Hier ligt een diepgaande discussie met Niels aan ten
grondslag. He's the man to fix it.
## Comment 1653
Date: 2005-05-03 21:45:08 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
English, please.
## Comment 1654
Date: 2005-05-03 21:52:53 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Asserts are a debugging aid. It is The Right Thing To Do to
check for errors on *every* invocation of a function that
can fail. This includes stream_write and friends. If an
error occurs, deal with it. It's as simple as that.
Having said that, these asserts are by their very nature
optional. Compile with NDEBUG defined (as we do for
released binaries), then the assert is compiled out and so
will not terminate the application.
## Comment 1655
Date: 2005-05-03 22:07:47 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Hi Sjoerd. I don't think anybody (me in particular)
questions the usefulness of assert(). The question I am
raising is *which* conditions are the ones to cover with
asserts. For some condition's you may want to simply give an
error message to the user, i.e. with GDKerror.
I tried to come with arguments why invoking a write on a
stream where previously an error was returned should not be
an assert condition. If you do not agree, try to come with
arguments for that; rather than trying to debate the general
usefulness for asserts.
Your suggestions to compile without asserts is not an
option, in the current state of the code. There is a class
of very serious conditions where execution must stop (for
instance those that if execution continues, lead to a
corrupted persistent database). Many of those are currently
checked with asserts and you would not want to disable those.
Asserts are quite useful in that case as they provide good
hints that users can include in bug reports.
In your quest for alternative suggestions (to disabling this
particular assert) I would like you to focus on those that
do make the current behavior of the server crashing when a
client is terminated disappear.
## Comment 1656
Date: 2005-05-03 22:28:50 +0200
From: @grobian
Logged In: YES
user_id=963970
I think Niels did already check-in a fix a few posts ago.
See the repective check-in message.
## Comment 1657
Date: 2005-05-04 12:35:43 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Er is nogal wat code die op GDKout schrijft. MIL commands die
dat doen hebben typisch geen voorkennis van eerder falen van
writes in andere commando invocaties. Dus zou je de error
handling moeten gaan doen middels explicite MIL. Als je dit dus
niet doet, krijg je een crash. Zowieso mag het niet zo zijn dat
ingetypte MIL (behalve dan quit();) leidt tot het termineren van de
server.
In het geval van XQuery, is het MIL command dat het meeste
schrijft print_result(), uit pathfinder/runtime/serialize.mx
Deze code doet veel stream_write() en stream_printf(); zonder
het resultaat te checken (overigens is dit niet "mijn code", maar
die van Jan Flokstra).
Ik vind een assert bij schrijven op een stream die een fout heeft
onwenselijk, omdat een simpele uitweg bestaat: -1 terug geven.
De assert die er nu inzit kan tijdelijk gedaan worden als doel om
evt bugs in de stream code op te sporen. Dwz als we zouden
denken dat de condities->nr < sizeof(s->buf) optreedt omdat er
iets mis zit in stream zelf.
Als de reden extern is, dwz in het gebruik van streams, dwz
writen na een eerdere failure, vind ik het correct om
catastrofisch te falen (voor een eindgebruiker is er geen verschil
tussen SEGV en assert).
Positief nieuws nu...
Door het niet meer gebruiken van Boehm, kan ik nu debuggen,
en heb dan ook deze trace weten te produceren (door tijdens
xquery evaluatie op ctrl-c te drukken in het MapiClient window):
(gdb) bt
0 0x000000365ee2dc45 in raise () from /lib64/tls/libc.so.6
1 0x000000365ee2f6ce in abort () from /lib64/tls/libc.so.6
2 0x000000365ee27862 in __assert_fail ()
from /lib64/tls/libc.so.6
3 0x0000002a964924f1 in bs_write (ss=0x2a9fcdbf60,
buf=0x2aaf8cbd28, elmsize=116, cnt=1) at stream.mx:1836
4 0x0000002a96490492 in stream_write (s=0x2a9fcdbf60,
buf=0x2aaf8cbd28, elmsize=116, cnt=1) at stream.mx:412
5 0x0000002a95aa016b in print_format (
format=0x2aadc94c88 "\nTrans 79.449 msec\nFetch %
7d.000 msec\nShred % 7d.000 msec\nQuery % 7d.000
msec\nPrint % 7d.000 msec\n") at builtin.mx:1275
6 0x0000002a95a9b836 in print_format_unpack1699905556
(argc=6, argv=0x2a9fcdaf68) at builtin.glue.c:420
7 0x0000002a95568eae in interpret (stk=617,
lt=0x2aaec30608, res=0x2a9fc31e18) at
monet_interpreter.mx:1148
8 0x0000002a95570b3d in interpret_seqblock (stk=617,
lt=0x2aae0543d8, res=0x2a9fc31e18, scope=1)
at monet_interpreter.mx:1769
9 0x0000002a95567339 in interpret (stk=3, lt=0x2aae005d48,
res=0x2a9fc31e18) at monet_interpreter.mx:756
10 0x0000002a95570b3d in interpret_seqblock (stk=3,
lt=0x2aaec30ad8, res=0x2a9fc31e18, scope=0)
at monet_interpreter.mx:1769
11 0x0000002a95567339 in interpret (stk=3, lt=0x2aaec30ad8,
res=0x2a9fc31e18) at monet_interpreter.mx:756
12 0x0000002a95565bdd in interpret_str (stk=0,
buf=0x2aaffcb010 "\n\n MAIN MIL QUERY\n{var ws :=
create_ws();\nvar loop000 := bat(void,oid,1).seqbase(0@0).insert
(0@0, 1@0).access(BAT_READ);\nvar vu_fid;\nvar vu_vid;\nvar
inner000 ;\nvar outer000 ;\nvar v_vid000 := bat(void"...,
res=0x2a9fc31e18) at monet_interpreter.mx:246
13 0x0000002a955639c0 in monet_eval (
mil_script=0x2aaffcb010 "\n\n MAIN MIL QUERY\n{var ws :=
create_ws();\nvar loop000 := bat(void,oid,1).seqbase(0@0).insert
(0@0, 1@0).access(BAT_READ);\nvar vu_fid;\nvar vu_vid;\nvar
inner000 ;\nvar outer000 ;\nvar v_vid000 := bat(void"...,
ret_type=0x403ff4a4) at monet.mx:592
14 0x0000002a95563bd7 in monet_exec (
mil_script=0x2aaffcb010 "\n\n MAIN MIL QUERY\n{var ws :=
create_ws();\nvar loop000 := bat(void,oid,1).seqbase(0@0).insert
(0@0, 1@0).access(BAT_READ);\nvar vu_fid;\nvar vu_vid;\nvar
inner000 ;\nvar outer000 ;\nvar v_vid000 := bat(void"...) at
monet.mx:627
15 0x0000002a9f01c3f6 in CMDxquery
(mode=0x2aadcc9f38 "timing-dm-mapi",
xquery=0x2aadcc9f47 "let $auction := doc
('auctions100MB.xml')\nfor $b in
$auction/site/open_auctions/open_auction\nwhere exactly-one
($b/bidder[1]/increase/text()) * 2 <= $b/bidder[last()]/increase/text
()\nreturn <increas"...)
at pathfinder.mx:2383
16 0x0000002a9f01ca9a in CMDxquery_server (stk=4,
lt=0x2aae0055b8, res=0x403ff7b0) at pathfinder.mx:2526
17 0x0000002a95567bcf in interpret (stk=4, lt=0x2aae0055b8,
res=0x403ff7b0) at monet_interpreter.mx:846
18 0x0000002a955833b4 in handleRequest (t=0x2a96472128,
q=0x1ce47d8, res=0x403ff7b0) at monet_queue.mx:534
19 0x0000002a955837ee in doRequest (t=0x2a96472128,
preference=0x0) at monet_queue.mx:560
20 0x0000002a955cffc8 in monetInterpreter
(status=0x7fbfffef54) at monet_process.mx:112
21 0x000000365f9057fb in start_thread ()
from /lib64/tls/libpthread.so.0
22 0x000000365eebab03 in thread_start ()
from /lib64/tls/libc.so.6
We zien hier dat het tarcing MIL statement in de genegeneerde
vertaling van XQuery naar MIL (print_format) de boosdoender is.
Dus zlefs als Jan Flokstra al zijn print_result code zou
aanpassen, zou dat niet genoeg zijn. Het is heel moeilijk om het
executerende MIl programma te laten weten dat de connectie
waaronder het executeerd eruit ligt.
Als iemand oplossingen heeft, hoor ik het graag, mara mijn
suggestie is om de assert om te toveren in een conditional die
stream_write -1 laat retourneren.
## Comment 1658
Date: 2005-05-04 12:47:19 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Sorry guys! Hit submit accidentally, apparently. Close this again.
## Comment 1659
Date: 2005-11-06 11:04:23 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-10-06: "left-overs" are now marked as "pending"
## Comment 1660
Date: 2005-11-21 04:20:20 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
## Comment 1661
Date: 2006-11-22 04:20:03 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 1662
Date: 2006-11-29 10:05:36 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
over-ruling "sf-robot":
re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet.
User (submitter) & developer (assignee),
please check, again.
## Comment 1663
Date: 2006-12-04 21:01:15 +0100
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
The steram_write function returns directly if there was a previous error. So the assert simply checks
if the block streams information is still consistent. Lets close this bug as writing an script which tests this consistently is hard (if not impossible).
## Comment 1664
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1011514 at http://sourceforge.net/support/tracker.php?aid=1011514
| Stream: bs_write assertion on client kill | https://api.github.com/repos/MonetDB/MonetDB/issues/307/comments | 0 | 2020-11-30T08:28:12Z | 2024-06-27T10:58:11Z | https://github.com/MonetDB/MonetDB/issues/307 | 753,268,427 | 307 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-18 03:13:49 +0200
From: Jan Rittinger <<jan.rittinger>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2007-11-30 04:20:04 +0100
## Comment 1630
Date: 2004-08-18 15:13:49 +0200
From: Jan Rittinger <<jan.rittinger>>
Produced a script, which evaluates an xmark query three times. In the
second loop a segmentation fault appears.
Added script, which can be run using the database in the path
/ufs/rittinge/work/MonetDB/Linux/var/MonetDB/dbfarm/demo/
(its writable for the group)
## Comment 1631
Date: 2004-08-18 15:41:54 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
without line 1507: var sorting := CTgroup(iter).CTgroup(item).CTgroup(kind);
it works well
and the attempt getting it writable for the group didn't work out - my database
randomly deleted tables afterwards...
## Comment 1632
Date: 2004-08-18 15:44:02 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
sorry for commenting faster than testing - with a larger table Mserver still
crashes
## Comment 1633
Date: 2004-09-06 17:36:17 +0200
From: @peterboncz
Logged In: YES
user_id=591107
this was fixed two weeks ago
## Comment 1634
Date: 2005-11-06 11:03:56 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-10-06: "left-overs" are now marked as "pending"
## Comment 1635
Date: 2005-11-21 04:20:20 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
## Comment 1636
Date: 2006-11-22 04:20:03 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 1637
Date: 2006-11-29 10:05:31 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
over-ruling "sf-robot":
re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet.
User (submitter) & developer (assignee),
please check, again.
## Comment 1638
Date: 2007-11-30 04:20:04 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 1639
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1011424 at http://sourceforge.net/support/tracker.php?aid=1011424
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| Segmentation fault in second run | https://api.github.com/repos/MonetDB/MonetDB/issues/306/comments | 0 | 2020-11-30T08:28:08Z | 2024-06-28T13:36:25Z | https://github.com/MonetDB/MonetDB/issues/306 | 753,268,392 | 306 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-18 01:39:32 +0200
From: @swingbit
To: @mlkersten
Version: -- development
Last updated: 2004-09-12 02:07:30 +0200
## Comment 1626
Date: 2004-08-18 13:39:32 +0200
From: @swingbit
In the Mil documentation, section 3.7 about pump
operator, there is paragraph about aggrX3 operators saying:
In the tertiary pump, the first (left) parameter of the
binary pump is split by column into two BATs with a
synced void head columns, where the tail of the first
contains the original HEAD column, and the tail of the
second the original TAIL column.
It is actually the other way around:
...where the tail of the first contains the original
TAIL column, and the tail of the second the original
HEAD column.
## Comment 1627
Date: 2004-09-12 14:07:30 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Changed the text accordingly
## Comment 1628
Date: 2005-10-06 16:27:36 +0200
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-10-06: Claimed by jennie
BugDay_2005-10-06: Done.
BugDay_2005-10-06: NO TEST / DOCUMENTATION
## Comment 1629
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1011363 at http://sourceforge.net/support/tracker.php?aid=1011363
| [documentation] error in Mil docum. about aggrX3 | https://api.github.com/repos/MonetDB/MonetDB/issues/305/comments | 0 | 2020-11-30T08:28:06Z | 2024-06-27T10:58:09Z | https://github.com/MonetDB/MonetDB/issues/305 | 753,268,353 | 305 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-18 10:29:56 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2004-08-18 12:55:09 +0200
## Comment 1622
Date: 2004-08-18 10:29:56 +0200
From: @drstmane
Many SQL test now fail with
"!current transaction is aborted (please ROLLBACK)"
See TestWeb for details.
## Comment 1623
Date: 2004-08-18 12:55:09 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed.
(Hmm, maybe I should let the tests run their course before
closing this...)
## Comment 1624
Date: 2005-10-06 16:21:58 +0200
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-10-06: Claimed by jennie
BugDay_2005-10-06: Done
NO TEST / COMPILATION
Note:
This is mass-bug, in which a large number of SQL tests fail.
It is very likely a compilation problem, and it's anyway not
possible to add test script for such kind of bug.
## Comment 1625
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1011285 at http://sourceforge.net/support/tracker.php?aid=1011285
| SQL tests fail: "!current transaction is aborted (ROLLBACK)" | https://api.github.com/repos/MonetDB/MonetDB/issues/304/comments | 0 | 2020-11-30T08:28:02Z | 2024-06-27T10:58:08Z | https://github.com/MonetDB/MonetDB/issues/304 | 753,268,321 | 304 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-17 05:06:39 +0200
From: @arjan
To: @sjoerdmullender
Version: -- development
Last updated: 2007-11-30 04:20:04 +0100
## Comment 1614
Date: 2004-08-17 17:06:39 +0200
From: @arjan
It would be nice to have the field count available even
if no protocol headers are given. Currently it returns
0, for example at the statement:
mapi_query("print(1);");
So, practically, MIL support through the mapi library
is currently broken.
## Comment 1615
Date: 2004-08-19 11:09:58 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I'd call this a bug, and it is fixed.
## Comment 1616
Date: 2005-11-06 11:03:34 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-10-06: "left-overs" are now marked as "pending"
## Comment 1617
Date: 2005-11-21 04:20:20 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
## Comment 1618
Date: 2006-11-22 04:20:03 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 1619
Date: 2006-11-29 10:05:27 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
over-ruling "sf-robot":
re-set to "Pending" since adding a proper test has neither been done nor finally been discarded, yet.
User (submitter) & developer (assignee),
please check, again.
## Comment 1620
Date: 2007-11-30 04:20:04 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 1621
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1010787 at http://sourceforge.net/support/tracker.php?aid=1010787
| Make mapi_get_field_count() without headers | https://api.github.com/repos/MonetDB/MonetDB/issues/303/comments | 0 | 2020-11-30T08:27:58Z | 2024-06-27T10:58:07Z | https://github.com/MonetDB/MonetDB/issues/303 | 753,268,282 | 303 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-17 03:44:33 +0200
From: @swingbit
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-08-17 11:39:35 +0200
## Comment 1608
Date: 2004-08-17 15:44:33 +0200
From: @swingbit
The result of this is funny:
b := new(void, int).seqbase(0@0);
b.insert(nil,1).insert(nil, 2).insert(nil, 3);
11 is the type_identifier of 'str'
[cast](b, 11).print;
## Comment 1609
Date: 2004-08-17 16:05:29 +0200
From: @drstmane
Logged In: YES
user_id=572415
I'm tempted to close this report, because "fun" can never be
a "bug", and will hopefully never be "fixed" (i.e., changed
into the opposite ... ;-)
Seriously, again:
Could you please add the "funny" result for those who are
too lazy to try it themselves?
Thanks!
## Comment 1610
Date: 2004-08-17 16:12:48 +0200
From: @swingbit
Logged In: YES
user_id=883451
Remember YOU asked......
monet>b := new(void, int).seqbase(0@0);
b.insert(nil,1).insert(nil, 2).insert(nil, 3);
11 is the int type_identifier of 'str'
[cast](b, 11).print;
b := new(void, int).seqbase(0@0);
monet>b.insert(nil,1).insert(nil, 2).insert(nil, 3);
monet>
monet> 11 is the int type_identifier of 'str'
monet>[cast](b, 11).print;
-----------------------------------------
h tmp_68 name
oid str type
-----------------------------------------
[ 10038@0, "any" ]
[ 10038@0, "void" ]
[ 10039@0, "BAT[any::1,any]" ]
[ 10039@0, "*BAT[any::1,any]" ]
[ 10039@0, "void" ]
[ 10040@0, "int" ]
[ 10040@0, "BAT[any::1,any]" ]
[ 10040@0, "*BAT[any::1,any]" ]
[ 10040@0, "void" ]
[ 10041@0, "BAT[any::1,any]" ]
[ 10041@0, "*BAT[any::1,any]" ]
[ 10041@0, "void" ]
[ 10042@0, "int" ]
[ 10042@0, "BAT[any::1,any]" ]
[ 10042@0, "*BAT[any::1,any]" ]
[ 10042@0, "void" ]
[ 10043@0, "BAT[any,BAT]" ]
[ 10043@0, "void" ]
[ 10044@0, "str" ]
[ 10044@0, "*any" ]
[ 10044@0, "void" ]
[ 10045@0, "str" ]
[ 10045@0, "*any" ]
[ 10045@0, "str" ]
[ 10048@0, "any" ]
[ 10048@0, "bit" ]
[ 10049@0, "chr" ]
[ 10049@0, "bit" ]
[ 10050@0, "bit" ]
[ 10050@0, "bit" ]
[ 10051@0, "sht" ]
[ 10051@0, "bit" ]
[ 10052@0, "int" ]
[ 10052@0, "bit" ]
[ 10053@0, "oid" ]
[ 10053@0, "bit" ]
[ 10054@0, "flt" ]
[ 10054@0, "bit" ]
[ 10055@0, "lng" ]
[ 10055@0, "bit" ]
[ 10056@0, "dbl" ]
[ 10056@0, "bit" ]
[ 10057@0, "str" ]
[ 10057@0, "bit" ]
[ 10058@0, "any::1" ]
[ 10058@0, "any::1" ]
[ 10058@0, "bit" ]
[ 10059@0, "any::1" ]
[ 10059@0, "any::1" ]
[ 10059@0, "bit" ]
[ 10060@0, "any::1" ]
[ 10060@0, "any::1" ]
[ 10060@0, "bit" ]
[ 10061@0, "any::1" ]
[ 10061@0, "any::1" ]
[ 10061@0, "bit" ]
[ 10062@0, "any::1" ]
[ 10062@0, "any::1" ]
[ 10062@0, "bit" ]
[ 10063@0, "any::1" ]
[ 10063@0, "any::1" ]
[ 10063@0, "bit" ]
[ 10064@0, "any::1" ]
[ 10064@0, "any::1" ]
[ 10064@0, "any::1" ]
[ 10064@0, "bit" ]
[ 10065@0, "bit" ]
[ 10065@0, "bit" ]
[ 10065@0, "bit" ]
[ 10066@0, "bit" ]
[ 10066@0, "bit" ]
[ 10066@0, "bit" ]
[ 10067@0, "chr" ]
[ 10067@0, "chr" ]
[ 10067@0, "bit" ]
[ 10068@0, "chr" ]
[ 10068@0, "chr" ]
[ 10068@0, "bit" ]
[ 10069@0, "chr" ]
[ 10069@0, "chr" ]
[ 10069@0, "bit" ]
[ 10070@0, "chr" ]
[ 10070@0, "chr" ]
[ 10070@0, "bit" ]
[ 10071@0, "chr" ]
[ 10071@0, "chr" ]
[ 10071@0, "bit" ]
[ 10072@0, "chr" ]
[ 10072@0, "chr" ]
[ 10072@0, "bit" ]
[ 10073@0, "chr" ]
[ 10073@0, "chr" ]
[ 10073@0, "chr" ]
[ 10073@0, "bit" ]
[ 10074@0, "sht" ]
[ 10074@0, "sht" ]
[ 10074@0, "bit" ]
[ 10075@0, "sht" ]
[ 10075@0, "sht" ]
[ 10075@0, "bit" ]
[ 10076@0, "sht" ]
[ 10076@0, "sht" ]
[ 10076@0, "bit" ]
[ 10077@0, "sht" ]
[ 10077@0, "sht" ]
[ 10077@0, "bit" ]
[ 10078@0, "sht" ]
[ 10078@0, "sht" ]
[ 10078@0, "bit" ]
[ 10079@0, "sht" ]
[ 10079@0, "sht" ]
[ 10079@0, "bit" ]
[ 10080@0, "sht" ]
[ 10080@0, "sht" ]
[ 10080@0, "sht" ]
[ 10080@0, "bit" ]
[ 10081@0, "int" ]
[ 10081@0, "int" ]
[ 10081@0, "bit" ]
[ 10082@0, "int" ]
[ 10082@0, "int" ]
[ 10082@0, "bit" ]
[ 10083@0, "int" ]
[ 10083@0, "int" ]
[ 10083@0, "bit" ]
[ 10084@0, "int" ]
[ 10084@0, "int" ]
[ 10084@0, "bit" ]
[ 10085@0, "int" ]
[ 10085@0, "int" ]
[ 10085@0, "bit" ]
[ 10086@0, "int" ]
[ 10086@0, "int" ]
[ 10086@0, "bit" ]
[ 10087@0, "int" ]
[ 10087@0, "int" ]
[ 10087@0, "int" ]
[ 10087@0, "bit" ]
[ 10088@0, "oid" ]
[ 10088@0, "oid" ]
[ 10088@0, "bit" ]
[ 10089@0, "oid" ]
[ 10089@0, "oid" ]
[ 10089@0, "bit" ]
[ 10090@0, "oid" ]
[ 10090@0, "oid" ]
[ 10090@0, "bit" ]
[ 10091@0, "oid" ]
[ 10091@0, "oid" ]
[ 10091@0, "bit" ]
[ 10092@0, "oid" ]
[ 10092@0, "oid" ]
[ 10092@0, "bit" ]
[ 10093@0, "oid" ]
[ 10093@0, "oid" ]
[ 10093@0, "bit" ]
[ 10094@0, "oid" ]
[ 10094@0, "oid" ]
[ 10094@0, "oid" ]
[ 10094@0, "bit" ]
[ 10095@0, "flt" ]
[ 10095@0, "flt" ]
[ 10095@0, "bit" ]
[ 10096@0, "flt" ]
[ 10096@0, "flt" ]
[ 10096@0, "bit" ]
[ 10097@0, "flt" ]
[ 10097@0, "flt" ]
[ 10097@0, "bit" ]
[ 10098@0, "flt" ]
[ 10098@0, "flt" ]
[ 10098@0, "bit" ]
[ 10099@0, "flt" ]
[ 10099@0, "flt" ]
[ 10099@0, "bit" ]
[ 10100@0, "flt" ]
[ 10100@0, "flt" ]
[ 10100@0, "bit" ]
[ 10101@0, "flt" ]
[ 10101@0, "flt" ]
[ 10101@0, "flt" ]
[ 10101@0, "bit" ]
[ 10102@0, "dbl" ]
[ 10102@0, "dbl" ]
[ 10102@0, "bit" ]
[ 10103@0, "dbl" ]
[ 10103@0, "dbl" ]
[ 10103@0, "bit" ]
[ 10104@0, "dbl" ]
[ 10104@0, "dbl" ]
[ 10104@0, "bit" ]
[ 10105@0, "dbl" ]
[ 10105@0, "dbl" ]
[ 10105@0, "bit" ]
[ 10106@0, "dbl" ]
[ 10106@0, "dbl" ]
[ 10106@0, "bit" ]
[ 10107@0, "dbl" ]
[ 10107@0, "dbl" ]
[ 10107@0, "bit" ]
[ 10108@0, "dbl" ]
[ 10108@0, "dbl" ]
[ 10108@0, "dbl" ]
[ 10108@0, "bit" ]
[ 10109@0, "lng" ]
[ 10109@0, "lng" ]
[ 10109@0, "bit" ]
[ 10110@0, "lng" ]
[ 10110@0, "lng" ]
[ 10110@0, "bit" ]
[ 10111@0, "lng" ]
[ 10111@0, "lng" ]
[ 10111@0, "bit" ]
[ 10112@0, "lng" ]
[ 10112@0, "lng" ]
[ 10112@0, "bit" ]
[ 10113@0, "lng" ]
[ 10113@0, "lng" ]
[ 10113@0, "bit" ]
[ 10114@0, "lng" ]
[ 10114@0, "lng" ]
[ 10114@0, "bit" ]
[ 10115@0, "lng" ]
[ 10115@0, "lng" ]
[ 10115@0, "lng" ]
[ 10115@0, "bit" ]
[ 10116@0, "str" ]
[ 10116@0, "str" ]
[ 10116@0, "bit" ]
[ 10117@0, "str" ]
[ 10117@0, "str" ]
[ 10117@0, "bit" ]
[ 10118@0, "str" ]
[ 10118@0, "str" ]
[ 10118@0, "bit" ]
[ 10119@0, "str" ]
[ 10119@0, "str" ]
[ 10119@0, "bit" ]
[ 10120@0, "str" ]
[ 10120@0, "str" ]
[ 10120@0, "bit" ]
[ 10121@0, "str" ]
[ 10121@0, "str" ]
[ 10121@0, "bit" ]
[ 10122@0, "str" ]
[ 10122@0, "str" ]
[ 10122@0, "str" ]
[ 10122@0, "bit" ]
[ 10123@0, "chr" ]
[ 10123@0, "int" ]
[ 10123@0, "int" ]
[ 10124@0, "sht" ]
[ 10124@0, "sht" ]
[ 10124@0, "sht" ]
[ 10125@0, "sht" ]
[ 10125@0, "int" ]
[ 10125@0, "int" ]
[ 10126@0, "int" ]
[ 10126@0, "int" ]
[ 10126@0, "int" ]
[ 10127@0, "lng" ]
[ 10127@0, "lng" ]
[ 10127@0, "lng" ]
[ 10128@0, "lng" ]
[ 10128@0, "int" ]
[ 10128@0, "int" ]
[ 10129@0, "int" ]
[ 10129@0, "chr" ]
[ 10129@0, "chr" ]
[ 10130@0, "int" ]
[ 10130@0, "sht" ]
[ 10130@0, "sht" ]
[ 10131@0, "chr" ]
[ 10131@0, "chr" ]
[ 10131@0, "chr" ]
[ 10132@0, "chr" ]
[ 10132@0, "chr" ]
[ 10132@0, "chr" ]
[ 10133@0, "chr" ]
[ 10133@0, "chr" ]
[ 10133@0, "chr" ]
[ 10134@0, "chr" ]
[ 10134@0, "chr" ]
[ 10134@0, "chr" ]
[ 10135@0, "chr" ]
[ 10135@0, "sht" ]
[ 10135@0, "sht" ]
[ 10136@0, "chr" ]
[ 10136@0, "sht" ]
[ 10136@0, "sht" ]
[ 10137@0, "chr" ]
[ 10137@0, "sht" ]
[ 10137@0, "sht" ]
[ 10138@0, "chr" ]
[ 10138@0, "sht" ]
[ 10138@0, "sht" ]
[ 10139@0, "chr" ]
[ 10139@0, "int" ]
[ 10139@0, "int" ]
[ 10140@0, "chr" ]
[ 10140@0, "int" ]
[ 10140@0, "int" ]
[ 10141@0, "chr" ]
[ 10141@0, "int" ]
[ 10141@0, "int" ]
[ 10142@0, "chr" ]
[ 10142@0, "int" ]
[ 10142@0, "int" ]
[ 10143@0, "chr" ]
[ 10143@0, "lng" ]
[ 10143@0, "lng" ]
[ 10144@0, "chr" ]
[ 10144@0, "lng" ]
[ 10144@0, "lng" ]
[ 10145@0, "chr" ]
[ 10145@0, "lng" ]
[ 10145@0, "lng" ]
[ 10146@0, "chr" ]
[ 10146@0, "lng" ]
[ 10146@0, "lng" ]
[ 10147@0, "chr" ]
[ 10147@0, "flt" ]
[ 10147@0, "flt" ]
[ 10148@0, "chr" ]
[ 10148@0, "flt" ]
[ 10148@0, "flt" ]
[ 10149@0, "chr" ]
[ 10149@0, "flt" ]
[ 10149@0, "flt" ]
[ 10150@0, "chr" ]
[ 10150@0, "flt" ]
[ 10150@0, "flt" ]
[ 10151@0, "chr" ]
[ 10151@0, "dbl" ]
[ 10151@0, "dbl" ]
[ 10152@0, "chr" ]
[ 10152@0, "dbl" ]
[ 10152@0, "dbl" ]
[ 10153@0, "chr" ]
[ 10153@0, "dbl" ]
[ 10153@0, "dbl" ]
[ 10154@0, "chr" ]
[ 10154@0, "dbl" ]
[ 10154@0, "dbl" ]
[ 10155@0, "sht" ]
[ 10155@0, "chr" ]
[ 10155@0, "sht" ]
[ 10156@0, "sht" ]
[ 10156@0, "chr" ]
[ 10156@0, "sht" ]
[ 10157@0, "sht" ]
[ 10157@0, "chr" ]
[ 10157@0, "sht" ]
[ 10158@0, "sht" ]
[ 10158@0, "chr" ]
[ 10158@0, "sht" ]
[ 10159@0, "sht" ]
[ 10159@0, "sht" ]
[ 10159@0, "sht" ]
[ 10160@0, "sht" ]
[ 10160@0, "sht" ]
[ 10160@0, "sht" ]
[ 10161@0, "sht" ]
[ 10161@0, "sht" ]
[ 10161@0, "sht" ]
[ 10162@0, "sht" ]
[ 10162@0, "sht" ]
[ 10162@0, "sht" ]
[ 10163@0, "sht" ]
[ 10163@0, "int" ]
[ 10163@0, "int" ]
[ 10164@0, "sht" ]
[ 10164@0, "int" ]
[ 10164@0, "int" ]
[ 10165@0, "sht" ]
[ 10165@0, "int" ]
[ 10165@0, "int" ]
[ 10166@0, "sht" ]
[ 10166@0, "int" ]
[ 10166@0, "int" ]
[ 10167@0, "sht" ]
[ 10167@0, "lng" ]
[ 10167@0, "lng" ]
[ 10168@0, "sht" ]
[ 10168@0, "lng" ]
[ 10168@0, "lng" ]
[ 10169@0, "sht" ]
[ 10169@0, "lng" ]
[ 10169@0, "lng" ]
[ 10170@0, "sht" ]
[ 10170@0, "lng" ]
[ 10170@0, "lng" ]
[ 10171@0, "sht" ]
[ 10171@0, "flt" ]
[ 10171@0, "flt" ]
[ 10172@0, "sht" ]
[ 10172@0, "flt" ]
[ 10172@0, "flt" ]
[ 10173@0, "sht" ]
[ 10173@0, "flt" ]
[ 10173@0, "flt" ]
[ 10174@0, "sht" ]
[ 10174@0, "flt" ]
[ 10174@0, "flt" ]
[ 10175@0, "sht" ]
[ 10175@0, "dbl" ]
[ 10175@0, "dbl" ]
[ 10176@0, "sht" ]
[ 10176@0, "dbl" ]
[ 10176@0, "dbl" ]
[ 10177@0, "sht" ]
[ 10177@0, "dbl" ]
[ 10177@0, "dbl" ]
[ 10178@0, "sht" ]
[ 10178@0, "dbl" ]
[ 10178@0, "dbl" ]
[ 10179@0, "int" ]
[ 10179@0, "chr" ]
[ 10179@0, "int" ]
[ 10180@0, "int" ]
[ 10180@0, "chr" ]
[ 10180@0, "int" ]
[ 10181@0, "int" ]
[ 10181@0, "chr" ]
[ 10181@0, "int" ]
[ 10182@0, "int" ]
[ 10182@0, "chr" ]
[ 10182@0, "int" ]
[ 10183@0, "int" ]
[ 10183@0, "sht" ]
[ 10183@0, "int" ]
[ 10184@0, "int" ]
[ 10184@0, "sht" ]
[ 10184@0, "int" ]
[ 10185@0, "int" ]
[ 10185@0, "sht" ]
[ 10185@0, "int" ]
[ 10186@0, "int" ]
[ 10186@0, "sht" ]
[ 10186@0, "int" ]
[ 10187@0, "int" ]
[ 10187@0, "int" ]
[ 10187@0, "int" ]
[ 10188@0, "int" ]
[ 10188@0, "int" ]
[ 10188@0, "int" ]
[ 10189@0, "int" ]
[ 10189@0, "int" ]
[ 10189@0, "int" ]
[ 10190@0, "int" ]
[ 10190@0, "int" ]
[ 10190@0, "int" ]
[ 10191@0, "int" ]
[ 10191@0, "lng" ]
[ 10191@0, "lng" ]
[ 10192@0, "int" ]
[ 10192@0, "lng" ]
[ 10192@0, "lng" ]
[ 10193@0, "int" ]
[ 10193@0, "lng" ]
[ 10193@0, "lng" ]
[ 10194@0, "int" ]
[ 10194@0, "lng" ]
[ 10194@0, "lng" ]
[ 10195@0, "int" ]
[ 10195@0, "flt" ]
[ 10195@0, "flt" ]
[ 10196@0, "int" ]
[ 10196@0, "flt" ]
[ 10196@0, "flt" ]
[ 10197@0, "int" ]
[ 10197@0, "flt" ]
[ 10197@0, "flt" ]
[ 10198@0, "int" ]
[ 10198@0, "flt" ]
[ 10198@0, "flt" ]
[ 10199@0, "int" ]
[ 10199@0, "dbl" ]
[ 10199@0, "dbl" ]
[ 10200@0, "int" ]
[ 10200@0, "dbl" ]
[ 10200@0, "dbl" ]
[ 10201@0, "int" ]
[ 10201@0, "dbl" ]
[ 10201@0, "dbl" ]
[ 10202@0, "int" ]
[ 10202@0, "dbl" ]
[ 10202@0, "dbl" ]
[ 10203@0, "flt" ]
[ 10203@0, "chr" ]
[ 10203@0, "flt" ]
[ 10204@0, "flt" ]
[ 10204@0, "chr" ]
[ 10204@0, "flt" ]
[ 10205@0, "flt" ]
[ 10205@0, "chr" ]
[ 10205@0, "flt" ]
[ 10206@0, "flt" ]
[ 10206@0, "chr" ]
[ 10206@0, "flt" ]
[ 10207@0, "flt" ]
[ 10207@0, "sht" ]
[ 10207@0, "flt" ]
[ 10208@0, "flt" ]
[ 10208@0, "sht" ]
[ 10208@0, "flt" ]
[ 10209@0, "flt" ]
[ 10209@0, "sht" ]
[ 10209@0, "flt" ]
[ 10210@0, "flt" ]
[ 10210@0, "sht" ]
[ 10210@0, "flt" ]
[ 10211@0, "flt" ]
[ 10211@0, "int" ]
[ 10211@0, "flt" ]
[ 10212@0, "flt" ]
[ 10212@0, "int" ]
[ 10212@0, "flt" ]
[ 10213@0, "flt" ]
[ 10213@0, "int" ]
[ 10213@0, "flt" ]
[ 10214@0, "flt" ]
[ 10214@0, "int" ]
[ 10214@0, "flt" ]
[ 10215@0, "flt" ]
[ 10215@0, "lng" ]
[ 10215@0, "flt" ]
[ 10216@0, "flt" ]
[ 10216@0, "lng" ]
[ 10216@0, "flt" ]
[ 10217@0, "flt" ]
[ 10217@0, "lng" ]
[ 10217@0, "flt" ]
[ 10218@0, "flt" ]
[ 10218@0, "lng" ]
[ 10218@0, "flt" ]
[ 10219@0, "flt" ]
[ 10219@0, "flt" ]
[ 10219@0, "flt" ]
[ 10220@0, "flt" ]
[ 10220@0, "flt" ]
[ 10220@0, "flt" ]
[ 10221@0, "flt" ]
[ 10221@0, "flt" ]
[ 10221@0, "flt" ]
[ 10222@0, "flt" ]
[ 10222@0, "flt" ]
[ 10222@0, "flt" ]
[ 10223@0, "flt" ]
[ 10223@0, "dbl" ]
[ 10223@0, "dbl" ]
[ 10224@0, "flt" ]
[ 10224@0, "dbl" ]
[ 10224@0, "dbl" ]
[ 10225@0, "flt" ]
[ 10225@0, "dbl" ]
[ 10225@0, "dbl" ]
[ 10226@0, "flt" ]
[ 10226@0, "dbl" ]
[ 10226@0, "dbl" ]
[ 10227@0, "dbl" ]
[ 10227@0, "chr" ]
[ 10227@0, "dbl" ]
[ 10228@0, "dbl" ]
[ 10228@0, "chr" ]
[ 10228@0, "dbl" ]
[ 10229@0, "dbl" ]
[ 10229@0, "chr" ]
[ 10229@0, "dbl" ]
[ 10230@0, "dbl" ]
[ 10230@0, "chr" ]
[ 10230@0, "dbl" ]
[ 10231@0, "dbl" ]
[ 10231@0, "sht" ]
[ 10231@0, "dbl" ]
[ 10232@0, "dbl" ]
[ 10232@0, "sht" ]
[ 10232@0, "dbl" ]
[ 10233@0, "dbl" ]
[ 10233@0, "sht" ]
[ 10233@0, "dbl" ]
[ 10234@0, "dbl" ]
[ 10234@0, "sht" ]
[ 10234@0, "dbl" ]
[ 10235@0, "dbl" ]
[ 10235@0, "int" ]
[ 10235@0, "dbl" ]
[ 10236@0, "dbl" ]
[ 10236@0, "int" ]
[ 10236@0, "dbl" ]
[ 10237@0, "dbl" ]
[ 10237@0, "int" ]
[ 10237@0, "dbl" ]
[ 10238@0, "dbl" ]
[ 10238@0, "int" ]
[ 10238@0, "dbl" ]
[ 10239@0, "dbl" ]
[ 10239@0, "lng" ]
[ 10239@0, "dbl" ]
[ 10240@0, "dbl" ]
[ 10240@0, "lng" ]
[ 10240@0, "dbl" ]
[ 10241@0, "dbl" ]
[ 10241@0, "lng" ]
[ 10241@0, "dbl" ]
[ 10242@0, "dbl" ]
[ 10242@0, "lng" ]
[ 10242@0, "dbl" ]
[ 10243@0, "dbl" ]
[ 10243@0, "flt" ]
[ 10243@0, "dbl" ]
[ 10244@0, "dbl" ]
[ 10244@0, "flt" ]
[ 10244@0, "dbl" ]
[ 10245@0, "dbl" ]
[ 10245@0, "flt" ]
[ 10245@0, "dbl" ]
[ 10246@0, "dbl" ]
[ 10246@0, "flt" ]
[ 10246@0, "dbl" ]
[ 10247@0, "dbl" ]
[ 10247@0, "dbl" ]
[ 10247@0, "dbl" ]
[ 10248@0, "dbl" ]
[ 10248@0, "dbl" ]
[ 10248@0, "dbl" ]
[ 10249@0, "dbl" ]
[ 10249@0, "dbl" ]
[ 10249@0, "dbl" ]
[ 10250@0, "dbl" ]
[ 10250@0, "dbl" ]
[ 10250@0, "dbl" ]
[ 10251@0, "lng" ]
[ 10251@0, "chr" ]
[ 10251@0, "lng" ]
[ 10252@0, "lng" ]
[ 10252@0, "chr" ]
[ 10252@0, "lng" ]
[ 10253@0, "lng" ]
[ 10253@0, "chr" ]
[ 10253@0, "lng" ]
[ 10254@0, "lng" ]
[ 10254@0, "chr" ]
[ 10254@0, "lng" ]
[ 10255@0, "lng" ]
[ 10255@0, "sht" ]
[ 10255@0, "lng" ]
[ 10256@0, "lng" ]
[ 10256@0, "sht" ]
[ 10256@0, "lng" ]
[ 10257@0, "lng" ]
[ 10257@0, "sht" ]
[ 10257@0, "lng" ]
[ 10258@0, "lng" ]
[ 10258@0, "sht" ]
[ 10258@0, "lng" ]
[ 10259@0, "lng" ]
[ 10259@0, "int" ]
[ 10259@0, "lng" ]
[ 10260@0, "lng" ]
[ 10260@0, "int" ]
[ 10260@0, "lng" ]
[ 10261@0, "lng" ]
[ 10261@0, "int" ]
[ 10261@0, "lng" ]
[ 10262@0, "lng" ]
[ 10262@0, "int" ]
[ 10262@0, "lng" ]
[ 10263@0, "lng" ]
[ 10263@0, "lng" ]
[ 10263@0, "lng" ]
[ 10264@0, "lng" ]
[ 10264@0, "lng" ]
[ 10264@0, "lng" ]
[ 10265@0, "lng" ]
[ 10265@0, "lng" ]
[ 10265@0, "lng" ]
[ 10266@0, "lng" ]
[ 10266@0, "lng" ]
[ 10266@0, "lng" ]
[ 10267@0, "lng" ]
[ 10267@0, "flt" ]
[ 10267@0, "dbl" ]
[ 10268@0, "lng" ]
[ 10268@0, "flt" ]
[ 10268@0, "dbl" ]
[ 10269@0, "lng" ]
[ 10269@0, "flt" ]
[ 10269@0, "dbl" ]
[ 10270@0, "lng" ]
[ 10270@0, "flt" ]
[ 10270@0, "dbl" ]
[ 10271@0, "lng" ]
[ 10271@0, "dbl" ]
[ 10271@0, "dbl" ]
[ 10272@0, "lng" ]
[ 10272@0, "dbl" ]
[ 10272@0, "dbl" ]
[ 10273@0, "lng" ]
[ 10273@0, "dbl" ]
[ 10273@0, "dbl" ]
[ 10274@0, "lng" ]
[ 10274@0, "dbl" ]
[ 10274@0, "dbl" ]
[ 10275@0, "any::1" ]
[ 10275@0, "any::1" ]
[ 10275@0, "any::1" ]
[ 10276@0, "any::1" ]
[ 10276@0, "any::1" ]
[ 10276@0, "any::1" ]
[ 10277@0, "chr" ]
[ 10277@0, "chr" ]
[ 10277@0, "chr" ]
[ 10278@0, "chr" ]
[ 10278@0, "chr" ]
[ 10278@0, "chr" ]
[ 10279@0, "sht" ]
[ 10279@0, "sht" ]
[ 10279@0, "sht" ]
[ 10280@0, "sht" ]
[ 10280@0, "sht" ]
[ 10280@0, "sht" ]
[ 10281@0, "int" ]
[ 10281@0, "int" ]
[ 10281@0, "int" ]
[ 10282@0, "int" ]
[ 10282@0, "int" ]
[ 10282@0, "int" ]
[ 10283@0, "oid" ]
[ 10283@0, "oid" ]
[ 10283@0, "oid" ]
[ 10284@0, "oid" ]
[ 10284@0, "oid" ]
[ 10284@0, "oid" ]
[ 10285@0, "flt" ]
[ 10285@0, "flt" ]
[ 10285@0, "flt" ]
[ 10286@0, "flt" ]
[ 10286@0, "flt" ]
[ 10286@0, "flt" ]
[ 10287@0, "lng" ]
[ 10287@0, "lng" ]
[ 10287@0, "lng" ]
[ 10288@0, "lng" ]
[ 10288@0, "lng" ]
[ 10288@0, "lng" ]
[ 10289@0, "dbl" ]
[ 10289@0, "dbl" ]
[ 10289@0, "dbl" ]
[ 10290@0, "dbl" ]
[ 10290@0, "dbl" ]
[ 10290@0, "dbl" ]
[ 10291@0, "chr" ]
[ 10291@0, "chr" ]
[ 10292@0, "chr" ]
[ 10292@0, "chr" ]
[ 10293@0, "sht" ]
[ 10293@0, "sht" ]
[ 10294@0, "sht" ]
[ 10294@0, "sht" ]
[ 10295@0, "int" ]
[ 10295@0, "int" ]
[ 10296@0, "int" ]
[ 10296@0, "int" ]
[ 10297@0, "flt" ]
[ 10297@0, "flt" ]
[ 10298@0, "flt" ]
[ 10298@0, "flt" ]
[ 10299@0, "lng" ]
[ 10299@0, "lng" ]
[ 10300@0, "lng" ]
[ 10300@0, "lng" ]
[ 10301@0, "dbl" ]
[ 10301@0, "dbl" ]
[ 10302@0, "dbl" ]
[ 10302@0, "dbl" ]
[ 10303@0, "flt" ]
[ 10303@0, "flt" ]
[ 10304@0, "dbl" ]
[ 10304@0, "dbl" ]
[ 10305@0, "bit" ]
[ 10305@0, "bit" ]
[ 10305@0, "bit" ]
[ 10306@0, "bit" ]
[ 10306@0, "bit" ]
[ 10306@0, "bit" ]
[ 10307@0, "bit" ]
[ 10307@0, "bit" ]
[ 10307@0, "bit" ]
[ 10308@0, "bit" ]
[ 10308@0, "bit" ]
[ 10309@0, "bit" ]
[ 10309@0, "any::1" ]
[ 10309@0, "any::1" ]
[ 10309@0, "any::1" ]
[ 10310@0, "chr" ]
[ 10310@0, "chr" ]
[ 10310@0, "chr" ]
[ 10311@0, "chr" ]
[ 10311@0, "chr" ]
[ 10311@0, "chr" ]
[ 10312@0, "chr" ]
[ 10312@0, "chr" ]
[ 10312@0, "chr" ]
[ 10313@0, "chr" ]
[ 10313@0, "chr" ]
[ 10314@0, "chr" ]
[ 10314@0, "int" ]
[ 10314@0, "chr" ]
[ 10315@0, "chr" ]
[ 10315@0, "int" ]
[ 10315@0, "chr" ]
[ 10316@0, "sht" ]
[ 10316@0, "sht" ]
[ 10316@0, "sht" ]
[ 10317@0, "sht" ]
[ 10317@0, "sht" ]
[ 10317@0, "sht" ]
[ 10318@0, "sht" ]
[ 10318@0, "sht" ]
[ 10318@0, "sht" ]
[ 10319@0, "sht" ]
[ 10319@0, "sht" ]
[ 10320@0, "sht" ]
[ 10320@0, "int" ]
[ 10320@0, "sht" ]
[ 10321@0, "sht" ]
[ 10321@0, "int" ]
[ 10321@0, "sht" ]
[ 10322@0, "int" ]
[ 10322@0, "int" ]
[ 10322@0, "int" ]
[ 10323@0, "int" ]
[ 10323@0, "int" ]
[ 10323@0, "int" ]
[ 10324@0, "int" ]
[ 10324@0, "int" ]
[ 10324@0, "int" ]
[ 10325@0, "int" ]
[ 10325@0, "int" ]
[ 10326@0, "int" ]
[ 10326@0, "int" ]
[ 10326@0, "int" ]
[ 10327@0, "int" ]
[ 10327@0, "int" ]
[ 10327@0, "int" ]
[ 10328@0, "lng" ]
[ 10328@0, "lng" ]
[ 10328@0, "lng" ]
[ 10329@0, "lng" ]
[ 10329@0, "lng" ]
[ 10329@0, "lng" ]
[ 10330@0, "lng" ]
[ 10330@0, "lng" ]
[ 10330@0, "lng" ]
[ 10331@0, "lng" ]
[ 10331@0, "lng" ]
[ 10332@0, "lng" ]
[ 10332@0, "int" ]
[ 10332@0, "lng" ]
[ 10333@0, "lng" ]
[ 10333@0, "int" ]
[ 10333@0, "lng" ]
[ 10334@0, "int" ]
[ 10335@0, "int" ]
[ 10335@0, "void" ]
[ 10336@0, "int" ]
[ 10337@0, "chr" ]
[ 10338@0, "chr" ]
[ 10339@0, "sht" ]
[ 10340@0, "sht" ]
[ 10341@0, "int" ]
[ 10342@0, "int" ]
[ 10343@0, "lng" ]
[ 10344@0, "lng" ]
[ 10345@0, "lng" ]
[ 10345@0, "dbl" ]
[ 10346@0, "dbl" ]
[ 10346@0, "lng" ]
[ 10347@0, "int" ]
[ 10347@0, "flt" ]
[ 10348@0, "flt" ]
[ 10348@0, "int" ]
[ 10349@0, "void" ]
[ 10352@0, "str" ]
[ 10352@0, "int" ]
[ 10352@0, "str" ]
[ 10353@0, "str" ]
[ 10353@0, "int" ]
[ 10353@0, "int" ]
[ 10353@0, "str" ]
[ 10354@0, "str" ]
[ 10354@0, "any" ]
[ 10354@0, "str" ]
[ 10355@0, "str" ]
[ 10355@0, "int" ]
[ 10356@0, "str" ]
[ 10356@0, "int" ]
[ 10357@0, "str" ]
[ 10357@0, "int" ]
[ 10357@0, "chr" ]
[ 10358@0, "str" ]
[ 10358@0, "int" ]
[ 10358@0, "int" ]
[ 10359@0, "int" ]
[ 10359@0, "str" ]
[ 10360@0, "str" ]
[ 10361@0, "str" ]
[ 10361@0, "str" ]
[ 10361@0, "str" ]
[ 10361@0, "str" ]
[ 10362@0, "str" ]
[ 10362@0, "str" ]
[ 10362@0, "bit" ]
[ 10363@0, "str" ]
[ 10363@0, "str" ]
[ 10363@0, "bit" ]
[ 10364@0, "str" ]
[ 10364@0, "str" ]
[ 10365@0, "str" ]
[ 10365@0, "str" ]
[ 10366@0, "str" ]
[ 10366@0, "chr" ]
[ 10366@0, "int" ]
[ 10367@0, "str" ]
[ 10367@0, "chr" ]
[ 10367@0, "int" ]
[ 10368@0, "str" ]
[ 10368@0, "str" ]
[ 10368@0, "int" ]
[ 10369@0, "str" ]
[ 10369@0, "str" ]
[ 10369@0, "int" ]
[ 10370@0, "str" ]
[ 10370@0, "str" ]
[ 10371@0, "str" ]
[ 10371@0, "str" ]
[ 10372@0, "str" ]
[ 10372@0, "str" ]
[ 10373@0, "str" ]
[ 10373@0, "str" ]
[ 10373@0, "str" ]
[ 10373@0, "bit" ]
[ 10373@0, "str" ]
[ 10374@0, "str" ]
[ 10374@0, "str" ]
[ 10374@0, "BAT[void,str]" ]
[ 10375@0, "void" ]
[ 10378@0, "void" ]
[ 10381@0, "int" ]
[ 10381@0, "int" ]
[ 10381@0, "BAT[any,any]" ]
[ 10382@0, "int" ]
[ 10382@0, "int" ]
[ 10382@0, "int" ]
[ 10382@0, "BAT[any,any]" ]
[ 10383@0, "int" ]
[ 10383@0, "int" ]
[ 10383@0, "lng" ]
[ 10383@0, "BAT[any,any]" ]
[ 10384@0, "BAT[any::1,any::2]" ]
[ 10384@0, "BAT[any::2,any::1]" ]
[ 10385@0, "BAT[any::1,any]" ]
[ 10385@0, "BAT[any::1,any::1]" ]
[ 10386@0, "BAT[any::1,any::2]" ]
[ 10386@0, "BAT[any::1,any::2]" ]
[ 10387@0, "BAT[any::1,any::2]" ]
[ 10387@0, "BAT[any::1,any::2]" ]
[ 10388@0, "BAT[any::1,any::2]" ]
[ 10388@0, "BAT[any::1,any::2]" ]
[ 10389@0, "BAT[any::1,any::2]" ]
[ 10389@0, "BAT[any::1,any::2]" ]
[ 10390@0, "BAT[any::1,any::2]" ]
[ 10390@0, "any::1" ]
[ 10390@0, "any::2" ]
[ 10390@0, "BAT[any::1,any::2]" ]
[ 10391@0, "BAT[any::1,any::2]" ]
[ 10391@0, "BAT[any::1,any::2]" ]
[ 10391@0, "BAT[any::1,any::2]" ]
[ 10392@0, "BAT[any::1,any::2]" ]
[ 10392@0, "any::1" ]
[ 10392@0, "any::2" ]
[ 10392@0, "BAT[any::1,any::2]" ]
[ 10393@0, "BAT[any::1,any::2]" ]
[ 10393@0, "BAT[any::1,any::2]" ]
[ 10393@0, "BAT[any::1,any::2]" ]
[ 10394@0, "BAT[any::1,any::2]" ]
[ 10394@0, "any::1" ]
[ 10394@0, "any::2" ]
[ 10394@0, "BAT[any::1,any::2]" ]
[ 10395@0, "BAT[any::1,any::2]" ]
[ 10395@0, "any::1" ]
[ 10395@0, "BAT[any::1,any::2]" ]
[ 10396@0, "BAT[any::1,any::2]" ]
[ 10396@0, "BAT[any::1,any::2]" ]
[ 10397@0, "BAT[any::1,any::2]" ]
[ 10397@0, "BAT[any::1,any]" ]
[ 10397@0, "BAT[any::1,any::2]" ]
[ 10398@0, "BAT[any::1,any::2]" ]
[ 10398@0, "BAT[any::1,any::2]" ]
[ 10398@0, "BAT[any::1,any::2]" ]
[ 10399@0, "int" ]
[ 10399@0, "lng" ]
[ 10400@0, "int" ]
[ 10400@0, "lng" ]
[ 10401@0, "BAT[any,any]" ]
[ 10401@0, "BAT[str,str]" ]
[ 10402@0, "int" ]
[ 10402@0, "str" ]
[ 10403@0, "int" ]
[ 10403@0, "str" ]
[ 10404@0, "BAT[any::1,any::2]" ]
[ 10404@0, "bit" ]
[ 10404@0, "BAT[any::1,any::2]" ]
[ 10405@0, "BAT[any::1,any::2]" ]
[ 10405@0, "bit" ]
[ 10406@0, "BAT[any::1,any::2]" ]
[ 10406@0, "bit" ]
[ 10406@0, "BAT[any::1,any::2]" ]
[ 10407@0, "BAT[any::1,any::2]" ]
[ 10407@0, "int" ]
[ 10407@0, "BAT[any::1,any::2]" ]
[ 10408@0, "BAT[any::1,any::2]" ]
[ 10408@0, "int" ]
[ 10409@0, "BAT[oid,any::1]" ]
[ 10409@0, "oid" ]
[ 10410@0, "BAT[void,any::1]" ]
[ 10410@0, "oid" ]
[ 10411@0, "BAT[void,any::1]" ]
[ 10411@0, "oid" ]
[ 10411@0, "BAT[void,any::1]" ]
[ 10412@0, "BAT[any,any]" ]
[ 10412@0, "bit" ]
[ 10413@0, "BAT[any,any]" ]
[ 10413@0, "bit" ]
[ 10414@0, "str" ]
[ 10414@0, "int" ]
[ 10415@0, "BAT[any,any]" ]
[ 10415@0, "int" ]
[ 10416@0, "BAT[any,any]" ]
[ 10416@0, "ptr" ]
[ 10416@0, "void" ]
[ 10417@0, "BAT[any,any]" ]
[ 10417@0, "ptr" ]
[ 10417@0, "int" ]
[ 10417@0, "int" ]
[ 10417@0, "void" ]
[ 10418@0, "BAT[any::1,any]" ]
[ 10418@0, "ptr" ]
[ 10418@0, "any::1" ]
[ 10418@0, "void" ]
[ 10419@0, "BAT[any,any]" ]
[ 10419@0, "str" ]
[ 10419@0, "bit" ]
[ 10420@0, "BAT[any,any]" ]
[ 10420@0, "str" ]
[ 10421@0, "BAT[any::1,any::2]" ]
[ 10421@0, "str" ]
[ 10421@0, "str" ]
[ 10421@0, "BAT[any::1,any::2]" ]
[ 10422@0, "BAT[any::1,any::2]" ]
[ 10422@0, "bit" ]
[ 10422@0, "BAT[any::1,any::2]" ]
[ 10423@0, "str" ]
[ 10423@0, "bit" ]
[ 10423@0, "bit" ]
[ 10424@0, "str" ]
[ 10424@0, "bit" ]
[ 10425@0, "str" ]
[ 10425@0, "bit" ]
[ 10426@0, "str" ]
[ 10426@0, "bit" ]
[ 10427@0, "str" ]
[ 10427@0, "void" ]
[ 10428@0, "str" ]
[ 10428@0, "void" ]
[ 10429@0, "str" ]
[ 10429@0, "int" ]
[ 10430@0, "BAT[any::1,any::2]" ]
[ 10430@0, "int" ]
[ 10430@0, "int" ]
[ 10430@0, "int" ]
[ 10430@0, "int" ]
[ 10430@0, "int" ]
[ 10430@0, "BAT[any::1,any::2]" ]
[ 10431@0, "BAT[any::1,any::2]" ]
[ 10431@0, "int" ]
[ 10431@0, "int" ]
[ 10431@0, "int" ]
[ 10431@0, "int" ]
[ 10431@0, "int" ]
[ 10431@0, "BAT[any::1,any::2]" ]
[ 10432@0, "BAT[any,any]" ]
[ 10432@0, "int" ]
[ 10432@0, "void" ]
[ 10433@0, "BAT[any,any]" ]
[ 10433@0, "int" ]
[ 10433@0, "any" ]
[ 10433@0, "void" ]
[ 10434@0, "BAT[any,any]" ]
[ 10434@0, "int" ]
[ 10434@0, "void" ]
[ 10435@0, "BAT[any,any]" ]
[ 10435@0, "int" ]
[ 10436@0, "BAT[any,any]" ]
[ 10436@0, "BAT[any,any]" ]
[ 10436@0, "bit" ]
[ 10437@0, "BAT[any::1,any::2]" ]
[ 10437@0, "int" ]
[ 10437@0, "BAT[any::1,any::2]" ]
[ 10438@0, "BAT[any::1,any::2]" ]
[ 10438@0, "int" ]
[ 10438@0, "BAT[any::1,any::2]" ]
[ 10439@0, "str" ]
[ 10439@0, "bit" ]
[ 10440@0, "BAT[any,any]" ]
[ 10440@0, "bit" ]
[ 10441@0, "BAT[any,any]" ]
[ 10441@0, "lng" ]
[ 10442@0, "BAT[any::1,any::2]" ]
[ 10442@0, "BAT[any::1,any::2]" ]
[ 10443@0, "str" ]
[ 10443@0, "BAT[any,any]" ]
[ 10444@0, "BAT[any::1,any::2]" ]
[ 10444@0, "void" ]
[ 10445@0, "BAT[any::1,any::2]" ]
[ 10445@0, "void" ]
[ 10446@0, "BAT[any,any]" ]
[ 10446@0, "str" ]
[ 10447@0, "BAT[any,any]" ]
[ 10447@0, "str" ]
[ 10448@0, "any" ]
[ 10448@0, "int" ]
[ 10449@0, "any" ]
[ 10449@0, "int" ]
[ 10450@0, "int" ]
[ 10450@0, "int" ]
[ 10450@0, "BAT[any,any]" ]
[ 10451@0, "int" ]
[ 10451@0, "int" ]
[ 10451@0, "int" ]
[ 10451@0, "BAT[any,any]" ]
[ 10452@0, "int" ]
[ 10452@0, "int" ]
[ 10452@0, "lng" ]
[ 10452@0, "BAT[any,any]" ]
[ 10455@0, "BAT[any::1,any]" ]
[ 10455@0, "any::1" ]
[ 10455@0, "bit" ]
[ 10456@0, "BAT[any::1,any::2]" ]
[ 10456@0, "any::1" ]
[ 10456@0, "any::2" ]
[ 10456@0, "bit" ]
[ 10457@0, "BAT[any::1,any::2]" ]
[ 10457@0, "any::1" ]
[ 10457@0, "any::2" ]
[ 10458@0, "BAT[any::1,any]" ]
[ 10458@0, "any::1" ]
[ 10458@0, "int" ]
[ 10459@0, "BAT[any::1,any::2]" ]
[ 10459@0, "any::1" ]
[ 10459@0, "any::2" ]
[ 10459@0, "int" ]
[ 10460@0, "BAT[any,any::1]" ]
[ 10460@0, "int" ]
[ 10460@0, "any::1" ]
[ 10461@0, "BAT[any,any::1]" ]
[ 10461@0, "oid" ]
[ 10461@0, "any::1" ]
[ 10462@0, "BAT[any::1,any::2]" ]
[ 10462@0, "BAT[int,any]" ]
[ 10462@0, "BAT[any::1,any::2]" ]
[ 10463@0, "BAT[any::1,any::2]" ]
[ 10463@0, "BAT[oid,any]" ]
[ 10463@0, "BAT[any::1,any::2]" ]
[ 10464@0, "BAT[any::1,any::2]" ]
[ 10464@0, "any::2" ]
[ 10464@0, "any::2" ]
[ 10464@0, "BAT[any::1,any::2]" ]
[ 10465@0, "BAT[any::1,any::2]" ]
[ 10465@0, "any::2" ]
[ 10465@0, "any::2" ]
[ 10465@0, "bit" ]
[ 10465@0, "bit" ]
[ 10465@0, "BAT[any::1,any::2]" ]
[ 10466@0, "BAT[any::1,any::2]" ]
[ 10466@0, "any::2" ]
[ 10466@0, "any::2" ]
[ 10466@0, "BAT[any::1,void]" ]
[ 10467@0, "BAT[any::1,any::2]" ]
[ 10467@0, "any::2" ]
[ 10467@0, "any::2" ]
[ 10467@0, "bit" ]
[ 10467@0, "bit" ]
[ 10467@0, "BAT[any::1,void]" ]
[ 10468@0, "BAT[any::1,any::2]" ]
[ 10468@0, "any::2" ]
[ 10468@0, "BAT[any::1,any::2]" ]
[ 10469@0, "BAT[any::1,any::2]" ]
[ 10469@0, "any::2" ]
[ 10469@0, "BAT[any::1,void]" ]
[ 10470@0, "BAT[any::1,any::2]" ]
[ 10470@0, "any::1" ]
[ 10470@0, "any::1" ]
[ 10470@0, "any::2" ]
[ 10470@0, "any::2" ]
[ 10470@0, "BAT[any::1,any::2]" ]
[ 10471@0, "BAT[any::1,any::2]" ]
[ 10471@0, "int" ]
[ 10471@0, "BAT[any::1,any::2]" ]
[ 10472@0, "BAT[any::1,str]" ]
[ 10472@0, "str" ]
[ 10472@0, "BAT[any::1,str]" ]
[ 10473@0, "BAT[any::1,any::2]" ]
[ 10473@0, "int" ]
[ 10473@0, "int" ]
[ 10473@0, "BAT[any::1,any::2]" ]
[ 10474@0, "BAT[any::1,any::2]" ]
[ 10474@0, "BAT[any::1,any::2]" ]
[ 10475@0, "BAT[any::1,any::2]" ]
[ 10475@0, "BAT[any::1,any::2]" ]
[ 10476@0, "BAT[any::1,any::2]" ]
[ 10476@0, "BAT[any::1,any::2]" ]
[ 10477@0, "BAT[any::1,any]" ]
[ 10477@0, "any::2" ]
[ 10477@0, "BAT[any::1,any::2]" ]
[ 10478@0, "BAT[any::1,any::2]" ]
[ 10478@0, "BAT[any::1,any::2]" ]
[ 10479@0, "BAT[any::1,any::2]" ]
[ 10479@0, "BAT[any::1,any::2]" ]
[ 10480@0, "BAT[any::1,any::2]" ]
[ 10480@0, "BAT[any::1,any::2]" ]
[ 10480@0, "BAT[any::1,any::2]" ]
[ 10481@0, "BAT[any::1,any::2]" ]
[ 10481@0, "BAT[any::1,any]" ]
[ 10481@0, "BAT[any::1,any::2]" ]
[ 10482@0, "BAT[any::1,any::2]" ]
[ 10482@0, "BAT[any::1,any::2]" ]
[ 10482@0, "BAT[any::1,any::2]" ]
[ 10483@0, "BAT[any::1,any::2]" ]
[ 10483@0, "BAT[any::1,any]" ]
[ 10483@0, "BAT[any::1,any::2]" ]
[ 10484@0, "BAT[any::1,any::2]" ]
[ 10484@0, "BAT[any::1,any::2]" ]
[ 10484@0, "BAT[any::1,any::2]" ]
[ 10485@0, "BAT[any::1,any::2]" ]
[ 10485@0, "BAT[any::1,any::2]" ]
[ 10485@0, "BAT[any::1,any::2]" ]
[ 10486@0, "BAT[any::1,any::2]" ]
[ 10486@0, "BAT[any::3,any::4]" ]
[ 10486@0, "BAT[any::1,any::4]" ]
[ 10487@0, "BAT[any::1,any::2]" ]
[ 10487@0, "BAT[any::2,any::3]" ]
[ 10487@0, "lng" ]
[ 10487@0, "BAT[any::1,any::3]" ]
[ 10488@0, "BAT[any::1,any::2]" ]
[ 10488@0, "BAT[any::2,any::3]" ]
[ 10488@0, "lng" ]
[ 10488@0, "BAT[any::1,any::3]" ]
[ 10489@0, "BAT[any::1,any::2]" ]
[ 10489@0, "BAT[any::2,any::3]" ]
[ 10489@0, "int" ]
[ 10489@0, "lng" ]
[ 10489@0, "BAT[any::1,any::3]" ]
[ 10490@0, "BAT[any::2,any::2]" ]
[ 10490@0, "BAT[any::1,any::3]" ]
[ 10490@0, "BAT[any::1,any::2]" ]
[ 10490@0, "BAT[any::2,any::3]" ]
[ 10490@0, "int" ]
[ 10490@0, "void" ]
[ 10491@0, "BAT[any::1,any::2]" ]
[ 10491@0, "BAT[any::2,any::3]" ]
[ 10491@0, "any::2" ]
[ 10491@0, "any::2" ]
[ 10491@0, "BAT[any::1,any::3]" ]
[ 10492@0, "BAT[any::1,any]" ]
[ 10492@0, "BAT[any::1,oid]" ]
[ 10493@0, "BAT[any::1,any]" ]
[ 10493@0, "oid" ]
[ 10493@0, "BAT[any::1,oid]" ]
[ 10494@0, "BAT[any::1,oid]" ]
[ 10494@0, "BAT[oid,oid]" ]
[ 10494@0, "BAT[any::1,oid]" ]
[ 10495@0, "BAT[any::1,any]" ]
[ 10495@0, "BAT[any::1,int]" ]
[ 10496@0, "BAT[any::1,any]" ]
[ 10496@0, "int" ]
[ 10496@0, "int" ]
[ 10496@0, "int" ]
[ 10496@0, "BAT[any::1,int]" ]
[ 10497@0, "BAT[any::1,any::2]" ]
[ 10497@0, "int" ]
[ 10497@0, "BAT[int,BAT]" ]
[ 10498@0, "BAT[any::1,any::2]" ]
[ 10498@0, "int" ]
[ 10498@0, "BAT[int,BAT]" ]
[ 10499@0, "BAT[any::1,any::2]" ]
[ 10499@0, "int" ]
[ 10499@0, "BAT[any::2,BAT]" ]
[ 10500@0, "BAT[any::1,any::2]" ]
[ 10500@0, "int" ]
[ 10500@0, "BAT[any::2,BAT]" ]
[ 10501@0, "BAT[any,any]" ]
[ 10501@0, "int" ]
[ 10502@0, "BAT[any,any]" ]
[ 10502@0, "bit" ]
[ 10502@0, "int" ]
[ 10503@0, "BAT[any,any::2]" ]
[ 10503@0, "BAT[any::2,int]" ]
[ 10504@0, "BAT[any::2,any]" ]
[ 10504@0, "BAT[any::2,int]" ]
[ 10505@0, "BAT[any::1,any::2]" ]
[ 10505@0, "any::2" ]
[ 10506@0, "BAT[any::1,any::2]" ]
[ 10506@0, "any::2" ]
[ 10507@0, "BAT[any,uchr]" ]
[ 10507@0, "uchr" ]
[ 10508@0, "BAT[any,uchr]" ]
[ 10508@0, "sht" ]
[ 10509@0, "BAT[any,uchr]" ]
[ 10509@0, "int" ]
[ 10510@0, "BAT[any,uchr]" ]
[ 10510@0, "lng" ]
[ 10511@0, "BAT[any,sht]" ]
[ 10511@0, "sht" ]
[ 10512@0, "BAT[any,sht]" ]
[ 10512@0, "int" ]
[ 10513@0, "BAT[any,sht]" ]
[ 10513@0, "lng" ]
[ 10514@0, "BAT[any,int]" ]
[ 10514@0, "int" ]
[ 10515@0, "BAT[any,int]" ]
[ 10515@0, "lng" ]
[ 10516@0, "BAT[any,lng]" ]
[ 10516@0, "lng" ]
[ 10517@0, "BAT[any,flt]" ]
[ 10517@0, "flt" ]
[ 10518@0, "BAT[any,flt]" ]
[ 10518@0, "dbl" ]
[ 10519@0, "BAT[any,dbl]" ]
[ 10519@0, "dbl" ]
[ 10520@0, "BAT[any,uchr]" ]
[ 10520@0, "uchr" ]
[ 10521@0, "BAT[any,uchr]" ]
[ 10521@0, "sht" ]
[ 10522@0, "BAT[any,uchr]" ]
[ 10522@0, "int" ]
[ 10523@0, "BAT[any,uchr]" ]
[ 10523@0, "lng" ]
[ 10524@0, "BAT[any,sht]" ]
[ 10524@0, "sht" ]
[ 10525@0, "BAT[any,sht]" ]
[ 10525@0, "int" ]
[ 10526@0, "BAT[any,sht]" ]
[ 10526@0, "lng" ]
[ 10527@0, "BAT[any,int]" ]
[ 10527@0, "int" ]
[ 10528@0, "BAT[any,int]" ]
[ 10528@0, "lng" ]
[ 10529@0, "BAT[any,lng]" ]
[ 10529@0, "lng" ]
[ 10530@0, "BAT[any,flt]" ]
[ 10530@0, "flt" ]
[ 10531@0, "BAT[any,flt]" ]
[ 10531@0, "dbl" ]
[ 10532@0, "BAT[any,dbl]" ]
[ 10532@0, "dbl" ]
[ 10533@0, "BAT[any,uchr]" ]
[ 10533@0, "uchr" ]
[ 10534@0, "BAT[any,sht]" ]
[ 10534@0, "sht" ]
[ 10535@0, "BAT[any,int]" ]
[ 10535@0, "int" ]
[ 10536@0, "BAT[any,flt]" ]
[ 10536@0, "flt" ]
[ 10537@0, "BAT[any,dbl]" ]
[ 10537@0, "dbl" ]
[ 10538@0, "BAT[any,lng]" ]
[ 10538@0, "lng" ]
[ 10539@0, "BAT[any,uchr]" ]
[ 10539@0, "uchr" ]
[ 10540@0, "BAT[any,sht]" ]
[ 10540@0, "sht" ]
[ 10541@0, "BAT[any,int]" ]
[ 10541@0, "int" ]
[ 10542@0, "BAT[any,flt]" ]
[ 10542@0, "flt" ]
[ 10543@0, "BAT[any,dbl]" ]
[ 10543@0, "dbl" ]
[ 10544@0, "BAT[any,lng]" ]
[ 10544@0, "lng" ]
[ 10545@0, "str" ]
[ 10545@0, "str" ]
[ 10545@0, "str" ]
[ 10545@0, "str" ]
[ 10545@0, "str" ]
[ 10545@0, "void" ]
[ 10546@0, "BAT[any::1,any::2]" ]
[ 10546@0, "BAT[any::1,any::2]" ]
[ 10547@0, "BAT[any::1,any::2]" ]
[ 10547@0, "BAT[any::1,any]" ]
[ 10547@0, "BAT[any::1,any::2]" ]
[ 10548@0, "BAT[any::1,any::2]" ]
[ 10548@0, "BAT[any::1,any::2]" ]
[ 10549@0, "BAT[any::1,any::2]" ]
[ 10549@0, "BAT[any::1,any::2]" ]
[ 10549@0, "BAT[any::1,any::2]" ]
[ 10550@0, "BAT[any::1,any::2]" ]
[ 10550@0, "BAT[any::1,any::2]" ]
[ 10550@0, "BAT[any::1,any::2]" ]
[ 10551@0, "BAT[any::1,any::2]" ]
[ 10551@0, "BAT[any::1,any::2]" ]
[ 10551@0, "BAT[any::1,any::2]" ]
[ 10552@0, "BAT[any::1,any]" ]
[ 10552@0, "BAT[any::1,void]" ]
[ 10553@0, "BAT[any::1,any::2]" ]
[ 10553@0, "BAT[any::2,any::3]" ]
[ 10553@0, "BAT[any::1,any::3]" ]
[ 10554@0, "BAT[any::1,any::2]" ]
[ 10554@0, "BAT[any::2,any::3]" ]
[ 10554@0, "BAT[any::1,any::3]" ]
[ 10555@0, "BAT[any::1,any::2]" ]
[ 10555@0, "BAT[any::2,any::3]" ]
[ 10555@0, "str" ]
[ 10555@0, "*any" ]
[ 10555@0, "BAT[any::1,any::3]" ]
[ 10556@0, "BAT[any,any]" ]
[ 10556@0, "BAT[any,any]" ]
[ 10556@0, "int" ]
[ 10556@0, "BAT[any,any]" ]
[ 10557@0, "BAT[any::1,any::2]" ]
[ 10557@0, "BAT[any::2,any::3]" ]
[ 10557@0, "lng" ]
[ 10557@0, "str" ]
[ 10557@0, "*any" ]
[ 10557@0, "BAT[any::1,any::3]" ]
[ 10558@0, "BAT[any::1,str]" ]
[ 10558@0, "str" ]
[ 10558@0, "BAT[any::1,oid]" ]
[ 10559@0, "BAT[any::1,any::2]" ]
[ 10559@0, "str" ]
[ 10559@0, "*any" ]
[ 10559@0, "BAT[any::1,any::2]" ]
[ 10560@0, "BAT[any::1,any::2]" ]
[ 10560@0, "str" ]
[ 10560@0, "any::2" ]
[ 10560@0, "any::2" ]
[ 10560@0, "BAT[any::1,any::2]" ]
[ 10561@0, "BAT[any::1,any::2]" ]
[ 10561@0, "str" ]
[ 10561@0, "*any" ]
[ 10561@0, "BAT[any::1,any::2]" ]
[ 10562@0, "BAT[any::1,any::2]" ]
[ 10562@0, "str" ]
[ 10562@0, "any::2" ]
[ 10562@0, "BAT[any::1,any::2]" ]
[ 10563@0, "BAT[any,any::1]" ]
[ 10563@0, "BAT[any::1,void]" ]
[ 10564@0, "BAT[any::1,any::2]" ]
[ 10564@0, "BAT[any::1,any::2]" ]
[ 10565@0, "BAT[any,uchr]" ]
[ 10565@0, "uchr" ]
[ 10566@0, "BAT[any,uchr]" ]
[ 10566@0, "uchr" ]
[ 10567@0, "BAT[any,sht]" ]
[ 10567@0, "sht" ]
[ 10568@0, "BAT[any,sht]" ]
[ 10568@0, "sht" ]
[ 10569@0, "BAT[any,int]" ]
[ 10569@0, "int" ]
[ 10570@0, "BAT[any,int]" ]
[ 10570@0, "int" ]
[ 10571@0, "BAT[any,lng]" ]
[ 10571@0, "lng" ]
[ 10572@0, "BAT[any,lng]" ]
[ 10572@0, "lng" ]
[ 10573@0, "BAT[any,flt]" ]
[ 10573@0, "flt" ]
[ 10574@0, "BAT[any,flt]" ]
[ 10574@0, "flt" ]
[ 10575@0, "BAT[any,dbl]" ]
[ 10575@0, "dbl" ]
[ 10576@0, "BAT[any,dbl]" ]
[ 10576@0, "dbl" ]
[ 10577@0, "BAT[any,uchr]" ]
[ 10577@0, "dbl" ]
[ 10578@0, "BAT[any,sht]" ]
[ 10578@0, "dbl" ]
[ 10579@0, "BAT[any,int]" ]
[ 10579@0, "dbl" ]
[ 10580@0, "BAT[any,lng]" ]
[ 10580@0, "dbl" ]
[ 10581@0, "BAT[any,flt]" ]
[ 10581@0, "dbl" ]
[ 10582@0, "BAT[any,dbl]" ]
[ 10582@0, "dbl" ]
[ 10583@0, "BAT[any,any]" ]
[ 10583@0, "int" ]
[ 10586@0, "BAT[str,int]" ]
[ 10587@0, "BAT[str,int]" ]
[ 10588@0, "BAT[str,int]" ]
[ 10589@0, "BAT[str,int]" ]
[ 10590@0, "BAT[lng,lng]" ]
[ 10591@0, "BAT[lng,lng]" ]
[ 10592@0, "void" ]
[ 10593@0, "void" ]
[ 10594@0, "lng" ]
[ 10595@0, "lng" ]
[ 10596@0, "lng" ]
[ 10596@0, "void" ]
[ 10597@0, "lng" ]
[ 10598@0, "lng" ]
[ 10599@0, "lng" ]
[ 10599@0, "void" ]
[ 10600@0, "lng" ]
[ 10601@0, "lng" ]
[ 10601@0, "void" ]
[ 10602@0, "lng" ]
[ 10603@0, "lng" ]
[ 10603@0, "void" ]
[ 10604@0, "lng" ]
[ 10604@0, "BAT[str,lng]" ]
[ 10605@0, "lng" ]
[ 10605@0, "BAT[str,lng]" ]
[ 10606@0, "BAT[int,str]" ]
[ 10607@0, "BAT[int,int]" ]
[ 10608@0, "BAT[int,int]" ]
[ 10609@0, "BAT[int,str]" ]
[ 10610@0, "BAT[int,int]" ]
[ 10611@0, "BAT[int,str]" ]
[ 10612@0, "BAT[int,str]" ]
[ 10613@0, "BAT[int,str]" ]
[ 10614@0, "lng" ]
[ 10615@0, "BAT[str,str]" ]
[ 10616@0, "BAT[int,str]" ]
[ 10617@0, "BAT[int,str]" ]
[ 10618@0, "BAT[int,int]" ]
[ 10619@0, "BAT[int,int]" ]
[ 10620@0, "BAT[int,str]" ]
[ 10621@0, "BAT[int,str]" ]
[ 10622@0, "BAT[int,str]" ]
[ 10628@0, "BAT[int,str]" ]
[ 10629@0, "str" ]
[ 10629@0, "str" ]
[ 10630@0, "str" ]
[ 10630@0, "str" ]
[ 10631@0, "oid" ]
[ 10631@0, "str" ]
[ 10632@0, "int" ]
[ 10632@0, "str" ]
[ 10633@0, "oid" ]
[ 10633@0, "void" ]
[ 10634@0, "<predefinition>" ]
[ 10635@0, "str" ]
[ 10635@0, "void" ]
[ 10636@0, "BAT[any::1,any::2]" ]
[ 10636@0, "str" ]
[ 10636@0, "BAT[any::1,any::2]" ]
[ 10637@0, "BAT[any::1,any::2]" ]
[ 10637@0, "str" ]
[ 10637@0, "BAT[any::1,any::2]" ]
[ 10638@0, "void" ]
[ 10639@0, "void" ]
[ 10640@0, "void" ]
[ 10641@0, "str" ]
[ 10641@0, "void" ]
[ 10642@0, "BAT[int,str]" ]
[ 10642@0, "any" ]
[ 10643@0, "void" ]
[ 10644@0, "str" ]
[ 10644@0, "void" ]
[ 10645@0, "any" ]
[ 10646@0, "void" ]
[ 10647@0, "str" ]
[ 10647@0, "void" ]
[ 10648@0, "void" ]
[ 10649@0, "void" ]
[ 10650@0, "void" ]
[ 10651@0, "void" ]
[ 10652@0, "void" ]
[ 10653@0, "void" ]
[ 10654@0, "BAT[str,str]" ]
[ 10655@0, "BAT[str,int]" ]
[ 10656@0, "BAT[str,int]" ]
[ 10657@0, "BAT[str,int]" ]
[ 10658@0, "BAT[str,int]" ]
[ 10659@0, "BAT[any::1,any::2]" ]
[ 10659@0, "int" ]
[ 10659@0, "BAT[any::1,any::2]" ]
[ 10660@0, "BAT[any::1,any::2]" ]
[ 10660@0, "int" ]
[ 10661@0, "BAT[str,lng]" ]
[ 10662@0, "BAT[str,lng]" ]
[ 10663@0, "int" ]
[ 10663@0, "BAT[str,lng]" ]
[ 10664@0, "int" ]
[ 10664@0, "BAT[str,lng]" ]
[ 10667@0, "void" ]
[ 10668@0, "void" ]
[ 10669@0, "void" ]
[ 10670@0, "BAT[any,any]" ]
[ 10670@0, "*BAT[any,any]" ]
[ 10670@0, "void" ]
[ 10671@0, "BAT[any,any]" ]
[ 10671@0, "*BAT[any,any]" ]
[ 10671@0, "void" ]
[ 10672@0, "BAT[any,any]" ]
[ 10672@0, "*BAT[any,any]" ]
[ 10672@0, "void" ]
[ 10673@0, "BAT[any::1,any::2]" ]
[ 10673@0, "BAT[any::1,any::2]" ]
[ 10674@0, "BAT[any::1,any::2]" ]
[ 10674@0, "BAT[any::1,any::2]" ]
[ 10677@0, "BAT[void,dbl]" ]
[ 10677@0, "BAT[void,dbl]" ]
[ 10677@0, "BAT[void,dbl]" ]
[ 10677@0, "BAT[void,dbl]" ]
[ 10678@0, "BAT[void,dbl]" ]
[ 10678@0, "BAT[void,dbl]" ]
[ 10678@0, "BAT[void,dbl]" ]
[ 10678@0, "BAT[void,dbl]" ]
[ 10679@0, "dbl" ]
[ 10679@0, "BAT[void,dbl]" ]
[ 10679@0, "BAT[void,dbl]" ]
[ 10679@0, "BAT[void,dbl]" ]
[ 10680@0, "dbl" ]
[ 10680@0, "dbl" ]
[ 10680@0, "dbl" ]
[ 10680@0, "dbl" ]
[ 10690@0, "int" ]
[ 10690@0, "void" ]
[ 10691@0, "int" ]
[ 10691@0, "str" ]
[ 10691@0, "void" ]
[ 10692@0, "BAT[str,str]" ]
[ 10693@0, "int" ]
[ 10694@0, "int" ]
[ 10695@0, "int" ]
[ 10696@0, "str" ]
[ 10697@0, "void" ]
[ 10699@0, "dbl" ]
[ 10699@0, "dbl" ]
[ 10700@0, "dbl" ]
[ 10700@0, "dbl" ]
[ 10701@0, "dbl" ]
[ 10701@0, "dbl" ]
[ 10702@0, "dbl" ]
[ 10702@0, "dbl" ]
[ 10702@0, "dbl" ]
[ 10703@0, "dbl" ]
[ 10703@0, "dbl" ]
[ 10704@0, "dbl" ]
[ 10704@0, "dbl" ]
[ 10705@0, "dbl" ]
[ 10705@0, "dbl" ]
[ 10706@0, "dbl" ]
[ 10706@0, "dbl" ]
[ 10707@0, "dbl" ]
[ 10707@0, "dbl" ]
[ 10708@0, "dbl" ]
[ 10708@0, "dbl" ]
[ 10709@0, "dbl" ]
[ 10709@0, "dbl" ]
[ 10710@0, "dbl" ]
[ 10710@0, "dbl" ]
[ 10711@0, "dbl" ]
[ 10711@0, "dbl" ]
[ 10712@0, "dbl" ]
[ 10712@0, "dbl" ]
[ 10712@0, "dbl" ]
[ 10713@0, "dbl" ]
[ 10713@0, "dbl" ]
[ 10714@0, "dbl" ]
[ 10714@0, "dbl" ]
[ 10715@0, "dbl" ]
[ 10715@0, "dbl" ]
[ 10716@0, "dbl" ]
[ 10716@0, "dbl" ]
[ 10717@0, "dbl" ]
[ 10717@0, "dbl" ]
[ 10717@0, "dbl" ]
[ 10718@0, "dbl" ]
[ 10718@0, "int" ]
[ 10718@0, "dbl" ]
[ 10719@0, "dbl" ]
[ 10719@0, "bit" ]
[ 10720@0, "dbl" ]
[ 10720@0, "int" ]
[ 10721@0, "dbl" ]
[ 10721@0, "bit" ]
[ 10722@0, "flt" ]
[ 10722@0, "flt" ]
[ 10723@0, "flt" ]
[ 10723@0, "flt" ]
[ 10724@0, "flt" ]
[ 10724@0, "flt" ]
[ 10725@0, "flt" ]
[ 10725@0, "flt" ]
[ 10726@0, "flt" ]
[ 10726@0, "flt" ]
[ 10727@0, "flt" ]
[ 10727@0, "flt" ]
[ 10728@0, "flt" ]
[ 10728@0, "flt" ]
[ 10729@0, "flt" ]
[ 10729@0, "flt" ]
[ 10730@0, "flt" ]
[ 10730@0, "flt" ]
[ 10731@0, "flt" ]
[ 10731@0, "flt" ]
[ 10732@0, "flt" ]
[ 10732@0, "flt" ]
[ 10733@0, "flt" ]
[ 10733@0, "flt" ]
[ 10734@0, "flt" ]
[ 10734@0, "flt" ]
[ 10735@0, "flt" ]
[ 10735@0, "flt" ]
[ 10736@0, "flt" ]
[ 10736@0, "flt" ]
[ 10737@0, "void" ]
[ 10738@0, "void" ]
[ 10741@0, "Stream" ]
[ 10742@0, "Stream" ]
[ 10743@0, "Stream" ]
[ 10744@0, "str" ]
[ 10744@0, "Stream" ]
[ 10745@0, "str" ]
[ 10745@0, "Stream" ]
[ 10746@0, "str" ]
[ 10746@0, "Stream" ]
[ 10747@0, "str" ]
[ 10747@0, "Stream" ]
[ 10748@0, "Stream" ]
[ 10748@0, "Stream" ]
[ 10749@0, "Stream" ]
[ 10749@0, "Stream" ]
[ 10750@0, "int" ]
[ 10750@0, "str" ]
[ 10750@0, "Stream" ]
[ 10751@0, "int" ]
[ 10751@0, "str" ]
[ 10751@0, "Stream" ]
[ 10752@0, "int" ]
[ 10752@0, "str" ]
[ 10752@0, "Stream" ]
[ 10753@0, "int" ]
[ 10753@0, "str" ]
[ 10753@0, "Stream" ]
[ 10754@0, "Stream" ]
[ 10754@0, "Stream" ]
[ 10755@0, "Stream" ]
[ 10755@0, "str" ]
[ 10755@0, "void" ]
[ 10756@0, "Stream" ]
[ 10756@0, "int" ]
[ 10756@0, "void" ]
[ 10757@0, "Stream" ]
[ 10757@0, "int" ]
[ 10758@0, "Stream" ]
[ 10758@0, "str" ]
[ 10759@0, "Stream" ]
[ 10759@0, "void" ]
[ 10760@0, "Stream" ]
[ 10760@0, "void" ]
[ 10761@0, "Stream" ]
[ 10761@0, "int" ]
[ 10761@0, "Bstream" ]
[ 10762@0, "Bstream" ]
[ 10762@0, "void" ]
[ 10763@0, "Bstream" ]
[ 10763@0, "int" ]
[ 10763@0, "int" ]
[ 10764@0, "Stream" ]
[ 10764@0, "str" ]
[ 10764@0, "*any" ]
[ 10764@0, "void" ]
[ 10765@0, "Stream" ]
[ 10765@0, "*BAT[any::1,any]" ]
[ 10765@0, "void" ]
[ 10766@0, "Stream" ]
[ 10766@0, "int" ]
[ 10766@0, "*BAT[any::1,any]" ]
[ 10766@0, "void" ]
[ 10767@0, "Stream" ]
[ 10767@0, "str" ]
[ 10767@0, "int" ]
[ 10767@0, "void" ]
[ 10768@0, "Stream" ]
[ 10768@0, "str" ]
[ 10769@0, "Stream" ]
[ 10769@0, "int" ]
[ 10770@0, "str" ]
[ 10770@0, "Stream" ]
[ 10770@0, "void" ]
[ 10771@0, "Stream" ]
[ 10771@0, "void" ]
[ 10772@0, "Stream" ]
[ 10772@0, "void" ]
[ 10773@0, "str" ]
[ 10773@0, "str" ]
[ 10773@0, "Stream" ]
[ 10774@0, "void" ]
[ 10776@0, "int" ]
[ 10776@0, "void" ]
[ 10777@0, "BAT[void,str]" ]
[ 10777@0, "BAT[void,str]" ]
[ 10777@0, "BAT[void,str]" ]
[ 10777@0, "str" ]
[ 10777@0, "int" ]
[ 10777@0, "BAT[str,BAT]" ]
[ 10778@0, "BAT[void,str]" ]
[ 10778@0, "BAT[void,str]" ]
[ 10778@0, "BAT[void,str]" ]
[ 10778@0, "Stream" ]
[ 10778@0, "int" ]
[ 10778@0, "BAT[str,BAT]" ]
[ 10779@0, "BAT[void,str]" ]
[ 10779@0, "BAT[void,str]" ]
[ 10779@0, "BAT[void,BAT]" ]
[ 10779@0, "str" ]
[ 10779@0, "int" ]
[ 10779@0, "void" ]
[ 10780@0, "BAT[any,any]" ]
[ 10780@0, "BAT[void,str]" ]
[ 10780@0, "BAT[void,BAT]" ]
[ 10780@0, "Stream" ]
[ 10780@0, "void" ]
[ 10781@0, "str" ]
[ 10781@0, "BAT[str,BAT]" ]
[ 10782@0, "BAT[str,BAT]" ]
[ 10782@0, "str" ]
[ 10782@0, "int" ]
[ 10782@0, "BAT[str,BAT]" ]
[ 10783@0, "BAT[str,BAT]" ]
[ 10783@0, "any" ]
[ 10784@0, "BAT[str,BAT]" ]
[ 10784@0, "any" ]
[ 10785@0, "BAT[void,BAT]" ]
[ 10785@0, "BAT[void,str]" ]
[ 10786@0, "BAT[any,any]" ]
[ 10786@0, "str" ]
[ 10787@0, "BAT[void,BAT]" ]
[ 10787@0, "str" ]
[ 10787@0, "BAT[str,BAT]" ]
[ 10788@0, "BAT[str,BAT]" ]
[ 10788@0, "str" ]
[ 10788@0, "int" ]
[ 10788@0, "any" ]
[ 10789@0, "BAT[str,BAT]" ]
[ 10789@0, "BAT[str,BAT]" ]
[ 10789@0, "str" ]
[ 10789@0, "int" ]
[ 10789@0, "any" ]
[ 10790@0, "BAT[any,any]" ]
[ 10790@0, "str" ]
[ 10790@0, "BAT[any,any]" ]
[ 10791@0, "BAT[any,any]" ]
[ 10791@0, "str" ]
[ 10791@0, "any" ]
[ 10792@0, "void" ]
[ 10794@0, "BAT[void,sht]" ]
[ 10794@0, "BAT[void,sht]" ]
[ 10794@0, "BAT[void,sht]" ]
[ 10795@0, "sht" ]
[ 10795@0, "BAT[void,sht]" ]
[ 10795@0, "BAT[void,sht]" ]
[ 10796@0, "BAT[void,sht]" ]
[ 10796@0, "sht" ]
[ 10796@0, "BAT[void,sht]" ]
[ 10797@0, "BAT[void,sht]" ]
[ 10797@0, "BAT[void,sht]" ]
[ 10797@0, "BAT[void,sht]" ]
[ 10798@0, "sht" ]
[ 10798@0, "BAT[void,sht]" ]
[ 10798@0, "BAT[void,sht]" ]
[ 10799@0, "BAT[void,sht]" ]
[ 10799@0, "sht" ]
[ 10799@0, "BAT[void,sht]" ]
[ 10800@0, "BAT[void,sht]" ]
[ 10800@0, "BAT[void,sht]" ]
[ 10800@0, "BAT[void,sht]" ]
[ 10801@0, "sht" ]
[ 10801@0, "BAT[void,sht]" ]
[ 10801@0, "BAT[void,sht]" ]
[ 10802@0, "BAT[void,sht]" ]
[ 10802@0, "sht" ]
[ 10802@0, "BAT[void,sht]" ]
[ 10803@0, "BAT[void,sht]" ]
[ 10803@0, "BAT[void,sht]" ]
[ 10803@0, "BAT[void,sht]" ]
[ 10804@0, "sht" ]
[ 10804@0, "BAT[void,sht]" ]
[ 10804@0, "BAT[void,sht]" ]
[ 10805@0, "BAT[void,sht]" ]
[ 10805@0, "sht" ]
[ 10805@0, "BAT[void,sht]" ]
[ 10806@0, "BAT[void,sht]" ]
[ 10806@0, "BAT[void,sht]" ]
[ 10806@0, "BAT[void,sht]" ]
[ 10807@0, "sht" ]
[ 10807@0, "BAT[void,sht]" ]
[ 10807@0, "BAT[void,sht]" ]
[ 10808@0, "BAT[void,sht]" ]
[ 10808@0, "sht" ]
[ 10808@0, "BAT[void,sht]" ]
[ 10809@0, "BAT[void,sht]" ]
[ 10809@0, "BAT[void,sht]" ]
[ 10809@0, "BAT[void,sht]" ]
[ 10810@0, "sht" ]
[ 10810@0, "BAT[void,sht]" ]
[ 10810@0, "BAT[void,sht]" ]
[ 10811@0, "BAT[void,sht]" ]
[ 10811@0, "sht" ]
[ 10811@0, "BAT[void,sht]" ]
[ 10812@0, "BAT[void,sht]" ]
[ 10812@0, "BAT[void,sht]" ]
[ 10812@0, "BAT[void,sht]" ]
[ 10813@0, "sht" ]
[ 10813@0, "BAT[void,sht]" ]
[ 10813@0, "BAT[void,sht]" ]
[ 10814@0, "BAT[void,sht]" ]
[ 10814@0, "sht" ]
[ 10814@0, "BAT[void,sht]" ]
[ 10815@0, "BAT[void,sht]" ]
[ 10815@0, "BAT[void,sht]" ]
[ 10815@0, "BAT[void,sht]" ]
[ 10816@0, "sht" ]
[ 10816@0, "BAT[void,sht]" ]
[ 10816@0, "BAT[void,sht]" ]
[ 10817@0, "BAT[void,sht]" ]
[ 10817@0, "sht" ]
[ 10817@0, "BAT[void,sht]" ]
[ 10818@0, "BAT[void,sht]" ]
[ 10818@0, "BAT[void,sht]" ]
[ 10818@0, "BAT[void,sht]" ]
[ 10819@0, "sht" ]
[ 10819@0, "BAT[void,sht]" ]
[ 10819@0, "BAT[void,sht]" ]
[ 10820@0, "BAT[void,sht]" ]
[ 10820@0, "sht" ]
[ 10820@0, "BAT[void,sht]" ]
[ 10821@0, "BAT[void,sht]" ]
[ 10821@0, "BAT[void,sht]" ]
[ 10821@0, "BAT[void,sht]" ]
[ 10822@0, "sht" ]
[ 10822@0, "BAT[void,sht]" ]
[ 10822@0, "BAT[void,sht]" ]
[ 10823@0, "BAT[void,sht]" ]
[ 10823@0, "sht" ]
[ 10823@0, "BAT[void,sht]" ]
[ 10824@0, "BAT[void,int]" ]
[ 10824@0, "BAT[void,int]" ]
[ 10824@0, "BAT[void,int]" ]
[ 10825@0, "int" ]
[ 10825@0, "BAT[void,int]" ]
[ 10825@0, "BAT[void,int]" ]
[ 10826@0, "BAT[void,int]" ]
[ 10826@0, "int" ]
[ 10826@0, "BAT[void,int]" ]
[ 10827@0, "BAT[void,int]" ]
[ 10827@0, "BAT[void,int]" ]
[ 10827@0, "BAT[void,int]" ]
[ 10828@0, "int" ]
[ 10828@0, "BAT[void,int]" ]
[ 10828@0, "BAT[void,int]" ]
[ 10829@0, "BAT[void,int]" ]
[ 10829@0, "int" ]
[ 10829@0, "BAT[void,int]" ]
[ 10830@0, "BAT[void,int]" ]
[ 10830@0, "BAT[void,int]" ]
[ 10830@0, "BAT[void,int]" ]
[ 10831@0, "int" ]
[ 10831@0, "BAT[void,int]" ]
[ 10831@0, "BAT[void,int]" ]
[ 10832@0, "BAT[void,int]" ]
[ 10832@0, "int" ]
[ 10832@0, "BAT[void,int]" ]
[ 10833@0, "BAT[void,int]" ]
[ 10833@0, "BAT[void,int]" ]
[ 10833@0, "BAT[void,int]" ]
[ 10834@0, "int" ]
[ 10834@0, "BAT[void,int]" ]
[ 10834@0, "BAT[void,int]" ]
[ 10835@0, "BAT[void,int]" ]
[ 10835@0, "int" ]
[ 10835@0, "BAT[void,int]" ]
[ 10836@0, "BAT[void,int]" ]
[ 10836@0, "BAT[void,int]" ]
[ 10836@0, "BAT[void,int]" ]
[ 10837@0, "int" ]
[ 10837@0, "BAT[void,int]" ]
[ 10837@0, "BAT[void,int]" ]
[ 10838@0, "BAT[void,int]" ]
[ 10838@0, "int" ]
[ 10838@0, "BAT[void,int]" ]
[ 10839@0, "BAT[void,int]" ]
[ 10839@0, "BAT[void,int]" ]
[ 10839@0, "BAT[void,int]" ]
[ 10840@0, "int" ]
[ 10840@0, "BAT[void,int]" ]
[ 10840@0, "BAT[void,int]" ]
[ 10841@0, "BAT[void,int]" ]
[ 10841@0, "int" ]
[ 10841@0, "BAT[void,int]" ]
[ 10842@0, "BAT[void,int]" ]
[ 10842@0, "BAT[void,int]" ]
[ 10842@0, "BAT[void,int]" ]
[ 10843@0, "int" ]
[ 10843@0, "BAT[void,int]" ]
[ 10843@0, "BAT[void,int]" ]
[ 10844@0, "BAT[void,int]" ]
[ 10844@0, "int" ]
[ 10844@0, "BAT[void,int]" ]
[ 10845@0, "BAT[void,int]" ]
[ 10845@0, "BAT[void,int]" ]
[ 10845@0, "BAT[void,int]" ]
[ 10846@0, "int" ]
[ 10846@0, "BAT[void,int]" ]
[ 10846@0, "BAT[void,int]" ]
[ 10847@0, "BAT[void,int]" ]
[ 10847@0, "int" ]
[ 10847@0, "BAT[void,int]" ]
[ 10848@0, "BAT[void,int]" ]
[ 10848@0, "BAT[void,int]" ]
[ 10848@0, "BAT[void,int]" ]
[ 10849@0, "int" ]
[ 10849@0, "BAT[void,int]" ]
[ 10849@0, "BAT[void,int]" ]
[ 10850@0, "BAT[void,int]" ]
[ 10850@0, "int" ]
[ 10850@0, "BAT[void,int]" ]
[ 10851@0, "BAT[void,int]" ]
[ 10851@0, "BAT[void,int]" ]
[ 10851@0, "BAT[void,int]" ]
[ 10852@0, "int" ]
[ 10852@0, "BAT[void,int]" ]
[ 10852@0, "BAT[void,int]" ]
[ 10853@0, "BAT[void,int]" ]
[ 10853@0, "int" ]
[ 10853@0, "BAT[void,int]" ]
[ 10854@0, "BAT[void,lng]" ]
[ 10854@0, "BAT[void,lng]" ]
[ 10854@0, "BAT[void,lng]" ]
[ 10855@0, "lng" ]
[ 10855@0, "BAT[void,lng]" ]
[ 10855@0, "BAT[void,lng]" ]
[ 10856@0, "BAT[void,lng]" ]
[ 10856@0, "lng" ]
[ 10856@0, "BAT[void,lng]" ]
[ 10857@0, "BAT[void,lng]" ]
[ 10857@0, "BAT[void,lng]" ]
[ 10857@0, "BAT[void,lng]" ]
[ 10858@0, "lng" ]
[ 10858@0, "BAT[void,lng]" ]
[ 10858@0, "BAT[void,lng]" ]
[ 10859@0, "BAT[void,lng]" ]
[ 10859@0, "lng" ]
[ 10859@0, "BAT[void,lng]" ]
[ 10860@0, "BAT[void,lng]" ]
[ 10860@0, "BAT[void,lng]" ]
[ 10860@0, "BAT[void,lng]" ]
[ 10861@0, "lng" ]
[ 10861@0, "BAT[void,lng]" ]
[ 10861@0, "BAT[void,lng]" ]
[ 10862@0, "BAT[void,lng]" ]
[ 10862@0, "lng" ]
[ 10862@0, "BAT[void,lng]" ]
[ 10863@0, "BAT[void,lng]" ]
[ 10863@0, "BAT[void,lng]" ]
[ 10863@0, "BAT[void,lng]" ]
[ 10864@0, "lng" ]
[ 10864@0, "BAT[void,lng]" ]
[ 10864@0, "BAT[void,lng]" ]
[ 10865@0, "BAT[void,lng]" ]
[ 10865@0, "lng" ]
[ 10865@0, "BAT[void,lng]" ]
[ 10866@0, "BAT[void,lng]" ]
[ 10866@0, "BAT[void,lng]" ]
[ 10866@0, "BAT[void,lng]" ]
[ 10867@0, "lng" ]
[ 10867@0, "BAT[void,lng]" ]
[ 10867@0, "BAT[void,lng]" ]
[ 10868@0, "BAT[void,lng]" ]
[ 10868@0, "lng" ]
[ 10868@0, "BAT[void,lng]" ]
[ 10869@0, "BAT[void,lng]" ]
[ 10869@0, "BAT[void,lng]" ]
[ 10869@0, "BAT[void,lng]" ]
[ 10870@0, "lng" ]
[ 10870@0, "BAT[void,lng]" ]
[ 10870@0, "BAT[void,lng]" ]
[ 10871@0, "BAT[void,lng]" ]
[ 10871@0, "lng" ]
[ 10871@0, "BAT[void,lng]" ]
[ 10872@0, "BAT[void,lng]" ]
[ 10872@0, "BAT[void,lng]" ]
[ 10872@0, "BAT[void,lng]" ]
[ 10873@0, "lng" ]
[ 10873@0, "BAT[void,lng]" ]
[ 10873@0, "BAT[void,lng]" ]
[ 10874@0, "BAT[void,lng]" ]
[ 10874@0, "lng" ]
[ 10874@0, "BAT[void,lng]" ]
[ 10875@0, "BAT[void,lng]" ]
[ 10875@0, "BAT[void,lng]" ]
[ 10875@0, "BAT[void,lng]" ]
[ 10876@0, "lng" ]
[ 10876@0, "BAT[void,lng]" ]
[ 10876@0, "BAT[void,lng]" ]
[ 10877@0, "BAT[void,lng]" ]
[ 10877@0, "lng" ]
[ 10877@0, "BAT[void,lng]" ]
[ 10878@0, "BAT[void,lng]" ]
[ 10878@0, "BAT[void,lng]" ]
[ 10878@0, "BAT[void,lng]" ]
[ 10879@0, "lng" ]
[ 10879@0, "BAT[void,lng]" ]
[ 10879@0, "BAT[void,lng]" ]
[ 10880@0, "BAT[void,lng]" ]
[ 10880@0, "lng" ]
[ 10880@0, "BAT[void,lng]" ]
[ 10881@0, "BAT[void,lng]" ]
[ 10881@0, "BAT[void,lng]" ]
[ 10881@0, "BAT[void,lng]" ]
[ 10882@0, "lng" ]
[ 10882@0, "BAT[void,lng]" ]
[ 10882@0, "BAT[void,lng]" ]
[ 10883@0, "BAT[void,lng]" ]
[ 10883@0, "lng" ]
[ 10883@0, "BAT[void,lng]" ]
[ 10884@0, "BAT[void,flt]" ]
[ 10884@0, "BAT[void,flt]" ]
[ 10884@0, "BAT[void,flt]" ]
[ 10885@0, "flt" ]
[ 10885@0, "BAT[void,flt]" ]
[ 10885@0, "BAT[void,flt]" ]
[ 10886@0, "BAT[void,flt]" ]
[ 10886@0, "flt" ]
[ 10886@0, "BAT[void,flt]" ]
[ 10887@0, "BAT[void,flt]" ]
[ 10887@0, "BAT[void,flt]" ]
[ 10887@0, "BAT[void,flt]" ]
[ 10888@0, "flt" ]
[ 10888@0, "BAT[void,flt]" ]
[ 10888@0, "BAT[void,flt]" ]
[ 10889@0, "BAT[void,flt]" ]
[ 10889@0, "flt" ]
[ 10889@0, "BAT[void,flt]" ]
[ 10890@0, "BAT[void,flt]" ]
[ 10890@0, "BAT[void,flt]" ]
[ 10890@0, "BAT[void,flt]" ]
[ 10891@0, "flt" ]
[ 10891@0, "BAT[void,flt]" ]
[ 10891@0, "BAT[void,flt]" ]
[ 10892@0, "BAT[void,flt]" ]
[ 10892@0, "flt" ]
[ 10892@0, "BAT[void,flt]" ]
[ 10893@0, "BAT[void,flt]" ]
[ 10893@0, "BAT[void,flt]" ]
[ 10893@0, "BAT[void,flt]" ]
[ 10894@0, "flt" ]
[ 10894@0, "BAT[void,flt]" ]
[ 10894@0, "BAT[void,flt]" ]
[ 10895@0, "BAT[void,flt]" ]
[ 10895@0, "flt" ]
[ 10895@0, "BAT[void,flt]" ]
[ 10896@0, "BAT[void,flt]" ]
[ 10896@0, "BAT[void,flt]" ]
[ 10896@0, "BAT[void,flt]" ]
[ 10897@0, "flt" ]
[ 10897@0, "BAT[void,flt]" ]
[ 10897@0, "BAT[void,flt]" ]
[ 10898@0, "BAT[void,flt]" ]
[ 10898@0, "flt" ]
[ 10898@0, "BAT[void,flt]" ]
[ 10899@0, "BAT[void,flt]" ]
[ 10899@0, "BAT[void,flt]" ]
[ 10899@0, "BAT[void,flt]" ]
[ 10900@0, "flt" ]
[ 10900@0, "BAT[void,flt]" ]
[ 10900@0, "BAT[void,flt]" ]
[ 10901@0, "BAT[void,flt]" ]
[ 10901@0, "flt" ]
[ 10901@0, "BAT[void,flt]" ]
[ 10902@0, "BAT[void,flt]" ]
[ 10902@0, "BAT[void,flt]" ]
[ 10902@0, "BAT[void,flt]" ]
[ 10903@0, "flt" ]
[ 10903@0, "BAT[void,flt]" ]
[ 10903@0, "BAT[void,flt]" ]
[ 10904@0, "BAT[void,flt]" ]
[ 10904@0, "flt" ]
[ 10904@0, "BAT[void,flt]" ]
[ 10905@0, "BAT[void,flt]" ]
[ 10905@0, "BAT[void,flt]" ]
[ 10905@0, "BAT[void,flt]" ]
[ 10906@0, "flt" ]
[ 10906@0, "BAT[void,flt]" ]
[ 10906@0, "BAT[void,flt]" ]
[ 10907@0, "BAT[void,flt]" ]
[ 10907@0, "flt" ]
[ 10907@0, "BAT[void,flt]" ]
[ 10908@0, "BAT[void,dbl]" ]
[ 10908@0, "BAT[void,dbl]" ]
[ 10908@0, "BAT[void,dbl]" ]
[ 10909@0, "dbl" ]
[ 10909@0, "BAT[void,dbl]" ]
[ 10909@0, "BAT[void,dbl]" ]
[ 10910@0, "BAT[void,dbl]" ]
[ 10910@0, "dbl" ]
[ 10910@0, "BAT[void,dbl]" ]
[ 10911@0, "BAT[void,dbl]" ]
[ 10911@0, "BAT[void,dbl]" ]
[ 10911@0, "BAT[void,dbl]" ]
[ 10912@0, "dbl" ]
[ 10912@0, "BAT[void,dbl]" ]
[ 10912@0, "BAT[void,dbl]" ]
[ 10913@0, "BAT[void,dbl]" ]
[ 10913@0, "dbl" ]
[ 10913@0, "BAT[void,dbl]" ]
[ 10914@0, "BAT[void,dbl]" ]
[ 10914@0, "BAT[void,dbl]" ]
[ 10914@0, "BAT[void,dbl]" ]
[ 10915@0, "dbl" ]
[ 10915@0, "BAT[void,dbl]" ]
[ 10915@0, "BAT[void,dbl]" ]
[ 10916@0, "BAT[void,dbl]" ]
[ 10916@0, "dbl" ]
[ 10916@0, "BAT[void,dbl]" ]
[ 10917@0, "BAT[void,dbl]" ]
[ 10917@0, "BAT[void,dbl]" ]
[ 10917@0, "BAT[void,dbl]" ]
[ 10918@0, "dbl" ]
[ 10918@0, "BAT[void,dbl]" ]
[ 10918@0, "BAT[void,dbl]" ]
[ 10919@0, "BAT[void,dbl]" ]
[ 10919@0, "dbl" ]
[ 10919@0, "BAT[void,dbl]" ]
[ 10920@0, "BAT[void,dbl]" ]
[ 10920@0, "BAT[void,dbl]" ]
[ 10920@0, "BAT[void,dbl]" ]
[ 10921@0, "dbl" ]
[ 10921@0, "BAT[void,dbl]" ]
[ 10921@0, "BAT[void,dbl]" ]
[ 10922@0, "BAT[void,dbl]" ]
[ 10922@0, "dbl" ]
[ 10922@0, "BAT[void,dbl]" ]
[ 10923@0, "BAT[void,dbl]" ]
[ 10923@0, "BAT[void,dbl]" ]
[ 10923@0, "BAT[void,dbl]" ]
[ 10924@0, "dbl" ]
[ 10924@0, "BAT[void,dbl]" ]
[ 10924@0, "BAT[void,dbl]" ]
[ 10925@0, "BAT[void,dbl]" ]
[ 10925@0, "dbl" ]
[ 10925@0, "BAT[void,dbl]" ]
[ 10926@0, "BAT[void,dbl]" ]
[ 10926@0, "BAT[void,dbl]" ]
[ 10926@0, "BAT[void,dbl]" ]
[ 10927@0, "dbl" ]
[ 10927@0, "BAT[void,dbl]" ]
[ 10927@0, "BAT[void,dbl]" ]
[ 10928@0, "BAT[void,dbl]" ]
[ 10928@0, "dbl" ]
[ 10928@0, "BAT[void,dbl]" ]
[ 10929@0, "BAT[void,dbl]" ]
[ 10929@0, "BAT[void,dbl]" ]
[ 10929@0, "BAT[void,dbl]" ]
[ 10930@0, "dbl" ]
[ 10930@0, "BAT[void,dbl]" ]
[ 10930@0, "BAT[void,dbl]" ]
[ 10931@0, "BAT[void,dbl]" ]
[ 10931@0, "dbl" ]
[ 10931@0, "BAT[void,dbl]" ]
[ 10933@0, "BAT[void,dbl]" ]
[ 10933@0, "BAT[void,dbl]" ]
[ 10934@0, "BAT[void,dbl]" ]
[ 10934@0, "BAT[void,dbl]" ]
[ 10935@0, "BAT[void,dbl]" ]
[ 10935@0, "BAT[void,dbl]" ]
[ 10936@0, "BAT[void,dbl]" ]
[ 10936@0, "BAT[void,dbl]" ]
[ 10936@0, "BAT[void,dbl]" ]
[ 10937@0, "dbl" ]
[ 10937@0, "BAT[void,dbl]" ]
[ 10937@0, "BAT[void,dbl]" ]
[ 10938@0, "BAT[void,dbl]" ]
[ 10938@0, "dbl" ]
[ 10938@0, "BAT[void,dbl]" ]
[ 10940@0, "lock" ]
[ 10941@0, "lock" ]
[ 10941@0, "void" ]
[ 10942@0, "lock" ]
[ 10942@0, "int" ]
[ 10943@0, "lock" ]
[ 10943@0, "void" ]
[ 10944@0, "lock" ]
[ 10944@0, "void" ]
[ 10945@0, "int" ]
[ 10945@0, "sema" ]
[ 10946@0, "sema" ]
[ 10946@0, "void" ]
[ 10947@0, "sema" ]
[ 10947@0, "int" ]
[ 10948@0, "sema" ]
[ 10948@0, "void" ]
[ 10949@0, "sema" ]
[ 10949@0, "void" ]
[ 10951@0, "BAT[any::1,any::2]" ]
[ 10951@0, "str" ]
[ 10951@0, "flt" ]
[ 10951@0, "int" ]
[ 10951@0, "*int" ]
[ 10951@0, "BAT[any::1,any::2]" ]
[ 10952@0, "BAT[any,any]" ]
[ 10952@0, "int" ]
[ 10953@0, "BAT[oid,oid]" ]
[ 10953@0, "int" ]
[ 10953@0, "int" ]
[ 10953@0, "BAT[int,int]" ]
[ 10954@0, "BAT[any,oid]" ]
[ 10954@0, "int" ]
[ 10954@0, "int" ]
[ 10954@0, "BAT[int,int]" ]
[ 10955@0, "BAT[oid,any::1]" ]
[ 10955@0, "BAT[int,int]" ]
[ 10955@0, "int" ]
[ 10955@0, "BAT[void,any::1]" ]
[ 10956@0, "BAT[any::2,oid]" ]
[ 10956@0, "BAT[any::2,any::1]" ]
[ 10956@0, "BAT[int,int]" ]
[ 10956@0, "int" ]
[ 10956@0, "BAT[void,any::1]" ]
[ 10957@0, "BAT[any::2,oid]" ]
[ 10957@0, "BAT[any::2,any::1]" ]
[ 10957@0, "BAT[int,int]" ]
[ 10957@0, "int" ]
[ 10957@0, "BAT[void,any::1]" ]
[ 10958@0, "BAT[any::2,oid]" ]
[ 10958@0, "BAT[any::2,any::1]" ]
[ 10958@0, "BAT[int,int]" ]
[ 10958@0, "int" ]
[ 10958@0, "BAT[void,any::1]" ]
[ 10959@0, "BAT[any::1,any::2]" ]
[ 10959@0, "BAT[any::2,any::3]" ]
[ 10959@0, "int" ]
[ 10959@0, "int" ]
[ 10959@0, "BAT[any,any]" ]
[ 10960@0, "BAT[any::1,any::2]" ]
[ 10960@0, "BAT[any::2,any::3]" ]
[ 10960@0, "int" ]
[ 10960@0, "int" ]
[ 10960@0, "bit" ]
[ 10960@0, "BAT[any,any]" ]
[ 10961@0, "BAT[oid,oid]" ]
[ 10961@0, "BAT[void,any::1]" ]
[ 10961@0, "BAT[int,int]" ]
[ 10961@0, "int" ]
[ 10961@0, "int" ]
[ 10961@0, "BAT[void,any::1]" ]
[ 10962@0, "BAT[void,oid]" ]
[ 10962@0, "BAT[oid,oid]" ]
[ 10962@0, "BAT[void,any::1]" ]
[ 10962@0, "BAT[int,int]" ]
[ 10962@0, "int" ]
[ 10962@0, "int" ]
[ 10962@0, "BAT[void,any::1]" ]
[ 10963@0, "BAT[oid,oid]" ]
[ 10963@0, "BAT[void,any::1]" ]
[ 10963@0, "BAT[void,any::1]" ]
[ 10964@0, "BAT[any::1,integer1]" ]
[ 10964@0, "BAT[any::1,pax1]" ]
[ 10965@0, "BAT[any::1,integer1]" ]
[ 10965@0, "int" ]
[ 10965@0, "BAT[any::1,any]" ]
[ 10966@0, "BAT[any::1,integer2]" ]
[ 10966@0, "BAT[any::1,pax2]" ]
[ 10967@0, "BAT[any::1,integer2]" ]
[ 10967@0, "int" ]
[ 10967@0, "BAT[any::1,any]" ]
[ 10968@0, "BAT[any::1,integer4]" ]
[ 10968@0, "BAT[any::1,pax4]" ]
[ 10969@0, "BAT[any::1,integer4]" ]
[ 10969@0, "int" ]
[ 10969@0, "BAT[any::1,any]" ]
[ 10970@0, "BAT[any::1,integer8]" ]
[ 10970@0, "BAT[any::1,pax8]" ]
[ 10971@0, "BAT[any::1,integer8]" ]
[ 10971@0, "int" ]
[ 10971@0, "BAT[any::1,any]" ]
[ 10972@0, "BAT[any::1,integer16]" ]
[ 10972@0, "BAT[any::1,pax16]" ]
[ 10973@0, "BAT[any::1,integer16]" ]
[ 10973@0, "int" ]
[ 10973@0, "BAT[any::1,any]" ]
[ 10974@0, "BAT[any::1,integer32]" ]
[ 10974@0, "BAT[any::1,pax32]" ]
[ 10975@0, "BAT[any::1,integer32]" ]
[ 10975@0, "int" ]
[ 10975@0, "BAT[any::1,any]" ]
[ 10976@0, "BAT[any::1,integer64]" ]
[ 10976@0, "BAT[any::1,pax64]" ]
[ 10977@0, "BAT[any::1,integer64]" ]
[ 10977@0, "int" ]
[ 10977@0, "BAT[any::1,any]" ]
[ 10978@0, "BAT[any::1,integer128]" ]
[ 10978@0, "BAT[any::1,pax128]" ]
[ 10979@0, "BAT[any::1,integer128]" ]
[ 10979@0, "int" ]
[ 10979@0, "BAT[any::1,any]" ]
[ 10980@0, "BAT[any::1,integer256]" ]
[ 10980@0, "BAT[any::1,pax256]" ]
[ 10981@0, "BAT[any::1,integer256]" ]
[ 10981@0, "int" ]
[ 10981@0, "BAT[any::1,any]" ]
[ 10982@0, "BAT[any::1,integer1]" ]
[ 10982@0, "BAT[any::1,Int1]" ]
[ 10983@0, "BAT[void,oid]" ]
[ 10983@0, "BAT[oid,oid]" ]
[ 10983@0, "BAT[void,integer1]" ]
[ 10983@0, "BAT[int,int]" ]
[ 10983@0, "int" ]
[ 10983@0, "int" ]
[ 10983@0, "BAT[void,Int1]" ]
[ 10984@0, "BAT[void,oid]" ]
[ 10984@0, "BAT[oid,oid]" ]
[ 10984@0, "BAT[void,pax1]" ]
[ 10984@0, "BAT[int,int]" ]
[ 10984@0, "int" ]
[ 10984@0, "int" ]
[ 10984@0, "BAT[void,Int1]" ]
[ 10985@0, "BAT[oid,oid]" ]
[ 10985@0, "BAT[void,integer1]" ]
[ 10985@0, "BAT[void,Int1]" ]
[ 10986@0, "BAT[oid,oid]" ]
[ 10986@0, "BAT[void,pax1]" ]
[ 10986@0, "BAT[void,Int1]" ]
[ 10987@0, "BAT[void,oid]" ]
[ 10987@0, "BAT[void,integer1]" ]
[ 10987@0, "BAT[void,Int1]" ]
[ 10988@0, "BAT[void,oid]" ]
[ 10988@0, "BAT[void,pax1]" ]
[ 10988@0, "BAT[void,Int1]" ]
[ 10989@0, "BAT[integer1,any::2]" ]
[ 10989@0, "str" ]
[ 10989@0, "flt" ]
[ 10989@0, "int" ]
[ 10989@0, "*int" ]
[ 10989@0, "BAT[Int1,any::2]" ]
[ 10990@0, "BAT[pax1,any::2]" ]
[ 10990@0, "str" ]
[ 10990@0, "flt" ]
[ 10990@0, "int" ]
[ 10990@0, "*int" ]
[ 10990@0, "BAT[Int1,any::2]" ]
[ 10991@0, "BAT[any::1,integer2]" ]
[ 10991@0, "BAT[any::1,Int2]" ]
[ 10992@0, "BAT[void,oid]" ]
[ 10992@0, "BAT[oid,oid]" ]
[ 10992@0, "BAT[void,integer2]" ]
[ 10992@0, "BAT[int,int]" ]
[ 10992@0, "int" ]
[ 10992@0, "int" ]
[ 10992@0, "BAT[void,Int2]" ]
[ 10993@0, "BAT[void,oid]" ]
[ 10993@0, "BAT[oid,oid]" ]
[ 10993@0, "BAT[void,pax2]" ]
[ 10993@0, "BAT[int,int]" ]
[ 10993@0, "int" ]
[ 10993@0, "int" ]
[ 10993@0, "BAT[void,Int2]" ]
[ 10994@0, "BAT[oid,oid]" ]
[ 10994@0, "BAT[void,integer2]" ]
[ 10994@0, "BAT[void,Int2]" ]
[ 10995@0, "BAT[oid,oid]" ]
[ 10995@0, "BAT[void,pax2]" ]
[ 10995@0, "BAT[void,Int2]" ]
[ 10996@0, "BAT[void,oid]" ]
[ 10996@0, "BAT[void,integer2]" ]
[ 10996@0, "BAT[void,Int2]" ]
[ 10997@0, "BAT[void,oid]" ]
[ 10997@0, "BAT[void,pax2]" ]
[ 10997@0, "BAT[void,Int2]" ]
[ 10998@0, "BAT[integer2,any::2]" ]
[ 10998@0, "str" ]
[ 10998@0, "flt" ]
[ 10998@0, "int" ]
[ 10998@0, "*int" ]
[ 10998@0, "BAT[Int2,any::2]" ]
[ 10999@0, "BAT[pax2,any::2]" ]
[ 10999@0, "str" ]
[ 10999@0, "flt" ]
[ 10999@0, "int" ]
[ 10999@0, "*int" ]
[ 10999@0, "BAT[Int2,any::2]" ]
[ 11000@0, "BAT[any::1,integer4]" ]
[ 11000@0, "BAT[any::1,Int4]" ]
[ 11001@0, "BAT[void,oid]" ]
[ 11001@0, "BAT[oid,oid]" ]
[ 11001@0, "BAT[void,integer4]" ]
[ 11001@0, "BAT[int,int]" ]
[ 11001@0, "int" ]
[ 11001@0, "int" ]
[ 11001@0, "BAT[void,Int4]" ]
[ 11002@0, "BAT[void,oid]" ]
[ 11002@0, "BAT[oid,oid]" ]
[ 11002@0, "BAT[void,pax4]" ]
[ 11002@0, "BAT[int,int]" ]
[ 11002@0, "int" ]
[ 11002@0, "int" ]
[ 11002@0, "BAT[void,Int4]" ]
[ 11003@0, "BAT[oid,oid]" ]
[ 11003@0, "BAT[void,integer4]" ]
[ 11003@0, "BAT[void,Int4]" ]
[ 11004@0, "BAT[oid,oid]" ]
[ 11004@0, "BAT[void,pax4]" ]
[ 11004@0, "BAT[void,Int4]" ]
[ 11005@0, "BAT[void,oid]" ]
[ 11005@0, "BAT[void,integer4]" ]
[ 11005@0, "BAT[void,Int4]" ]
[ 11006@0, "BAT[void,oid]" ]
[ 11006@0, "BAT[void,pax4]" ]
[ 11006@0, "BAT[void,Int4]" ]
[ 11007@0, "BAT[integer4,any::2]" ]
[ 11007@0, "str" ]
[ 11007@0, "flt" ]
[ 11007@0, "int" ]
[ 11007@0, "*int" ]
[ 11007@0, "BAT[Int4,any::2]" ]
[ 11008@0, "BAT[pax4,any::2]" ]
[ 11008@0, "str" ]
[ 11008@0, "flt" ]
[ 11008@0, "int" ]
[ 11008@0, "*int" ]
[ 11008@0, "BAT[Int4,any::2]" ]
[ 11009@0, "BAT[any::1,integer8]" ]
[ 11009@0, "BAT[any::1,Int8]" ]
[ 11010@0, "BAT[void,oid]" ]
[ 11010@0, "BAT[oid,oid]" ]
[ 11010@0, "BAT[void,integer8]" ]
[ 11010@0, "BAT[int,int]" ]
[ 11010@0, "int" ]
[ 11010@0, "int" ]
[ 11010@0, "BAT[void,Int8]" ]
[ 11011@0, "BAT[void,oid]" ]
[ 11011@0, "BAT[oid,oid]" ]
[ 11011@0, "BAT[void,pax8]" ]
[ 11011@0, "BAT[int,int]" ]
[ 11011@0, "int" ]
[ 11011@0, "int" ]
[ 11011@0, "BAT[void,Int8]" ]
[ 11012@0, "BAT[oid,oid]" ]
[ 11012@0, "BAT[void,integer8]" ]
[ 11012@0, "BAT[void,Int8]" ]
[ 11013@0, "BAT[oid,oid]" ]
[ 11013@0, "BAT[void,pax8]" ]
[ 11013@0, "BAT[void,Int8]" ]
[ 11014@0, "BAT[void,oid]" ]
[ 11014@0, "BAT[void,integer8]" ]
[ 11014@0, "BAT[void,Int8]" ]
[ 11015@0, "BAT[void,oid]" ]
[ 11015@0, "BAT[void,pax8]" ]
[ 11015@0, "BAT[void,Int8]" ]
[ 11016@0, "BAT[integer8,any::2]" ]
[ 11016@0, "str" ]
[ 11016@0, "flt" ]
[ 11016@0, "int" ]
[ 11016@0, "*int" ]
[ 11016@0, "BAT[Int8,any::2]" ]
[ 11017@0, "BAT[pax8,any::2]" ]
[ 11017@0, "str" ]
[ 11017@0, "flt" ]
[ 11017@0, "int" ]
[ 11017@0, "*int" ]
[ 11017@0, "BAT[Int8,any::2]" ]
[ 11018@0, "BAT[any::1,integer16]" ]
[ 11018@0, "BAT[any::1,Int16]" ]
[ 11019@0, "BAT[void,oid]" ]
[ 11019@0, "BAT[oid,oid]" ]
[ 11019@0, "BAT[void,integer16]" ]
[ 11019@0, "BAT[int,int]" ]
[ 11019@0, "int" ]
[ 11019@0, "int" ]
[ 11019@0, "BAT[void,Int16]" ]
[ 11020@0, "BAT[void,oid]" ]
[ 11020@0, "BAT[oid,oid]" ]
[ 11020@0, "BAT[void,pax16]" ]
[ 11020@0, "BAT[int,int]" ]
[ 11020@0, "int" ]
[ 11020@0, "int" ]
[ 11020@0, "BAT[void,Int16]" ]
[ 11021@0, "BAT[oid,oid]" ]
[ 11021@0, "BAT[void,integer16]" ]
[ 11021@0, "BAT[void,Int16]" ]
[ 11022@0, "BAT[oid,oid]" ]
[ 11022@0, "BAT[void,pax16]" ]
[ 11022@0, "BAT[void,Int16]" ]
[ 11023@0, "BAT[void,oid]" ]
[ 11023@0, "BAT[void,integer16]" ]
[ 11023@0, "BAT[void,Int16]" ]
[ 11024@0, "BAT[void,oid]" ]
[ 11024@0, "BAT[void,pax16]" ]
[ 11024@0, "BAT[void,Int16]" ]
[ 11025@0, "BAT[integer16,any::2]" ]
[ 11025@0, "str" ]
[ 11025@0, "flt" ]
[ 11025@0, "int" ]
[ 11025@0, "*int" ]
[ 11025@0, "BAT[Int16,any::2]" ]
[ 11026@0, "BAT[pax16,any::2]" ]
[ 11026@0, "str" ]
[ 11026@0, "flt" ]
[ 11026@0, "int" ]
[ 11026@0, "*int" ]
[ 11026@0, "BAT[Int16,any::2]" ]
[ 11027@0, "BAT[any::1,integer32]" ]
[ 11027@0, "BAT[any::1,Int32]" ]
[ 11028@0, "BAT[void,oid]" ]
[ 11028@0, "BAT[oid,oid]" ]
[ 11028@0, "BAT[void,integer32]" ]
[ 11028@0, "BAT[int,int]" ]
[ 11028@0, "int" ]
[ 11028@0, "int" ]
[ 11028@0, "BAT[void,Int32]" ]
[ 11029@0, "BAT[void,oid]" ]
[ 11029@0, "BAT[oid,oid]" ]
[ 11029@0, "BAT[void,pax32]" ]
[ 11029@0, "BAT[int,int]" ]
[ 11029@0, "int" ]
[ 11029@0, "int" ]
[ 11029@0, "BAT[void,Int32]" ]
[ 11030@0, "BAT[oid,oid]" ]
[ 11030@0, "BAT[void,integer32]" ]
[ 11030@0, "BAT[void,Int32]" ]
[ 11031@0, "BAT[oid,oid]" ]
[ 11031@0, "BAT[void,pax32]" ]
[ 11031@0, "BAT[void,Int32]" ]
[ 11032@0, "BAT[void,oid]" ]
[ 11032@0, "BAT[void,integer32]" ]
[ 11032@0, "BAT[void,Int32]" ]
[ 11033@0, "BAT[void,oid]" ]
[ 11033@0, "BAT[void,pax32]" ]
[ 11033@0, "BAT[void,Int32]" ]
[ 11034@0, "BAT[integer32,any::2]" ]
[ 11034@0, "str" ]
[ 11034@0, "flt" ]
[ 11034@0, "int" ]
[ 11034@0, "*int" ]
[ 11034@0, "BAT[Int32,any::2]" ]
[ 11035@0, "BAT[pax32,any::2]" ]
[ 11035@0, "str" ]
[ 11035@0, "flt" ]
[ 11035@0, "int" ]
[ 11035@0, "*int" ]
[ 11035@0, "BAT[Int32,any::2]" ]
[ 11036@0, "BAT[any::1,integer64]" ]
[ 11036@0, "BAT[any::1,Int64]" ]
[ 11037@0, "BAT[void,oid]" ]
[ 11037@0, "BAT[oid,oid]" ]
[ 11037@0, "BAT[void,integer64]" ]
[ 11037@0, "BAT[int,int]" ]
[ 11037@0, "int" ]
[ 11037@0, "int" ]
[ 11037@0, "BAT[void,Int64]" ]
[ 11038@0, "BAT[void,oid]" ]
[ 11038@0, "BAT[oid,oid]" ]
[ 11038@0, "BAT[void,pax64]" ]
[ 11038@0, "BAT[int,int]" ]
[ 11038@0, "int" ]
[ 11038@0, "int" ]
[ 11038@0, "BAT[void,Int64]" ]
[ 11039@0, "BAT[oid,oid]" ]
[ 11039@0, "BAT[void,integer64]" ]
[ 11039@0, "BAT[void,Int64]" ]
[ 11040@0, "BAT[oid,oid]" ]
[ 11040@0, "BAT[void,pax64]" ]
[ 11040@0, "BAT[void,Int64]" ]
[ 11041@0, "BAT[void,oid]" ]
[ 11041@0, "BAT[void,integer64]" ]
[ 11041@0, "BAT[void,Int64]" ]
[ 11042@0, "BAT[void,oid]" ]
[ 11042@0, "BAT[void,pax64]" ]
[ 11042@0, "BAT[void,Int64]" ]
[ 11043@0, "BAT[integer64,any::2]" ]
[ 11043@0, "str" ]
[ 11043@0, "flt" ]
[ 11043@0, "int" ]
[ 11043@0, "*int" ]
[ 11043@0, "BAT[Int64,any::2]" ]
[ 11044@0, "BAT[pax64,any::2]" ]
[ 11044@0, "str" ]
[ 11044@0, "flt" ]
[ 11044@0, "int" ]
[ 11044@0, "*int" ]
[ 11044@0, "BAT[Int64,any::2]" ]
[ 11045@0, "BAT[any::1,integer128]" ]
[ 11045@0, "BAT[any::1,Int128]" ]
[ 11046@0, "BAT[void,oid]" ]
[ 11046@0, "BAT[oid,oid]" ]
[ 11046@0, "BAT[void,integer128]" ]
[ 11046@0, "BAT[int,int]" ]
[ 11046@0, "int" ]
[ 11046@0, "int" ]
[ 11046@0, "BAT[void,Int128]" ]
[ 11047@0, "BAT[void,oid]" ]
[ 11047@0, "BAT[oid,oid]" ]
[ 11047@0, "BAT[void,pax128]" ]
[ 11047@0, "BAT[int,int]" ]
[ 11047@0, "int" ]
[ 11047@0, "int" ]
[ 11047@0, "BAT[void,Int128]" ]
[ 11048@0, "BAT[oid,oid]" ]
[ 11048@0, "BAT[void,integer128]" ]
[ 11048@0, "BAT[void,Int128]" ]
[ 11049@0, "BAT[oid,oid]" ]
[ 11049@0, "BAT[void,pax128]" ]
[ 11049@0, "BAT[void,Int128]" ]
[ 11050@0, "BAT[void,oid]" ]
[ 11050@0, "BAT[void,integer128]" ]
[ 11050@0, "BAT[void,Int128]" ]
[ 11051@0, "BAT[void,oid]" ]
[ 11051@0, "BAT[void,pax128]" ]
[ 11051@0, "BAT[void,Int128]" ]
[ 11052@0, "BAT[integer128,any::2]" ]
[ 11052@0, "str" ]
[ 11052@0, "flt" ]
[ 11052@0, "int" ]
[ 11052@0, "*int" ]
[ 11052@0, "BAT[Int128,any::2]" ]
[ 11053@0, "BAT[pax128,any::2]" ]
[ 11053@0, "str" ]
[ 11053@0, "flt" ]
[ 11053@0, "int" ]
[ 11053@0, "*int" ]
[ 11053@0, "BAT[Int128,any::2]" ]
[ 11054@0, "BAT[any::1,integer256]" ]
[ 11054@0, "BAT[any::1,Int256]" ]
[ 11055@0, "BAT[void,oid]" ]
[ 11055@0, "BAT[oid,oid]" ]
[ 11055@0, "BAT[void,integer256]" ]
[ 11055@0, "BAT[int,int]" ]
[ 11055@0, "int" ]
[ 11055@0, "int" ]
[ 11055@0, "BAT[void,Int256]" ]
[ 11056@0, "BAT[void,oid]" ]
[ 11056@0, "BAT[oid,oid]" ]
[ 11056@0, "BAT[void,pax256]" ]
[ 11056@0, "BAT[int,int]" ]
[ 11056@0, "int" ]
[ 11056@0, "int" ]
[ 11056@0, "BAT[void,Int256]" ]
[ 11057@0, "BAT[oid,oid]" ]
[ 11057@0, "BAT[void,integer256]" ]
[ 11057@0, "BAT[void,Int256]" ]
[ 11058@0, "BAT[oid,oid]" ]
[ 11058@0, "BAT[void,pax256]" ]
[ 11058@0, "BAT[void,Int256]" ]
[ 11059@0, "BAT[void,oid]" ]
[ 11059@0, "BAT[void,integer256]" ]
[ 11059@0, "BAT[void,Int256]" ]
[ 11060@0, "BAT[void,oid]" ]
[ 11060@0, "BAT[void,pax256]" ]
[ 11060@0, "BAT[void,Int256]" ]
[ 11061@0, "BAT[integer256,any::2]" ]
[ 11061@0, "str" ]
[ 11061@0, "flt" ]
[ 11061@0, "int" ]
[ 11061@0, "*int" ]
[ 11061@0, "BAT[Int256,any::2]" ]
[ 11062@0, "BAT[pax256,any::2]" ]
[ 11062@0, "str" ]
[ 11062@0, "flt" ]
[ 11062@0, "int" ]
[ 11062@0, "*int" ]
[ 11062@0, "BAT[Int256,any::2]" ]
[ 11063@0, "BAT[void,oid]" ]
[ 11063@0, "BAT[void,any::1]" ]
[ 11063@0, "int" ]
[ 11063@0, "int" ]
[ 11063@0, "int" ]
[ 11063@0, "BAT[void,any::1]" ]
[ 11064@0, "int" ]
[ 11064@0, "int" ]
[ 11065@0, "oid" ]
[ 11065@0, "int" ]
[ 11065@0, "int" ]
[ 11065@0, "BAT[oid,int]" ]
[ 11066@0, "oid" ]
[ 11066@0, "int" ]
[ 11066@0, "int" ]
[ 11066@0, "int" ]
[ 11066@0, "int" ]
[ 11066@0, "BAT[oid,int]" ]
[ 11067@0, "BAT[any::1,int]" ]
[ 11067@0, "int" ]
[ 11067@0, "BAT[any::1,any]" ]
[ 11068@0, "int" ]
[ 11068@0, "int" ]
[ 11068@0, "BAT[oid,int]" ]
[ 11069@0, "int" ]
[ 11069@0, "BAT[oid,int]" ]
[ 11070@0, "int" ]
[ 11070@0, "int" ]
[ 11070@0, "int" ]
[ 11070@0, "int" ]
[ 11070@0, "BAT[oid,int]" ]
[ 11071@0, "oid" ]
[ 11071@0, "int" ]
[ 11071@0, "int" ]
[ 11071@0, "int" ]
[ 11071@0, "BAT[oid,int]" ]
[ 11072@0, "int" ]
[ 11072@0, "int" ]
[ 11072@0, "int" ]
[ 11072@0, "BAT[oid,int]" ]
[ 11073@0, "oid" ]
[ 11073@0, "int" ]
[ 11073@0, "int" ]
[ 11073@0, "BAT[oid,int]" ]
[ 11074@0, "int" ]
[ 11074@0, "int" ]
[ 11074@0, "BAT[oid,int]" ]
[ 11075@0, "int" ]
[ 11075@0, "BAT[oid,int]" ]
[ 11076@0, "BAT[any::1,any::2]" ]
[ 11076@0, "int" ]
[ 11076@0, "*int" ]
[ 11076@0, "BAT[any::1,any::2]" ]
[ 11077@0, "BAT[any::1,any::2]" ]
[ 11077@0, "str" ]
[ 11077@0, "int" ]
[ 11077@0, "*int" ]
[ 11077@0, "BAT[any::1,any::2]" ]
[ 11078@0, "BAT[any::1,any::2]" ]
[ 11078@0, "flt" ]
[ 11078@0, "int" ]
[ 11078@0, "*int" ]
[ 11078@0, "BAT[any::1,any::2]" ]
[ 11079@0, "BAT[any::1,any::2]" ]
[ 11079@0, "BAT[any::2,any::3]" ]
[ 11079@0, "BAT[any::1,any::3]" ]
[ 11080@0, "BAT[any::1,any::2]" ]
[ 11080@0, "BAT[any::2,any::3]" ]
[ 11080@0, "int" ]
[ 11080@0, "BAT[any::1,any::3]" ]
[ 11081@0, "BAT[any::1,any::2]" ]
[ 11081@0, "BAT[any::2,any::3]" ]
[ 11081@0, "BAT[any::1,any::3]" ]
[ 11082@0, "BAT[oid,any::1]" ]
[ 11082@0, "BAT[int,int]" ]
[ 11082@0, "BAT[void,any::1]" ]
[ 11083@0, "BAT[any::1,int]" ]
[ 11083@0, "BAT[any::1,integer1]" ]
[ 11084@0, "int" ]
[ 11085@0, "BAT[any::1,any::2]" ]
[ 11085@0, "BAT[any::2,any::3]" ]
[ 11085@0, "int" ]
[ 11085@0, "BAT[any::1,any::3]" ]
[ 11086@0, "BAT[any::1,any::2]" ]
[ 11086@0, "BAT[any::2,any::3]" ]
[ 11086@0, "int" ]
[ 11086@0, "int" ]
[ 11086@0, "bit" ]
[ 11086@0, "BAT[any::1,any::3]" ]
[ 11087@0, "int" ]
[ 11088@0, "BAT[void,oid]" ]
[ 11088@0, "BAT[void,any::1]" ]
[ 11088@0, "int" ]
[ 11088@0, "int" ]
[ 11088@0, "BAT[void,any::1]" ]
[ 11089@0, "BAT[void,oid]" ]
[ 11089@0, "BAT[void,any::1]" ]
[ 11089@0, "int" ]
[ 11089@0, "BAT[void,any::1]" ]
[ 11090@0, "int" ]
[ 11090@0, "int" ]
[ 11091@0, "BAT[void,oid]" ]
[ 11091@0, "int" ]
[ 11091@0, "int" ]
[ 11091@0, "int" ]
[ 11091@0, "BAT[oid,oid]" ]
[ 11092@0, "BAT[void,oid]" ]
[ 11092@0, "BAT[void,any::1]" ]
[ 11092@0, "BAT[void,any::1]" ]
[ 11093@0, "void" ]
[ 11095@0, "int" ]
[ 11095@0, "int" ]
[ 11095@0, "int" ]
[ 11095@0, "int" ]
[ 11095@0, "BAT[void,int]" ]
[ 11096@0, "BAT[any::1,any]" ]
[ 11096@0, "*BAT[any::1,int]" ]
[ 11096@0, "void" ]
[ 11097@0, "int" ]
[ 11097@0, "any::1" ]
[ 11097@0, "BAT[void,any::1]" ]
[ 11098@0, "BAT[oid,any::1]" ]
[ 11098@0, "BAT[oid,any::1]" ]
[ 11098@0, "int" ]
[ 11098@0, "BAT[oid,any::1]" ]
[ 11099@0, "BAT[any::1,any::2]" ]
[ 11099@0, "any::2" ]
[ 11099@0, "any::2" ]
[ 11099@0, "BAT[any::1,any::2]" ]
[ 11100@0, "str" ]
[ 11100@0, "bit" ]
[ 11101@0, "str" ]
[ 11101@0, "BAT[oid,str]" ]
[ 11102@0, "str" ]
[ 11102@0, "BAT[oid,str]" ]
[ 11103@0, "str" ]
[ 11103@0, "void" ]
[ 11104@0, "str" ]
[ 11104@0, "void" ]
[ 11105@0, "BAT[any::1,any::2]" ]
[ 11105@0, "BAT[any::1,any::2]" ]
[ 11105@0, "BAT[void,any::2]" ]
[ 11106@0, "int" ]
[ 11106@0, "BAT[void,int]" ]
[ 11107@0, "BAT[any::1,any::2]" ]
[ 11107@0, "int" ]
[ 11107@0, "BAT[int,BAT]" ]
[ 11108@0, "BAT[any::1,any::2]" ]
[ 11108@0, "int" ]
[ 11108@0, "BAT[any::1,any::2]" ]
[ 11109@0, "str" ]
[ 11109@0, "*any" ]
[ 11109@0, "void" ]
[ 11110@0, "str" ]
[ 11110@0, "*any" ]
[ 11110@0, "void" ]
[ 11111@0, "oid" ]
[ 11111@0, "str" ]
[ 11112@0, "str" ]
[ 11112@0, "oid" ]
[ 11113@0, "str" ]
[ 11113@0, "oid" ]
[ 11114@0, "str" ]
[ 11114@0, "oid" ]
[ 11115@0, "any" ]
[ 11115@0, "str" ]
[ 11116@0, "any" ]
[ 11116@0, "str" ]
[ 11117@0, "oid" ]
[ 11117@0, "int" ]
[ 11118@0, "oid" ]
[ 11118@0, "void" ]
[ 11119@0, "oid" ]
[ 11119@0, "void" ]
[ 11120@0, "str" ]
[ 11120@0, "str" ]
[ 11120@0, "str" ]
[ 11120@0, "void" ]
[ 11121@0, "oid" ]
[ 11121@0, "int" ]
[ 11121@0, "str" ]
[ 11121@0, "oid" ]
[ 11122@0, "oid" ]
[ 11122@0, "int" ]
[ 11122@0, "str" ]
[ 11122@0, "oid" ]
[ 11123@0, "str" ]
[ 11123@0, "void" ]
[ 11124@0, "oid" ]
[ 11124@0, "void" ]
[ 11125@0, "str" ]
[ 11125@0, "void" ]
[ 11126@0, "oid" ]
[ 11126@0, "void" ]
[ 11127@0, "oid" ]
[ 11127@0, "void" ]
[ 11128@0, "oid" ]
[ 11128@0, "oid" ]
[ 11128@0, "void" ]
[ 11129@0, "void" ]
[ 11130@0, "void" ]
[ 11131@0, "void" ]
[ 11132@0, "void" ]
[ 11133@0, "void" ]
[ 11134@0, "str" ]
[ 11134@0, "void" ]
[ 11135@0, "str" ]
[ 11135@0, "int" ]
[ 11135@0, "void" ]
[ 11136@0, "BAT[void,any]" ]
[ 11136@0, "BAT[void,any]" ]
[ 11136@0, "void" ]
[ 11137@0, "str" ]
[ 11137@0, "str" ]
[ 11137@0, "void" ]
[ 11138@0, "str" ]
[ 11138@0, "str" ]
[ 11138@0, "void" ]
[ 11139@0, "str" ]
[ 11139@0, "str" ]
[ 11139@0, "void" ]
[ 11140@0, "BAT[void,any::1]" ]
[ 11140@0, "int" ]
[ 11140@0, "BAT[void,any::1]" ]
[ 11141@0, "BAT[void,any::1]" ]
[ 11141@0, "int" ]
[ 11141@0, "any::1" ]
[ 11142@0, "BAT[void,any::1]" ]
[ 11142@0, "int" ]
[ 11142@0, "BAT[void,any::1]" ]
[ 11143@0, "BAT[void,any::1]" ]
[ 11143@0, "any::1" ]
[ 11144@0, "BAT[void,any::1]" ]
[ 11144@0, "BAT[void,any::1]" ]
[ 11145@0, "BAT[void,any::1]" ]
[ 11145@0, "BAT[void,any::1]" ]
[ 11146@0, "bit" ]
[ 11146@0, "bit" ]
[ 11147@0, "void" ]
[ 11148@0, "BAT[void,BAT]" ]
[ 11148@0, "BAT[void,BAT]" ]
[ 11149@0, "BAT[oid,BAT]" ]
[ 11149@0, "BAT[void,any::1]" ]
[ 11150@0, "BAT[void,BAT]" ]
[ 11150@0, "BAT[void,dbl]" ]
[ 11151@0, "int" ]
[ 11151@0, "BAT[void,BAT]" ]
[ 11151@0, "BAT[void,BAT]" ]
[ 11152@0, "BAT[void,BAT]" ]
[ 11152@0, "BAT[void,BAT]" ]
[ 11153@0, "BAT[void,BAT]" ]
[ 11153@0, "BAT[void,BAT]" ]
[ 11154@0, "BAT[void,str]" ]
[ 11154@0, "BAT[void,oid]" ]
[ 11154@0, "BAT[void,BAT]" ]
[ 11155@0, "BAT[void,BAT]" ]
[ 11155@0, "BAT[void,BAT]" ]
[ 11155@0, "BAT[void,BAT]" ]
[ 11155@0, "BAT[void,BAT]" ]
[ 11156@0, "BAT[void,BAT]" ]
[ 11156@0, "BAT[void,BAT]" ]
[ 11156@0, "BAT[void,BAT]" ]
[ 11156@0, "BAT[void,BAT]" ]
[ 11156@0, "void" ]
[ 11157@0, "BAT[void,dbl]" ]
[ 11157@0, "bit" ]
[ 11158@0, "BAT[void,oid]" ]
[ 11158@0, "BAT[void,str]" ]
[ 11158@0, "BAT[void,BAT]" ]
[ 11159@0, "BAT[void,str]" ]
[ 11159@0, "BAT[void,oid]" ]
[ 11159@0, "BAT[void,str]" ]
[ 11159@0, "oid" ]
[ 11159@0, "BAT[oid,dbl]" ]
[ 11160@0, "BAT[void,str]" ]
[ 11160@0, "BAT[void,oid]" ]
[ 11160@0, "BAT[void,str]" ]
[ 11160@0, "oid" ]
[ 11160@0, "BAT[oid,dbl]" ]
[ 11161@0, "BAT[void,BAT]" ]
[ 11161@0, "BAT[void,any]" ]
[ 11161@0, "BAT[void,dbl]" ]
[ 11162@0, "BAT[void,BAT]" ]
[ 11162@0, "BAT[void,any]" ]
[ 11162@0, "BAT[void,dbl]" ]
[ 11162@0, "BAT[void,dbl]" ]
[ 11163@0, "BAT[void,BAT]" ]
[ 11163@0, "BAT[void,dbl]" ]
[ 11163@0, "BAT[void,dbl]" ]
[ 11163@0, "BAT[void,dbl]" ]
[ 11164@0, "BAT[void,BAT]" ]
[ 11164@0, "BAT[void,BAT]" ]
[ 11164@0, "BAT[void,dbl]" ]
[ 11164@0, "BAT[void,dbl]" ]
[ 11165@0, "dbl" ]
[ 11165@0, "dbl" ]
[ 11165@0, "dbl" ]
[ 11165@0, "dbl" ]
[ 11166@0, "dbl" ]
[ 11166@0, "BAT[void,dbl]" ]
[ 11166@0, "BAT[void,dbl]" ]
[ 11166@0, "BAT[void,dbl]" ]
[ 11167@0, "BAT[void,dbl]" ]
[ 11167@0, "BAT[void,dbl]" ]
[ 11167@0, "BAT[void,dbl]" ]
[ 11167@0, "BAT[void,dbl]" ]
[ 11168@0, "BAT[void,dbl]" ]
[ 11168@0, "BAT[void,dbl]" ]
[ 11168@0, "BAT[void,dbl]" ]
[ 11168@0, "BAT[void,dbl]" ]
[ 11169@0, "BAT[void,dbl]" ]
[ 11169@0, "BAT[void,dbl]" ]
[ 11169@0, "BAT[void,dbl]" ]
[ 11170@0, "BAT[void,dbl]" ]
[ 11170@0, "BAT[void,dbl]" ]
[ 11170@0, "BAT[void,dbl]" ]
[ 11171@0, "BAT[void,oid]" ]
[ 11171@0, "BAT[void,str]" ]
[ 11171@0, "BAT[void,str]" ]
[ 11171@0, "void" ]
[ 11172@0, "BAT[void,oid]" ]
[ 11172@0, "BAT[void,str]" ]
[ 11172@0, "BAT[void,str]" ]
[ 11172@0, "void" ]
[ 11173@0, "str" ]
[ 11173@0, "void" ]
[ 11174@0, "void" ]
[ 11175@0, "void" ]
[ 11176@0, "void" ]
[ 11177@0, "void" ]
[ 11178@0, "BAT[void,BAT]" ]
[ 11178@0, "void" ]
[ 11179@0, "BAT[void,BAT]" ]
[ 11179@0, "int" ]
[ 11179@0, "void" ]
[ 11180@0, "BAT[void,BAT]" ]
[ 11180@0, "str" ]
[ 11180@0, "any" ]
[ 11181@0, "BAT[void,BAT]" ]
[ 11181@0, "str" ]
[ 11181@0, "int" ]
[ 11181@0, "any" ]
[ 11182@0, "BAT[void,BAT]" ]
[ 11182@0, "BAT[void,BAT]" ]
[ 11183@0, "BAT[void,BAT]" ]
[ 11183@0, "int" ]
[ 11183@0, "str" ]
[ 11184@0, "BAT[void,BAT]" ]
[ 11184@0, "str" ]
[ 11184@0, "str" ]
[ 11184@0, "any" ]
[ 11185@0, "BAT[void,BAT]" ]
[ 11185@0, "str" ]
[ 11185@0, "str" ]
[ 11185@0, "int" ]
[ 11185@0, "any" ]
[ 11186@0, "str" ]
[ 11186@0, "str" ]
[ 11186@0, "int" ]
[ 11186@0, "int" ]
[ 11186@0, "void" ]
[ 11187@0, "str" ]
[ 11187@0, "int" ]
[ 11187@0, "BAT[void,BAT]" ]
[ 11188@0, "BAT[oid,any]" ]
[ 11188@0, "BAT[void,BAT]" ]
[ 11189@0, "str" ]
[ 11189@0, "str" ]
[ 11189@0, "int" ]
[ 11189@0, "int" ]
[ 11189@0, "BAT[void,BAT]" ]
[ 11190@0, "str" ]
[ 11190@0, "str" ]
[ 11190@0, "int" ]
[ 11190@0, "int" ]
[ 11190@0, "void" ]
[ 11191@0, "str" ]
[ 11191@0, "str" ]
[ 11191@0, "int" ]
[ 11191@0, "int" ]
[ 11191@0, "BAT[void,BAT]" ]
[ 11192@0, "str" ]
[ 11192@0, "str" ]
[ 11192@0, "int" ]
[ 11192@0, "int" ]
[ 11192@0, "void" ]
[ 11193@0, "int" ]
[ 11193@0, "int" ]
[ 11193@0, "BAT[oid,dbl]" ]
[ 11194@0, "BAT[int,int]" ]
[ 11194@0, "int" ]
[ 11194@0, "void" ]
[ 11195@0, "int" ]
[ 11195@0, "void" ]
[ 11196@0, "int" ]
[ 11196@0, "int" ]
[ 11196@0, "void" ]
[ 11197@0, "str" ]
[ 11197@0, "str" ]
[ 11197@0, "void" ]
## Comment 1611
Date: 2004-08-17 23:39:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
"CMDbatcast()" did prepare the wrong "argv" to call
"interpret_batscast()".
The respective code has not been changed since the beginning
of the Monet-4.3 repository on July 26 2000; hence, I guess
"[cast]()" has never worked --- apparently Roberto just
wrote history today, being the first human to use "[cast]()" ...
(also added the respective tests, of course...)
## Comment 1612
Date: 2005-10-06 15:13:22 +0200
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-10-06: Claimed by jennie
BugDay_2005-10-06: Done.
test script available as:
MonetDB/tests/BugsViaSourgeforce/Tests/ID.1010729.*
## Comment 1613
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1010729 at http://sourceforge.net/support/tracker.php?aid=1010729
| [cast] buggy | https://api.github.com/repos/MonetDB/MonetDB/issues/302/comments | 0 | 2020-11-30T08:27:50Z | 2024-06-27T10:58:06Z | https://github.com/MonetDB/MonetDB/issues/302 | 753,268,178 | 302 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-17 11:27:07 +0200
From: @swingbit
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-11-22 04:20:03 +0100
## Comment 1600
Date: 2004-08-17 11:27:07 +0200
From: @swingbit
Commenting a macro definition with @( and @) makes Mx
segfault extracting mil code, as follows:
@mil
@(
@= test
test...
@
@)
## Comment 1601
Date: 2004-08-17 15:12:11 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Is this correct usage?
I use @' in front of every line to comment out code (see the
copyright notice in every Mx file).
Even if this is correct usage, I am loath to fix it. Mx is
by far the worst bit of code in the whole of the MonetDB
sources (and that's saying something! ;-).
## Comment 1602
Date: 2004-08-17 15:36:48 +0200
From: @swingbit
Logged In: YES
user_id=883451
I guess that is correct, in principle. It shouldn't segfault
anyway.
I also use @' , unless I have to comment a long piece of code.
I will not cry if this is not going to be fixed, just wanted
to report the bug.
## Comment 1603
Date: 2004-08-17 20:36:31 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
since NxtTok() is only called in FstTok() and in two
for-loop in Form.C & Code.c that do roughly the following:
for(t=FstTok(blk); t; t=NxtTok(t)) ,
we assume, we can savely ignore NULL arguments when NxtTok()
is called...
[ This fix does not change the "code-quality" of Mx in
either way ... ]
## Comment 1604
Date: 2005-11-06 11:03:21 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-10-06: "left-overs" are now marked as "pending"
## Comment 1605
Date: 2005-11-21 04:20:19 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
## Comment 1606
Date: 2006-11-22 04:20:03 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
Logged In: YES
user_id=1312539
Originator: NO
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 1607
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1010604 at http://sourceforge.net/support/tracker.php?aid=1010604
| Mx segfault commenting macros | https://api.github.com/repos/MonetDB/MonetDB/issues/301/comments | 0 | 2020-11-30T08:27:47Z | 2024-06-27T10:58:05Z | https://github.com/MonetDB/MonetDB/issues/301 | 753,268,138 | 301 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-11 09:10:47 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2004-08-11 10:56:42 +0200
## Comment 1597
Date: 2004-08-11 21:10:47 +0200
From: @drstmane
test src/backends/monet4/Tests/smack01.SQL seems to
crash the server.
## Comment 1598
Date: 2005-10-06 17:09:10 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / ALREADY IN TESTWEB
## Comment 1599
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1007486 at http://sourceforge.net/support/tracker.php?aid=1007486
| SQL: test src/backends/monet4/Tests/smack01.SQL fails | https://api.github.com/repos/MonetDB/MonetDB/issues/300/comments | 0 | 2020-11-30T08:27:44Z | 2024-06-27T10:58:04Z | https://github.com/MonetDB/MonetDB/issues/300 | 753,268,116 | 300 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-11 01:16:37 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2004-08-11 01:37:37 +0200
## Comment 1593
Date: 2004-08-11 13:16:37 +0200
From: @grobian
after
./de-bootstrap
cvs update
./bootstrap
<chdir>
rm -R *
../../src-head/sql/configure
--prefix=/nfs/poseidon/Temp/monet/program/
--with-monet=/nfs/poseidon/Temp/monet/program/
make install
../../../../../src-head/sql/src/odbc/driver/SQLExecute.c:
In function `ODBCInitResult':
../../../../../src-head/sql/src/odbc/driver/SQLExecute.c:141:
error: implicit declaration of function `mapi_get_len'
make[3]: *** [SQLExecute.lo] Error 1
make[3]: Leaving directory
`/nfs/poseidon/Temp/monet/build-head/sql/src/odbc/driver'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory
`/nfs/poseidon/Temp/monet/build-head/sql/src/odbc'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/nfs/poseidon/Temp/monet/build-head/sql/src'
make: *** [install-recursive] Error 1
## Comment 1594
Date: 2004-08-11 13:37:37 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Update MonetDB, and in particular Mapi.mx first.
## Comment 1595
Date: 2005-10-06 17:03:24 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / COMPILATION
## Comment 1596
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1007182 at http://sourceforge.net/support/tracker.php?aid=1007182
| ODBC driver build failure | https://api.github.com/repos/MonetDB/MonetDB/issues/299/comments | 0 | 2020-11-30T08:27:41Z | 2024-06-28T13:36:24Z | https://github.com/MonetDB/MonetDB/issues/299 | 753,268,077 | 299 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-11 08:20:54 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2004-08-11 06:29:37 +0200
## Comment 1588
Date: 2004-08-11 08:20:54 +0200
From: @drstmane
[...]
pdflatex /var/tmp/monet.GNU_32-d.12329/sql/SQLfeatures.tex
This is pdfTeX, Version 3.14159-14h-released-20010417
(Web2C 7.3.3.1)
(/var/tmp/monet.GNU_32-d.12329/sql/SQLfeatures.tex{/usr/share/texmf/pdftex/conf
ig/pdftex.cfg}
LaTeX2e <2001/06/01>
Babel <v3.7h> and hyphenation patterns for american,
french, german, ngerman, d
utch, italian, nohyphenation, loaded.
(/usr/share/texmf/tex/latex/base/article.cls
Document Class: article 2001/04/21 v1.4e Standard LaTeX
document class
(/usr/share/texmf/tex/latex/base/fleqn.clo)
(/usr/share/texmf/tex/latex/base/size10.clo))
(/usr/share/texmf/tex/latex/psnfss/times.sty)
(/usr/share/texmf/tex/plain/dvips/epsf.tex
This is `epsf.tex' v2.7k <10 July 1997>
) (/usr/share/texmf/tex/latex/graphics/graphicx.sty
(/usr/share/texmf/tex/latex/graphics/keyval.sty)
(/usr/share/texmf/tex/latex/graphics/graphics.sty
(/usr/share/texmf/tex/latex/graphics/trig.sty)
(/usr/share/texmf/tex/latex/config/graphics.cfg)
(/usr/share/texmf/tex/latex/graphics/pdftex.def)))
(/usr/share/texmf/tex/latex/graphics/epsfig.sty)
(/usr/share/texmf/tex/latex/graphics/color.sty
(/usr/share/texmf/tex/latex/config/color.cfg))
(/usr/share/texmf/tex/latex/html/url.sty)
(./SQLfeatures.aux)
(/usr/share/texmf/tex/latex/psnfss/ot1ptm.fd)
(/usr/share/texmf/tex/context/base/supp-pdf.tex
(/usr/share/texmf/tex/context/base/supp-mis.tex
loading : Context Support Macros / Missing
)
loading : Context Support Macros / PDF
)
LaTeX Warning: Reference `form' on page 1 undefined on
input line 50.
Overfull \hbox (214.79214pt too wide) in paragraph at
lines 84--84
[][]/ptmr7t@8.0pt/http://www.nationaalarchief.nl/collectie/zoeken/toegangen/VOC
[]inventarissen/default.asp?ComponentID=5535&SourcePageID=6947|
Underfull \hbox (badness 2343) in paragraph at lines 87--89
[]/ptmr7t/The archives com-prise over 25 mil-lion
his-tor-i-cal
[1{/usr/share/texmf/dvips/config/pdftex.map}]
Underfull \hbox (badness 1389) in paragraph at lines 90--97
/ptmr7t/lished in the book J.R. Bruijn, F.S. Gaas-tra
and I.
(/usr/share/texmf/tex/latex/psnfss/ot1pcr.fd)
LaTeX Warning: Reference `configfile' on page 2
undefined on input line 138.
Underfull \hbox (badness 1796) in paragraph at lines
140--143
[]/ptmr7t/The Mon-etDB server does not con-tain hard-wired
Overfull \hbox (20.10016pt too wide) in paragraph at
lines 153--153
[]/pcrr7t@8.0pt/ Copyright (c) 1993-2002, CWI. All
rights reserved.[]
Overfull \hbox (53.70018pt too wide) in paragraph at
lines 153--153
[]/pcrr7t@8.0pt/ compiled for i686-pc-linux-gnu/32bit;
dynamically linked.[]
Underfull \hbox (badness 1303) in paragraph at lines
156--159
[]/ptmr7t/Here $PRE-FIX de-notes the path where Mon-etDB
(/usr/share/texmf/tex/latex/psnfss/omsptm.fd)
Overfull \hbox (78.50003pt too wide) in paragraph at
lines 179--179
[]/pcrr7t/--set
monet_mod_path=$MONET_PREFIX/lib/MonetDB:\[]
Underfull \hbox (badness 10000) in paragraph at lines
180--184
/ptmr7t/$MONET[]PREFIX and $SQL[]PREFIX de-
Underfull \hbox (badness 6173) in paragraph at lines
180--184
/ptmr7t/note the pathes where Mon-etDB re-spec-tively
Underfull \hbox (badness 3189) in paragraph at lines
180--184
/ptmr7t/SQL have been in-stalled. Al-ter-na-tively, you
Underfull \hbox (badness 10000) in paragraph at lines
180--184
/ptmr7t/can add $SQL[]PREFIX/lib/MonetDB to the
[2]
Overfull \hbox (16.5pt too wide) in paragraph at lines
197--197
[]/pcrr7t/$ MapiClient -lsql -u monetdb -P monetdb[]
[3]
! LaTeX Error: Environment fig undefined.
See the LaTeX manual or LaTeX Companion for explanation.
Type H <return> for immediate help.
...
l.307 \begin{fig}
?
! Emergency stop.
...
l.307 \begin{fig}
! ==> Fatal error occurred, the output PDF file not
finished!
Transcript written on SQLfeatures.log.
make[2]: *** [SQLfeatures.pdf] Error 1
[...]
## Comment 1589
Date: 2004-08-11 10:10:05 +0200
From: @grobian
Logged In: YES
user_id=963970
Should be:
\begin{figure}
\begin{center}
\includegraphics[width=2in]{file_path}
\caption{ }
\label{ }
\end{center}
\end{figure}
## Comment 1590
Date: 2004-08-11 18:29:37 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Solved, plugged in a 'dummy' image
## Comment 1591
Date: 2005-10-06 17:02:45 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / COMPILATION
## Comment 1592
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1007037 at http://sourceforge.net/support/tracker.php?aid=1007037
| SQL: SQLfeatures.tex does not compile (with pdflatex) | https://api.github.com/repos/MonetDB/MonetDB/issues/298/comments | 0 | 2020-11-30T08:27:38Z | 2024-06-27T10:58:02Z | https://github.com/MonetDB/MonetDB/issues/298 | 753,268,041 | 298 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-10 05:25:54 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Duplicates: #296
Last updated: 2010-05-04 11:12:34 +0200
## Comment 1584
Date: 2004-08-10 17:25:54 +0200
From: @drstmane
Since the recent changes, test
src/odbc/samples/Tests/odbcsample1.SQL fails with
SQLPrepare 1: Error: SQLstate 24000, Errnr 0, Message
[MonetDB][ODBC Driver 1.0]Invalid cursor state
## Comment 1585
Date: 2004-08-10 17:27:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
removed accidently added duplicate
## Comment 1586
Date: 2005-10-06 17:08:27 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / ALREADY IN TESTWEB
## Comment 1587
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1006656 at http://sourceforge.net/support/tracker.php?aid=1006656
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 13976
Date: 2010-05-04 11:12:34 +0200
From: @grobian
*** This bug has been marked as a duplicate of bug #296 ***
| SQL: test src/odbc/samples/Tests/odbcsample1.SQL fails | https://api.github.com/repos/MonetDB/MonetDB/issues/297/comments | 0 | 2020-11-30T08:27:34Z | 2024-06-28T13:36:24Z | https://github.com/MonetDB/MonetDB/issues/297 | 753,268,001 | 297 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-10 05:11:55 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2010-05-04 11:12:34 +0200
## Comment 1580
Date: 2004-08-10 17:11:55 +0200
From: @drstmane
Since the recent changes, test
src/odbc/samples/Tests/odbcsample1.SQL fails with
SQLPrepare 1: Error: SQLstate 24000, Errnr 0, Message
[MonetDB][ODBC Driver 1.0]Invalid cursor state
## Comment 1581
Date: 2004-08-17 15:14:34 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed.
## Comment 1582
Date: 2005-10-06 17:08:06 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / ALREADY IN TESTWEB
## Comment 1583
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1006642 at http://sourceforge.net/support/tracker.php?aid=1006642
## Comment 13977
Date: 2010-05-04 11:12:34 +0200
From: @grobian
*** Bug #297 has been marked as a duplicate of this bug. ***
| SQL: test src/odbc/samples/Tests/odbcsample1.SQL fails | https://api.github.com/repos/MonetDB/MonetDB/issues/296/comments | 0 | 2020-11-30T08:27:31Z | 2024-06-27T10:58:00Z | https://github.com/MonetDB/MonetDB/issues/296 | 753,267,963 | 296 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-10 05:10:04 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2004-08-13 02:27:54 +0200
## Comment 1577
Date: 2004-08-10 17:10:04 +0200
From: @drstmane
Since the recent changes, test
/src/benchmarks/wisconsin/Tests/load.sql fails with
MapiClient:
/ufs/manegold/Monet/4.3/MonetDB/src/mapi/clients/C/Mapi.mx:2852:
mapi_query_part: Assertion `hdl->result == ((void *)0)'
failed.
!Mtimeout: Aborted (6): MapiClient --language=sql -u
monetdb -P monetdb --host=draco --port=53801
## Comment 1578
Date: 2005-10-06 17:07:38 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / ALREADY IN TESTWEB
## Comment 1579
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1006639 at http://sourceforge.net/support/tracker.php?aid=1006639
| SQL: test /src/benchmarks/wisconsin/Tests/load.sql fails | https://api.github.com/repos/MonetDB/MonetDB/issues/295/comments | 0 | 2020-11-30T08:27:28Z | 2024-06-27T10:57:59Z | https://github.com/MonetDB/MonetDB/issues/295 | 753,267,928 | 295 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-10 05:07:51 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-08-11 09:12:09 +0200
## Comment 1573
Date: 2004-08-10 17:07:51 +0200
From: @drstmane
Since the recent changes, test
src/benchmarks/tpch/Tests/load.SQL.py fails with
missing column name 33: find
[...]
MAPI = monetdb@draco:50147
ACTION= read_line
QUERY = COPY 5 RECORDS INTO region from
'/ufs/manegold/Monet/4.3/sql/src/benchmarks/tpch/SF-0.01/region.tbl'
USING DELIMITERS '|', '|\n';
ERROR = Connection terminated
## Comment 1574
Date: 2004-08-11 21:12:09 +0200
From: @drstmane
Logged In: YES
user_id=572415
Niels' (and/or Sjoerd's?) today's checkins seem to solved
the problem.
Thanks!
## Comment 1575
Date: 2005-10-06 17:07:05 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / ALREADY IN TESTWEB
## Comment 1576
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1006637 at http://sourceforge.net/support/tracker.php?aid=1006637
| SQL: test src/benchmarks/tpch/Tests/load.SQL.py fails | https://api.github.com/repos/MonetDB/MonetDB/issues/294/comments | 0 | 2020-11-30T08:27:25Z | 2024-06-27T10:57:58Z | https://github.com/MonetDB/MonetDB/issues/294 | 753,267,901 | 294 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-10 05:04:57 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-08-10 05:47:01 +0200
## Comment 1569
Date: 2004-08-10 17:04:57 +0200
From: @drstmane
Since the recent changes, test
src/benchmarks/ATIS/Tests/select_group.sql fails with
MAPI = monetdb@draco:54550
ACTION= read_line
QUERY = select min(from_airport),min(to_airport) from
flight;
ERROR = Connection terminated
## Comment 1570
Date: 2004-08-10 17:47:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
Niels' last checkin seems to fix this problem.
## Comment 1571
Date: 2005-10-06 17:06:26 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / ALREADY IN TESTWEB
## Comment 1572
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1006635 at http://sourceforge.net/support/tracker.php?aid=1006635
| SQL: test src/benchmarks/ATIS/Tests/select_group.sql fails | https://api.github.com/repos/MonetDB/MonetDB/issues/293/comments | 0 | 2020-11-30T08:27:22Z | 2024-06-27T10:57:57Z | https://github.com/MonetDB/MonetDB/issues/293 | 753,267,862 | 293 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-10 05:02:17 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-08-11 09:09:17 +0200
## Comment 1565
Date: 2004-08-10 17:02:17 +0200
From: @drstmane
Since the recent changes, the tests in
src/backends/monet4 produce now output (sample?) or
fail (smack01); only test smack00 does still work.
## Comment 1566
Date: 2004-08-11 21:09:17 +0200
From: @drstmane
Logged In: YES
user_id=572415
Niels' (and/or Sjoerd's?) today's checkins seem to have
solved to problems --- at least with the sample? tests; test
smack01 still crashes (will be filed in a separate bug report).
## Comment 1567
Date: 2005-10-06 17:05:40 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / ALREADY IN TESTWEB
## Comment 1568
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1006631 at http://sourceforge.net/support/tracker.php?aid=1006631
| SQL: test in src/backends/monet4/Tests fail | https://api.github.com/repos/MonetDB/MonetDB/issues/292/comments | 0 | 2020-11-30T08:27:19Z | 2024-06-27T10:57:56Z | https://github.com/MonetDB/MonetDB/issues/292 | 753,267,838 | 292 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-10 10:40:43 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-08-11 10:06:40 +0200
## Comment 1562
Date: 2004-08-10 10:40:43 +0200
From: @arjan
sql>select char_length('\'');
[ 1 ]
sql>create table test (s varchar(1));
sql>insert into test values ('\'');
MAPI = monetdb@localhost:45123
ACTION= read_into_cache
QUERY = insert into test values ('\'');
ERROR = !Types varchar(2,0) (str) and varchar(1,0)
(str) are not equal
So, in an INSERT, the '\'' string is wrongly typed as a
varchar(2), while it ofcourse is a varchar(1).
If escaped as '''', it has the same behaviour
## Comment 1563
Date: 2005-10-06 17:00:13 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
ALREADY IN TESTWEB
## Comment 1564
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1006469 at http://sourceforge.net/support/tracker.php?aid=1006469
| Escaped characters count double in INSERT | https://api.github.com/repos/MonetDB/MonetDB/issues/291/comments | 0 | 2020-11-30T08:27:16Z | 2024-06-27T10:57:55Z | https://github.com/MonetDB/MonetDB/issues/291 | 753,267,808 | 291 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-10 10:38:34 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2004-08-11 10:49:31 +0200
## Comment 1557
Date: 2004-08-10 10:38:34 +0200
From: @drstmane
ODBC driver fails to compile on the following platforms:
GNU 32 d Darwin7.4.0
GNU 32 s CYGWIN1.5.7
GNU 64 d IRIX646.5
GNU 64 d Linux2.4.18-e.25smp
GNU 64 d Linux2.4.26
GNU 64 d SunOS5.8
ntv 32 d Linux2.4.20-31.9smp
ntv 32 d Linux2.4.26
ntv 64 d Linux2.4.18-e.25smp
ntv 64 d SunOS5.8
see attached make log snippets for details.
## Comment 1558
Date: 2004-08-10 11:26:26 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Hopefully I was able to fix these errors. This report
should be closed after a successful test tomorrow.
## Comment 1559
Date: 2004-08-11 10:49:31 +0200
From: @drstmane
Logged In: YES
user_id=572415
Sjoerd's yesterday's changes did indeed fix the errors.
Thanks!
## Comment 1560
Date: 2005-10-06 16:58:50 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / COMPILATION
## Comment 1561
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1006468 at http://sourceforge.net/support/tracker.php?aid=1006468
| ODBC driver fails to compile on several platforms | https://api.github.com/repos/MonetDB/MonetDB/issues/290/comments | 0 | 2020-11-30T08:27:13Z | 2024-06-27T10:57:54Z | https://github.com/MonetDB/MonetDB/issues/290 | 753,267,767 | 290 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-09 02:55:32 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2004-08-10 08:22:56 +0200
## Comment 1549
Date: 2004-08-09 14:55:32 +0200
From: @drstmane
since the recent "utime"-related changes, Mx does not
compile any more with gcc on Solaris:
========
[...]
gcc -m64 -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU_64-d.10574/MonetDB/src/utils/Mx
-I../../..
-I/var/tmp/monet.GNU_64-d.10574/MonetDB/src/utils/Mx
-O2 -Wall -W -O2 -fomit-frame-pointer
-finline-functions -DHWCOUNTERS -DHW_SunOS -DHW_sun4u
-Werror-implicit-function-declaration -Werror
-Wno-format -Wno-unused -Wno-uninitialized -DUNIX
-DMX_CXX_SUFFIX=\"cc\" -O1 -c `test -f
'/var/tmp/monet.GNU_64-d.10574/MonetDB/src/utils/Mx/Io.c'
|| echo
'/var/tmp/monet.GNU_64-d.10574/MonetDB/src/utils/Mx/'`/var/tmp/monet.GNU_64-d.10574/MonetDB/src/utils/Mx/Io.c
/var/tmp/monet.GNU_64-d.10574/MonetDB/src/utils/Mx/Io.c:
In function `UpdateFiles':
/var/tmp/monet.GNU_64-d.10574/MonetDB/src/utils/Mx/Io.c:293:
implicit declaration of function `utime'
gmake[4]: *** [Io.o] Error 1
gmake[4]: Leaving directory
`/scratch/monet.GNU_64-d.10574/MonetDB/SunOS5.8/src/utils/Mx'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory
`/scratch/monet.GNU_64-d.10574/MonetDB/SunOS5.8/src/utils'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/scratch/monet.GNU_64-d.10574/MonetDB/SunOS5.8/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/scratch/monet.GNU_64-d.10574/MonetDB/SunOS5.8'
gmake: *** [all] Error 2
[...]
========
Apparently, (at least) on Solaris, we need to (also)
include "utime.h" to get a prototype definition for
"utime()"; including (only) the exsiting "sys/utime.h"
does not seem to work...
## Comment 1550
Date: 2004-08-09 16:00:49 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed by checking for the existence of utime.h (in addition
to sys/utime.h) and including that in preference to sys/utime.h.
## Comment 1551
Date: 2004-08-09 21:44:50 +0200
From: @mlkersten
Logged In: YES
user_id=490798
After a clean configure call and make on my machine, it
complaints about utime implictly defined.
So maybe the patch was not complete.
## Comment 1552
Date: 2004-08-09 22:14:44 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I can't reproduce this. Did you "./bootstrap"?
## Comment 1553
Date: 2004-08-09 22:45:38 +0200
From: @drstmane
Logged In: YES
user_id=572415
I cannot reproduce the problem, either.
also on my machine (which should be identical to Martin's),
from scratch compilation (./bootstrap; configure; make; make
install) of the latest CVS HEAD version works just fine with
gcc, both with "configure --enable-debug" and "configure
--enable-optimize"...
If testing tonight does not reveal any problems, either,
I'll close this report, again.
Martin,
could you please re-try with
./de-bootstrap
cvs update -dP
./bootstrap
cd Linux
configure
make
make install
## Comment 1554
Date: 2004-08-10 08:22:56 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Also fixed for Monet5.
## Comment 1555
Date: 2005-10-06 16:57:38 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / COMPILATION
## Comment 1556
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1005943 at http://sourceforge.net/support/tracker.php?aid=1005943
| Mx does not compile with GNU on Solaris | https://api.github.com/repos/MonetDB/MonetDB/issues/289/comments | 0 | 2020-11-30T08:27:10Z | 2024-06-27T10:57:53Z | https://github.com/MonetDB/MonetDB/issues/289 | 753,267,729 | 289 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-08 08:55:51 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-08-11 10:55:02 +0200
## Comment 1545
Date: 2004-08-08 20:55:51 +0200
From: @grobian
Monet Database Server V4.3.19
Copyright (c) 1993-2004, CWI. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl for further information.
monet>module(sql_server);
monet>Mserver:
../../../../src-head/sql/src/server/sql_scope.mx:263:
table_add_column: Assertion `(!tname || strlen(tname))'
failed.
Killed
Executed query:
(an attempt to get JDBC going with the new table layout)
SELECT * FROM ( SELECT 'demo' AS "TABLE_CAT",
"schemas"."name" AS "TABLE_SCHEM", "tables"."name" AS
"TABLE_NAME", 'SYSTEM TABLE' AS "TABLE_TYPE", '' AS
"REMARKS", null AS "TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'rowid' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS
"REF_GENERATION" FROM "tables", "schemas" WHERE
"tables"."schema_id" = "schemas"."id" AND
"tables"."system" = true AND "tables"."istable" = true
UNION ALL SELECT 'demo' AS "TABLE_CAT",
"schemas"."name" AS "TABLE_SCHEM", "tables"."name" AS
"TABLE_NAME", 'TABLE' AS "TABLE_TYPE", '' AS "REMARKS",
null AS "TYPE_CAT", null AS "TYPE_SCHEM", null AS
"TYPE_NAME", 'rowid' AS "SELF_REFERENCING_COL_NAME",
'SYSTEM' AS "REF_GENERATION" FROM "tables", "schemas"
WHERE "tables"."schema_id" = "schemas"."id" AND
"tables"."system" = false AND "tables"."istable" = true
UNION ALL SELECT 'demo' AS "TABLE_CAT",
"schemas"."name" AS "TABLE_SCHEM", "tables"."name" AS
"TABLE_NAME", 'SYSTEM VIEW' AS "TABLE_TYPE", '' AS
"REMARKS", null AS "TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'rowid' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS
"REF_GENERATION" FROM "tables", "schemas" WHERE
"tables"."schema_id" = "schemas"."id" AND
"tables"."system" = true AND "tables"."istable" = false
UNION ALL SELECT 'demo' AS "TABLE_CAT",
"schemas"."name" AS "TABLE_SCHEM", "tables"."name" AS
"TABLE_NAME", 'VIEW' AS "TABLE_TYPE", '' AS "REMARKS",
null AS "TYPE_CAT", null AS "TYPE_SCHEM", null AS
"TYPE_NAME", 'rowid' AS "SELF_REFERENCING_COL_NAME",
'SYSTEM' AS "REF_GENERATION" FROM "tables", "schemas"
WHERE "tables"."schema_id" = "schemas"."id" AND
"tables"."system" = false AND "tables"."istable" =
false UNION ALL SELECT 'demo' AS "TABLE_CAT",
"schemas"."name" AS "TABLE_SCHEM", "tables"."name" AS
"TABLE_NAME", 'SYSTEM SESSION TABLE' AS "TABLE_TYPE",
'' AS "REMARKS", null AS "TYPE_CAT", null AS
"TYPE_SCHEM", null AS "TYPE_NAME", 'rowid' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS
"REF_GENERATION" FROM "tmp_tables" AS "tables",
"schemas" WHERE "tables"."schema_id" = "schemas"."id"
AND "tables"."system" = true AND "tables"."istable" =
true UNION ALL SELECT 'demo' AS "TABLE_CAT",
"schemas"."name" AS "TABLE_SCHEM", "tables"."name" AS
"TABLE_NAME", 'SESSION TABLE' AS "TABLE_TYPE", '' AS
"REMARKS", null AS "TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'rowid' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS
"REF_GENERATION" FROM "tmp_tables" AS "tables",
"schemas" WHERE "tables"."schema_id" = "schemas"."id"
AND "tables"."system" = false AND "tables"."istable" =
true UNION ALL SELECT 'demo' AS "TABLE_CAT",
"schemas"."name" AS "TABLE_SCHEM", "tables"."name" AS
"TABLE_NAME", 'SYSTEM SESSION VIEW' AS "TABLE_TYPE", ''
AS "REMARKS", null AS "TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'rowid' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS
"REF_GENERATION" FROM "tmp_tables" AS "tables",
"schemas" WHERE "tables"."schema_id" = "schemas"."id"
AND "tables"."system" = true AND "tables"."istable" =
false UNION ALL SELECT 'demo' AS "TABLE_CAT",
"schemas"."name" AS "TABLE_SCHEM", "tables"."name" AS
"TABLE_NAME", 'SESSION VIEW' AS "TABLE_TYPE", '' AS
"REMARKS", null AS "TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'rowid' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS
"REF_GENERATION" FROM "tmp_tables" AS "tables",
"schemas" WHERE "tables"."schema_id" = "schemas"."id"
AND "tables"."system" = false AND "tables"."istable" =
false ) AS "tables" WHERE 1 = 1 AND ("TABLE_TYPE" LIKE
'TABLE' OR "TABLE_TYPE" LIKE 'VIEW') ORDER BY
"TABLE_TYPE", "TABLE_SCHEM", "TABLE_NAME" ;
## Comment 1546
Date: 2005-10-06 16:56:28 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06
REASSIGN meltdown
## Comment 1547
Date: 2005-10-06 20:56:42 +0200
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-10-06: HANDLED BY meltdown
BugDay_2005-10-06: TEST ADDED / SUCCESS
sql/src/test/BugDay_2005-10-06_2.9.3/Tests/simple_union.SF-1005596.*
## Comment 1548
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1005596 at http://sourceforge.net/support/tracker.php?aid=1005596
| SQL: MeltDown on `simple' union query | https://api.github.com/repos/MonetDB/MonetDB/issues/288/comments | 0 | 2020-11-30T08:27:07Z | 2024-06-27T10:57:52Z | https://github.com/MonetDB/MonetDB/issues/288 | 753,267,703 | 288 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-08-08 06:30:41 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-08-13 10:11:24 +0200
## Comment 1540
Date: 2004-08-08 18:30:41 +0200
From: @grobian
when the server has auto-commit switched on, and a
multi-query statement is sent, the server commits after
each query, instead of after the statement.
Suppose a multiquery statement:
update x set val = 2 where id = 12; select * from xtypo;
the second select query will fail, while the first
update will succeed.
In this case JDBC has to decide wheter to return
results (success) or an error (failure). The whole
statement has to be considered to be a transaction in
auto-commit mode. This thought is supported by the
fact that the user supplied these multiple queries at
the same time, not using multiple statements.
In case this auto-commit behaviour is implemented I
would have a simple solution for 'batching' facilities
as well
## Comment 1541
Date: 2004-08-13 10:11:24 +0200
From: @njnes
Logged In: YES
user_id=43556
The semantics are now changed to handle batches of queries
as one transaction.
## Comment 1542
Date: 2005-10-06 16:48:30 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06
REASSIGN meltdown
## Comment 1543
Date: 2005-10-06 21:02:37 +0200
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-10-06: HANDLED BY meltdown
BugDay_2005-10-06: NO TEST / POSTPONE
needs a JDBC application to test this, because JDBC
semantics are necessary here, not offered by mapiclient.
The behaviour is handled by the JDBC batching test at the
moment, though not error tested.
## Comment 1544
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1005549 at http://sourceforge.net/support/tracker.php?aid=1005549
| SQL: inappropriate auto-commit behaviour on multi-query stmt | https://api.github.com/repos/MonetDB/MonetDB/issues/287/comments | 0 | 2020-11-30T08:27:04Z | 2024-06-27T10:57:51Z | https://github.com/MonetDB/MonetDB/issues/287 | 753,267,672 | 287 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-30 09:40:31 +0200
From: Jan Rittinger <<jan.rittinger>>
To: @sjoerdmullender
Version: -- development
Last updated: 2004-08-17 03:36:28 +0200
## Comment 1534
Date: 2004-07-30 21:40:31 +0200
From: Jan Rittinger <<jan.rittinger>>
If I call the import_doc(str,str) from the pathfinder module (main branch)
with a non-existent source string I get no error message. It just stops
the PROC at the point where it goes wrong. If I do the same with the
Mserver I get a error reported.
Perhaps it is related to the other
<a href="http://sourceforge.net/tracker/index.php?
func=detail&aid=998332&group_id=56967&atid=482468">ERROR BUG
(998332)</a>.
The pathfinder module is loaded by the Mserver.
## Comment 1535
Date: 2004-07-30 21:42:45 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
grml - how do I get URLs inside a bug report without the real URL?
## Comment 1536
Date: 2004-08-03 15:29:19 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Just remove the printf(">>> Importing ...) statement from
pathfinder.mx and things work.
## Comment 1537
Date: 2004-08-17 15:36:28 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
By starting a new result set when an error is encountered
after having seen normal output, we can now report the error
message to users of the Mapi library.
When mapi_fetch_line returns NULL or mapi_fetch_row returns
0, call mapi_next_result. If that returns 1 there is a new
result set which you can then start reading from. At any
time (at the beginning is probably best) you can call
mapi_result_error which returns a string with the error
message from the server, if any (NULL otherwise). Typical
usage would be:
do {
if ((error = mapi_result_error(hdl)) != NULL)
mapi_explain_result(hdl, stderr);
while ((line = mapi_fetch_line(hdl)) != NULL)
/* use output */;
} while (mapi_next_result(hdl) == 1);
My previous comment was a red herring. It should now also
work with the original printf in pathfinder.mx (
## Comment 1538
Date: 2005-10-06 16:46:53 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done
NO TEST / REDUNDANT
note: already covered by test for http://sourceforge.net/support/tracker.php?aid=998332
## Comment 1539
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1000896 at http://sourceforge.net/support/tracker.php?aid=1000896
| MapiClient produces no error | https://api.github.com/repos/MonetDB/MonetDB/issues/286/comments | 0 | 2020-11-30T08:27:02Z | 2024-06-27T10:57:50Z | https://github.com/MonetDB/MonetDB/issues/286 | 753,267,632 | 286 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-30 11:15:23 +0200
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2004-08-05 10:37:51 +0200
## Comment 1528
Date: 2004-07-30 11:15:23 +0200
From: @sjoerdmullender
The following statement causes the server to crash with
Mserver:
/ufs/sjoerd/src/MonetDB/sql/src/server/sql_bm.mx:180:
bun_inplace: Assertion `b->dims.hseq == 0' failed.
select case c."null" when true then 1 when false then 0
end from sys.schemas s, sys.tables t, sys.columns c;
## Comment 1529
Date: 2004-08-05 22:37:51 +0200
From: @njnes
Logged In: YES
user_id=43556
assertion was to stricked
## Comment 1530
Date: 2005-10-06 16:44:38 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06
REASSIGN meltdown
## Comment 1531
Date: 2005-10-06 17:01:22 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
## Comment 1532
Date: 2005-10-06 17:07:02 +0200
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-10-06: Claimed by niels
BugDay_2005-10-06: TEST exists
Test exists as ./src/test/crashme and bugs case*
## Comment 1533
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1000592 at http://sourceforge.net/support/tracker.php?aid=1000592
| SQL server assertion error | https://api.github.com/repos/MonetDB/MonetDB/issues/285/comments | 0 | 2020-11-30T08:26:59Z | 2024-06-27T10:57:49Z | https://github.com/MonetDB/MonetDB/issues/285 | 753,267,606 | 285 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-30 10:32:27 +0200
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2004-08-08 11:25:38 +0200
## Comment 1523
Date: 2004-07-30 10:32:27 +0200
From: @sjoerdmullender
sql>select cast(true as integer);
convert_single_value name
mediumint type
1 tuplecount
0 id
[ 1 ]
sql>select cast(true as smallint);
MAPI = monetdb@localhost:45123
ACTION= read_into_cache
QUERY = select cast(true as smallint);
ERROR = !Types boolean(0,0) (bit) and smallint(4,0)
(sht) are not equal
sql>
## Comment 1524
Date: 2004-08-08 11:25:38 +0200
From: @njnes
Logged In: YES
user_id=43556
added missing convert functions
## Comment 1525
Date: 2004-08-13 08:52:20 +0200
From: @njnes
Logged In: YES
user_id=43556
added missing convert functions
## Comment 1526
Date: 2005-10-06 16:42:22 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
ALREADY IN TESTWEB
## Comment 1527
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1000576 at http://sourceforge.net/support/tracker.php?aid=1000576
| casting Boolean to smallint fails | https://api.github.com/repos/MonetDB/MonetDB/issues/284/comments | 0 | 2020-11-30T08:26:57Z | 2024-06-27T10:57:48Z | https://github.com/MonetDB/MonetDB/issues/284 | 753,267,575 | 284 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-30 10:25:27 +0200
From: @sjoerdmullender
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2004-07-30 11:17:43 +0200
## Comment 1517
Date: 2004-07-30 10:25:27 +0200
From: @sjoerdmullender
There are two problems with the use of the new macro
find_bounds. In both invocation, the last argument
causes a (fatal) compiler warning.
gcc -DHAVE_CONFIG_H -I.
-I/ufs/sjoerd/src/MonetDB/monet/src/modules/plain
-I../../..
-I/ufs/sjoerd/src/MonetDB/monet/src/modules/plain
-I../../common -I../../gdk -I../../monet
-I/usr/src/linux-2.6.6-1.435/include -std=c99 -Wall -W
-g -DHWCOUNTERS -DHW_Linux -DHW_i686
-Werror-implicit-function-declaration -Werror
-Wno-format -Wno-unused-function -Wno-unused-label
-Wno-strict-aliasing -D_REENTRANT -c arith.c -fPIC
-DPIC -o .libs/arith.o
/ufs/sjoerd/src/MonetDB/monet/src/modules/plain/algebra.mx:
In function `CMDfind_higher':
/ufs/sjoerd/src/MonetDB/monet/src/modules/plain/algebra.mx:1668:
warning: statement with no effect
/ufs/sjoerd/src/MonetDB/monet/src/modules/plain/algebra.mx:
In function `CMDfind_lower':
/ufs/sjoerd/src/MonetDB/monet/src/modules/plain/algebra.mx:1668:
warning: suggest parentheses around && within ||
## Comment 1518
Date: 2004-07-30 10:33:25 +0200
From: @peterboncz
Logged In: YES
user_id=591107
icc did not give a warning, therefore I did not notice this
before checking in
## Comment 1519
Date: 2004-07-30 10:57:39 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
No, only half the problem is fixed.
## Comment 1520
Date: 2004-07-30 11:17:43 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
It's really fixed now.
## Comment 1521
Date: 2005-10-06 16:40:55 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / COMPILATION
## Comment 1522
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1000571 at http://sourceforge.net/support/tracker.php?aid=1000571
| algebra.mx fails to compile | https://api.github.com/repos/MonetDB/MonetDB/issues/283/comments | 0 | 2020-11-30T08:26:54Z | 2024-06-27T10:57:47Z | https://github.com/MonetDB/MonetDB/issues/283 | 753,267,548 | 283 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-26 11:57:33 +0200
From: Jan Rittinger <<jan.rittinger>>
To: @sjoerdmullender
Version: -- development
Last updated: 2004-08-18 01:08:13 +0200
## Comment 1511
Date: 2004-07-26 23:57:33 +0200
From: Jan Rittinger <<jan.rittinger>>
Used blocking ('{' '}') to make the scopes of variables as small as
possible. But ERROR messages triggered in inner scopes don't get
printed.
In the appended file the ERROR call in line 1171 is not printed.
## Comment 1512
Date: 2004-07-27 01:24:20 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jan,
after patching your script as follows:
========
01:22:16 manegold@draco:~/Monet/4.3/MonetDB $ diff -u
/tmp/no_error_output.mil{~,}
--- /tmp/no_error_output.mil~ 2004-07-27
01:22:16.000000000 +0200
+++ /tmp/no_error_output.mil 2004-07-27
01:21:20.000000000 +0200
@@ -2,11 +2,11 @@
for $i in
fn:doc("auction.xml")/site/regions/australia/item
return <item>{attribute name {$i/name/text()},
$i/description}</item>
init ()
- module("pathfinder");
- module("pf_support");
- module("aggrX3");
- module("xtables");
- module("malalgebra");
+ module("pathfinder");
+ module("pf_support");
+ module("aggrX3");
+ module("xtables");
+ module("malalgebra");
var ws := create_ws();
var loop000 := bat(void,oid).seqbase(0@0);
loop000.insert(0@0, 1@0);
@@ -1166,10 +1166,16 @@
kind := vid.leftfetchjoin(v_kind001);
vid := nil;
} end of translateVar (c)
+print(0);
{ loop_liftedAttrConstr (int i)
var test := iter.tunique;
-if (test.count != kind.ord_uselect(STR).count)
+print(1);
+if (test.count != kind.ord_uselect(STR).count) {
+ print(2);
ERROR ("there can be only one string for each iter in
attribute construction");
+ print(3);
+}
+print(4);
test := {count}(iter.reverse,test);
if (test.count != test.sum)
ERROR ("more than 1 argument in attribute constructor");
@@ -1204,7 +1210,9 @@
pos := pos002;
item := iter002.mark(seqb);
kind := kind002.project(ATTR);
+print(5);
} end of loop_liftedAttrConstr (int i)
+print(6);
deleteResult2 ()
iter002 := nil;
pos002 := nil;
01:22:19 manegold@draco:~/Monet/4.3/MonetDB $
========
and using your database (the one we copied earlier),
I get this:
========
01:22:19 manegold@draco:~/Monet/4.3/MonetDB $ Mserver
--dbname=jan /tmp/no_error_output.mil
Monet Database Server V4.3.19
Copyright (c) 1993-2004, CWI. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl for further information.
!ERROR: ordering is wrong in scj (concept with slices
doesn't work)
monet>
01:23:44 manegold@draco:~/Monet/4.3/MonetDB $
========
!???
Stefan
## Comment 1513
Date: 2004-08-17 15:38:04 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
I think this was fixed by the same fix as http://sourceforge.net/support/tracker.php?aid=1000896.
Please check and close the bug report.
## Comment 1514
Date: 2004-08-18 13:08:13 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
seemed to work fine - bug report is now closed :)
## Comment 1515
Date: 2005-10-06 16:38:24 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
TEST ADDED / SUCCESS
## Comment 1516
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 998332 at http://sourceforge.net/support/tracker.php?aid=998332
| ERROR call doesn't get printed | https://api.github.com/repos/MonetDB/MonetDB/issues/282/comments | 0 | 2020-11-30T08:26:52Z | 2024-06-27T10:57:46Z | https://github.com/MonetDB/MonetDB/issues/282 | 753,267,522 | 282 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-23 04:16:52 +0200
From: Jens Teubner <<teubner>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-07-23 05:40:03 +0200
## Comment 1507
Date: 2004-07-23 16:16:52 +0200
From: Jens Teubner <<teubner>>
Consider this example:
a := new (void, int).seqbase (0@0);
a.insert (0@0, 1);
b := new (oid, int);
b.insert (1@0, 10);
b.insert (4@0, 20);
a.print;
b.print;
a.insert (b);
a.print;
The result will be
h tmp_69 name
void int type
-----------------
[ 0@0, 1 ]
[ 1@0, 10 ]
[ 2@0, 20 ]
a's head type was kept void, changing the head of the third tuple (originally
4@0, 20 to 2@0, 20). If I change the first BUN in b, e.g. to 2@0, a's head
is materialized to oid, and all tuples keep their values. The latter behavior
I'd also expect for the former case.
I would expect the head of a to remain void only if b's head is void, and its
seqbase is exactly the last value in a plus 1. (I remember Stefan having it
explained that way.)
A novice as I am, I tried to track down the situation in the source code
(MonetDB-4.3.18), and looked into gdk/gdk_batop.mx, line 80:
if (BAThdense(b) && b->htype == TYPE_void){
...
}
(b is the first argument to insert(), n the second)
Shouldn't this be a ``n>htype == TYPE_void''? The head is already
checked via BAThdense. Tracking down the macros BAThdense and
BAThvoid makes the condition here a bit strange otherwise. If the condition
is correct as in the code, it should easier read
if (b->htype == TYPE_void && b->hseqbase != oid_nil)
## Comment 1508
Date: 2004-07-23 17:40:03 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS (both main branch and MonetDB_4-3-18 branch):
when inserting a [oid,any] BAT into a
[void(seqbase!=oid_nil),any] BAT,
we can omit materialzation of the latter's head as oid only if
the insert densely continues (v)oid range AND the inserted
BAT's head
itself is dense!
## Comment 1509
Date: 2005-10-06 16:26:44 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
ALREADY IN TESTWEB
## Comment 1510
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 996570 at http://sourceforge.net/support/tracker.php?aid=996570
| BAT insert, conversion void-->oid: intended behavior? | https://api.github.com/repos/MonetDB/MonetDB/issues/281/comments | 0 | 2020-11-30T08:26:49Z | 2024-06-27T10:57:45Z | https://github.com/MonetDB/MonetDB/issues/281 | 753,267,503 | 281 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-22 09:27:51 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-08-08 11:06:09 +0200
## Comment 1501
Date: 2004-07-22 21:27:51 +0200
From: @grobian
Consider the following sequence of commands issued by
two clients:
(MonetDB SERIALIZABLE)
> start transaction; -- switch off auto commit
> select count(*) from test;
count
-----
5
> -- at this point the other client does insert into
test + commit
> select count(*) from test; -- should give 5
count
-----
5
> commit;
Error: transaction commit failed
I think the transaction commit failed is far to strict.
Consider the same sequence using PostgreSQL using the
same transaction level:
Postgres with SERIALIZABLE + auto commit
test=> start transaction;
START TRANSACTION
test=> set TRANSACTION ISOLATION LEVEL SERIALIZABLE;
SET
test=> select count(*) from test;
count
-------
2
(1 row)
test=> -- the other client inserts + commits here
test=> select count(*) from test;
count
-------
2
(1 row)
test=> commit;
COMMIT
test=> select count(*) from test;
count
-------
3
(1 row)
## Comment 1502
Date: 2004-07-22 21:35:07 +0200
From: @grobian
Logged In: YES
user_id=963970
I can add no test scripts, since this needs to be done
concurrently using two clients. I will add a JDBC example
that exhibits this behaviour some day.
For now a few other examples that demonstrate it is too
strict at the moment.
Consider a> to be client a, and b> to be client b. Both
clients have by default auto commit enabled. The 'start
transaction' statement switches auto commit mode off.
a> start transaction;
a> select * from tables;
b> select * from tables;
a> commit;
a: error: transaction commit failed.
============
a> start transaction;
a> select * from tables;
b> select * from schemas;
a> commit;
a: error: transaction commit failed
(client a hasn't even touched the table issued by b!!!)
## Comment 1503
Date: 2004-08-08 11:06:09 +0200
From: @njnes
Logged In: YES
user_id=43556
temporary tables (such as the session table) changed the
catalog,
ie made a transaction nessesary. This problem is fixed by
changing
the tables_type column. It is split int tables_istable,
tables_system
and tables_clear also an extra system table tmp_tables is added.
The session table (now called sessions) is now a global
table which
is cleared on transaction boundaries, ie no transaction
rollforward
needed.
## Comment 1504
Date: 2005-10-06 16:23:11 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06
REASSIGN fabian
## Comment 1505
Date: 2005-10-06 21:07:17 +0200
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-10-06: HANDLED BY meltdown
BugDay_2005-10-06: NO TEST / POSTPONE
Needs a JDBC application to test the concurrency.
## Comment 1506
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 996120 at http://sourceforge.net/support/tracker.php?aid=996120
| SQL: TRANSACTION SERIALIZABLE way too tight | https://api.github.com/repos/MonetDB/MonetDB/issues/280/comments | 0 | 2020-11-30T08:26:47Z | 2024-06-27T10:57:44Z | https://github.com/MonetDB/MonetDB/issues/280 | 753,267,471 | 280 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-20 11:57:17 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-07-25 01:09:01 +0200
## Comment 1495
Date: 2004-07-20 23:57:17 +0200
From: @drstmane
Mserver correctly refuses to accept a "shutdown();"
from a non-"adm" client session, but then it crashes
the hard way:
Mserver:
========
23:53:05 manegold@draco:~/Monet/4.3/MonetDB $ Mserver
$MONET_PREFIX/lib/MonetDB/mapi.mil
Monet Database Server V4.3.19
Copyright (c) 1993-2004, CWI. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl for further information.
monet>Mserver:
/ufs/manegold/Monet/4.3/MonetDB/src/common/stream.mx:388:
stream_write: Assertion `s->access == 1' failed.
Aborted (core dumped)
23:53:24 manegold@draco:~/Monet/4.3/MonetDB $
========
MapiClient:
========
23:51:29 manegold@draco:~/Monet/4.3/MonetDB $ MapiClient
Monet Database Server V4.3.19
Copyright (c) 1993-2004, CWI. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl for further information.
mil>shutdown();
No permission for shutdown; quit.
MAPI = anonymous@localhost:50000
ACTION= mapi_next_result
QUERY = shutdown();
ERROR = Connection lost
mil>23:53:27 manegold@draco:~/Monet/4.3/MonetDB $
========
## Comment 1496
Date: 2004-07-21 01:27:05 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS (main branch only, for now) by avoiding
"premature" stream_destroy(GDKout);
However, I don't close this, yet, because the following is
still open:
Is the forced quit in case of a non-adm shutdown(-attempt)
indeed intended ???
Maybe someone knows... ?
## Comment 1497
Date: 2004-07-23 17:41:33 +0200
From: @drstmane
Logged In: YES
user_id=572415
propagated fix to MonetDB_4-3-18 branch.
Question, whether the current behaviour is the intended one
remains open...
## Comment 1498
Date: 2004-07-25 13:09:01 +0200
From: @mlkersten
Logged In: YES
user_id=490798
A client issuing a shutdown() at least intends to terminate
his sesssion.
Thus a quit() as a replacement is hard, but acceptable in
our current setup.
## Comment 1499
Date: 2005-10-06 16:20:24 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06
TEST ADDED / SUCCESS
note: found new bug: type on a MapiClient: kill(0);
## Comment 1500
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 994842 at http://sourceforge.net/support/tracker.php?aid=994842
| "shutdown();" in a non-adm client session crashes Mserver | https://api.github.com/repos/MonetDB/MonetDB/issues/279/comments | 0 | 2020-11-30T08:26:44Z | 2024-06-27T10:57:43Z | https://github.com/MonetDB/MonetDB/issues/279 | 753,267,449 | 279 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-18 07:37:12 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-07-20 05:42:33 +0200
## Comment 1488
Date: 2004-07-18 19:37:12 +0200
From: @grobian
While experimenting with Sesame, the following query
--- which seems to work on MySQL, PostgreSQL, Oracle
and M$SQL Server --- generates a (parser?) error:
INSERT INTO newtriples SELECT inf.* FROM inferred inf
LEFT JOIN triples t ON inf.subject = t.subject AND
inf.predicate = t.predicate AND inf.object = t.object
WHERE t.subject IS NULL;
Error on line 6: Column expression Symbol(27)->token =
Table no output
It is not completely clear to me what is the problem here.
## Comment 1489
Date: 2004-07-19 19:59:16 +0200
From: @grobian
Logged In: YES
user_id=963970
Attached a database dump of sesame where the query applies to...
## Comment 1490
Date: 2004-07-20 17:42:33 +0200
From: @njnes
Logged In: YES
user_id=43556
added missing code for select t.*
## Comment 1491
Date: 2005-10-06 16:06:57 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06
REASSIGN: meltdown
## Comment 1492
Date: 2005-10-06 21:09:37 +0200
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-10-06: HANDLED BY meltdown
BugDay_2005-10-06: NO TEST / MISSING SCRIPTS
I don't have the sesamstraat scripts floating around anymore.
## Comment 1493
Date: 2005-10-06 22:20:47 +0200
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-10-06: HANDLED BY meltdown
BugDay_2005-10-06: TEST ADDED / SUCCESS
sql/src/test/BugDay_2005-10-06_2.9.3/Tests/sesamstr_parser_error.SF-993366.*
## Comment 1494
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 993366 at http://sourceforge.net/support/tracker.php?aid=993366
| SQL: "Table no output" ??? | https://api.github.com/repos/MonetDB/MonetDB/issues/278/comments | 0 | 2020-11-30T08:26:41Z | 2024-06-27T10:57:42Z | https://github.com/MonetDB/MonetDB/issues/278 | 753,267,411 | 278 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-14 07:53:00 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2004-08-18 12:42:29 +0200
## Comment 1480
Date: 2004-07-14 19:53:00 +0200
From: Jan Rittinger <<jan.rittinger>>
a := bat(oid,oid).insert(2@0,1@0).insert(1@0,2@0).insert(0@0,
0@0);
b := a.copy;
b := b.[int];
a := a.[int];
a.[-](b);
b := b.[oid].reverse.[int];
Mserver: /ufs/rittinge/work/MonetDB/src/gdk/gdk_utils.mx:954:
GDKfree: Assertion `(size&2) == 0' failed.
it works without copying (b:=a;)
don't know why - doesn't even matter :)
bug report only for documentation
## Comment 1481
Date: 2004-07-14 20:37:20 +0200
From: @drstmane
Logged In: YES
user_id=572415
the BUG seems to accour only with debugmask=0 (the default);
with debugmask=2 (property checking on new BATs) it is gone;
seems like BATcopy (or someone else) messes-up properties;
any volantiers to investigate this further?
[added test script to CVS]
## Comment 1482
Date: 2004-07-25 16:24:10 +0200
From: @mlkersten
Logged In: YES
user_id=490798
0) error report indicates a malicious free or buffer overflow
1) The command a.[-](b) does not produce the expected output
of three times [i@0,0]. e.g. print(a) produced the orginal
table. Assignment of the expression to a variable is needed
for this, e.g. f:=a.[-](b) to produce the correct result ->
something wrong in multiplex handling.
2) Valgrind identified access to an uninitialized variable
access in multiplex code monet_tbl.mx line 2202. fixed.
3) Valgrind identifies invalid read in Heapfree 230 in a
block already freed.
==23870== Invalid read of size 4
==23870== at 0x40467CAC: HEAPfree (gdk_heap.mx:230)
==23870== by 0x404546EF: HASHremove (gdk_search.mx:409)
==23870== by 0x40454808: HASHdestroy (gdk_search.mx:420)
==23870== by 0x4045B098: ACCremoveall (gdk_search.mx:1223)
==23870== Address 0x4B6BD3B8 is 24 bytes inside a block
of size 36 free'd
==23870== at 0x40029961: free (vg_replace_malloc.c:231)
==23870== by 0x404B7496: GDKfree (gdk_utils.mx:967)
==23870== by 0x40454742: HASHremove (gdk_search.mx:412)
==23870== by 0x40454808: HASHdestroy (gdk_search.mx:420)
Peter should have a look at it from here
## Comment 1483
Date: 2004-07-25 17:28:46 +0200
From: @drstmane
Logged In: YES
user_id=572415
Re. 1)
I indeed do hope that "a.[-](b);" produces no output at all
AND changes neither a nor b... !
It's simply supposed to produce a result, but that's
obviously (and correctly) "lost", since it is not kept in
(i.e., assigned to) any variable.
Hence, indeed only "f:=a.[-](b);" (correctly) allows to
access the (correct) result ...
Thus, the multiplex handling as such is correct.
However, since the heads are not sorted (ascendingly), the
multiplex uses a hash join (I suppose), that "somewhere
there" messes up the handling of the hash table...
## Comment 1484
Date: 2004-08-17 20:24:42 +0200
From: @drstmane
Logged In: YES
user_id=572415
report should be closed, once testing (by hand or
automatically tonight)
confirms that Peter's today's changes do indeed solve the
problem.
## Comment 1485
Date: 2004-08-18 12:42:29 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just to get a "clean desk":
Since the respective test[s] work[s] fine, now, I assume
that Peter's yesterday's changes do indeed fix the bug, and
hence close this report.
## Comment 1486
Date: 2005-10-06 16:03:47 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
ALREADY IN TESTWEB
## Comment 1487
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 991053 at http://sourceforge.net/support/tracker.php?aid=991053
| monet crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/277/comments | 0 | 2020-11-30T08:26:38Z | 2024-06-27T10:57:41Z | https://github.com/MonetDB/MonetDB/issues/277 | 753,267,383 | 277 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-14 03:22:51 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-07-14 06:13:22 +0200
## Comment 1476
Date: 2004-07-14 15:22:51 +0200
From: Jan Rittinger <<jan.rittinger>>
a := bat (void,oid);
a := a.reverse.mark(0@0).reverse;
b := a.reverse.mark(0@0).reverse.[int];
a.leftfetchjoin(b).print;
-------------------------
h tmp_146 name
oid int type
-------------------------
if I use leftfetchjoin I exspect the void column to be still there - at
least it is what I get if there are tuples in the bats
a := bat (void,oid).insert(0@0,0@0);
a := a.reverse.mark(0@0).reverse;
b := a.reverse.mark(0@0).reverse.[int];
a.leftfetchjoin(b).print;
-------------------------
t tmp_146 name
void int type
-------------------------
[ 0@0, 0 ]
## Comment 1477
Date: 2004-07-14 18:13:22 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS (main branch, only):
shrinking the left operand in a fetchjoin to the range that
overlaps with the right operand's (void) head is only needed
(and "reasonable") if neither operand is empty.
net-effect for all "void-lovers" (;-): void heads of the
left operand stay void, "even" if the right operand is empty...
## Comment 1478
Date: 2005-10-06 16:01:27 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
TEST ADDED / SUCCESS
## Comment 1479
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 990857 at http://sourceforge.net/support/tracker.php?aid=990857
| void changes to oid in leftfetchjoin with empty bats | https://api.github.com/repos/MonetDB/MonetDB/issues/276/comments | 0 | 2020-11-30T08:26:36Z | 2024-06-27T10:57:40Z | https://github.com/MonetDB/MonetDB/issues/276 | 753,267,348 | 276 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-13 04:20:56 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-07-14 11:34:54 +0200
## Comment 1472
Date: 2004-07-13 16:20:56 +0200
From: @drstmane
This BUG was originally reported by Jan Rittinger:
========
16:09:15 manegold@draco:~/Monet/4.3/MonetDB $ Mserver
--trace < /tmp/chr_max.mil
Monet Database Server V4.3.19
Copyright (c) 1993-2004, CWI. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl for further information.
monet>a:=new(void,chr).insert(nil,chr(-1)).insert(nil,chr(12));
monet>b:=new(void,chr).insert(nil,chr(12)).insert(nil,chr(-1));
monet>
monet>a.max.int.print;
[ 12 ]
monet>a.[uchr].max.int.print;
[ 12 ]
monet>a.[int].max.int.print;
[ 12 ]
monet>b.max.int.print;
[ -1 ] <======================
monet>b.[uchr].max.int.print;
[ -1 ] <======================
monet>b.[int].max.int.print;
[ 12 ]
monet>
monet>a.min.int.print;
[ -1 ]
monet>a.[uchr].min.int.print;
[ -1 ]
monet>a.[int].min.int.print;
[ -1 ]
monet>b.min.int.print;
[ 12 ] <=====================
monet>b.[uchr].min.int.print;
[ 12 ] <=====================
monet>b.[int].min.int.print;
[ -1 ]
monet>quit();
16:09:19 manegold@draco:~/Monet/4.3/MonetDB $
========
problem is being analysed, and fix will be checked-in soon.
## Comment 1473
Date: 2004-07-14 11:34:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed in CVS, both in the main branch and in the
MonetDB_4-3-18 branch.
[Fix is not (yet?) includes in the source and binary file
releases.)
With types "chr" & "uchr" both having the same ATOMstorage,
but the first being signed, while the latter is unsigned,
code expansion only on ATOMstorage is not sufficient with
other than equallity comparisons and copying. E.g., max &
min need to treat chr & uchr differently.
Fixed this in BATmax & BATmin.
[Probably, there are more places, with similar BUGs,
however, I suspect (hope) that in other cases chr is the
default, not uchr as it was with BATmax & BATmin. This will
hopefully be solved, once we replace the HACKY uchr by a
proper BYTe/ByTE, a 1 byte signed numerical type...]
## Comment 1474
Date: 2005-10-06 15:49:02 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / OBSOLETE
note: the type 'uchr' is depricated
## Comment 1475
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 990184 at http://sourceforge.net/support/tracker.php?aid=990184
| max/min(BAT[any,chr]) give wrong results on non-sorted BATs | https://api.github.com/repos/MonetDB/MonetDB/issues/275/comments | 0 | 2020-11-30T08:26:33Z | 2024-06-27T10:57:39Z | https://github.com/MonetDB/MonetDB/issues/275 | 753,267,323 | 275 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-13 01:26:43 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-07-15 08:54:28 +0200
## Comment 1468
Date: 2004-07-13 13:26:43 +0200
From: @arjan
-- Both these queries should give the same result:
-- View-less version:
CREATE TABLE x (i integer);
INSERT INTO x VALUES (1);
CREATE TABLE y (i integer);
INSERT INTO y VALUES (1);
SELECT * FROM
x a INNER JOIN y ON (a.i = y.i)
;
ROLLBACK;
-- Version with view:
CREATE TABLE x (i integer);
INSERT INTO x VALUES (1);
CREATE VIEW xview AS SELECT * FROM x;
CREATE TABLE y (i integer);
INSERT INTO y VALUES (1);
SELECT a.i FROM
xview a INNER JOIN y ON (a.i = y.i)
;
last query gives the error:
ERROR = !Column: a.i unknown
## Comment 1469
Date: 2004-07-15 08:54:28 +0200
From: @njnes
Logged In: YES
user_id=43556
aliases now allways have a table name and column name
## Comment 1470
Date: 2005-10-06 15:34:49 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
ALREADY IN TESTWEB
## Comment 1471
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 990096 at http://sourceforge.net/support/tracker.php?aid=990096
| SQL: view / alias problem | https://api.github.com/repos/MonetDB/MonetDB/issues/274/comments | 0 | 2020-11-30T08:26:30Z | 2024-06-27T10:57:38Z | https://github.com/MonetDB/MonetDB/issues/274 | 753,267,288 | 274 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-13 11:41:04 +0200
From: Jan Flokstra <<jflokstra>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-07-13 02:00:29 +0200
## Comment 1460
Date: 2004-07-13 11:41:04 +0200
From: Jan Flokstra <<jflokstra>>
In the indexedTail() function at the end of this
message only the else should should be sufficient. But
because of a failure of the BUNptr() call for
[void,chr] BATs I created a workaround in the then branch
/**
* Utility function. It reads the tail value of an
element in a
* [void,any] BAT indexed by oid_index.
*/
ptr indexedTail(BAT* b, oid oid_index) {
ptr res;
if ( BUNsize(b) == 1 ) {
// This is a BUG IN MONET. The else
code should work
// for all situations but does not work
for the
// bat[void,chr] situation
BUN bun = BUNfirst(b);
res = &bun[oid_index];
} else {
oid real_index = oid_index + 1;
BUN bun = BUNptr(b,real_index);
res = BUNtail(b,bun);
}
return res;
}
## Comment 1461
Date: 2004-07-13 12:56:28 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jan,
could you please specify, what exactly the problem is; i.e.,
what is the wrong behaviour of BUNptr() on [void,chr] BATs?
BUNptr is a core macro in MonetDB, used "almost everywhere",
hence,
I would be surprised, if the really was a bug, that hasn't
been detected, yet (after all, [void,chr] BATs are not that
rare or strange ...).
Moreover, I hope, you added the indexedTail function only
temporary to facilitate the use of your work-around.
indexedTail() seems to be other more that a wrapper for
BUNtail(b, BUNptr(b, oid_index)) (or to ensure correct
typing: BUNtail(b, BUNptr(b, (size_t)oid_index)) ). Since
BUNtail and BUNptr are marcos and hence avoid functions
calls in inner loops, your indexedTail() destroys all this
"optimization" be adding an expensive function call...
Stefan
## Comment 1462
Date: 2004-07-13 13:40:13 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Stefan,
The indexedTail() function is indeed a workaround because of
this problem. When everytjhing works properly I will make it
a define.
The problem is that I get a pointer (not nil, and no
segmentation violation) somewhere and the character at that
position is always '0'. When I added the repair code in the
'then' branch it worked properly. I was also surprised it
did not work. I first thought I did something wrong but
after 1 day of trying and use the same code on int,str and
dbl BATs I assumed something was wrong with the BATptr cde.
The place I use the code is in the runtime/xquery.mx file of
the Pathfinder module. I checked this in
the"Core2MIL_Summer2004" CVS thread for pathfinder.
(The monet version I use is 4.3.19, but I could not choose
this in BugTracker)
Jan.
## Comment 1463
Date: 2004-07-13 13:52:27 +0200
From: Jan Flokstra <<jflokstra>>
Logged In: YES
user_id=1054297
Stefan,
I'm really sorry. I just retried the code now without the
then and it seems to work correct now. I had this failure a
week ago and changed a lot and just did not recheck if the
bug still ocurred. I just did and now the pathfinder stuff
works great if I disable the repair branch,
(A deeply embarassed) Jan Flokstra.
## Comment 1464
Date: 2004-07-13 14:00:29 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Not a bug.
## Comment 1465
Date: 2004-07-13 14:14:46 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jan,
no problem, and surely no reason to be "embarassed" ;-)
Stefan
ps: In the BugTracker, the proper Group for MonetDB 4.3.19
is "MonetDB 4.3 CVS Head" ;-)
## Comment 1466
Date: 2005-10-06 15:31:56 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / INVALID
## Comment 1467
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 990024 at http://sourceforge.net/support/tracker.php?aid=990024
| BUNptr() does not work for [void,chr] BATs | https://api.github.com/repos/MonetDB/MonetDB/issues/273/comments | 0 | 2020-11-30T08:26:27Z | 2024-06-28T13:36:23Z | https://github.com/MonetDB/MonetDB/issues/273 | 753,267,246 | 273 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-12 10:21:56 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-07-15 08:54:00 +0200
## Comment 1454
Date: 2004-07-12 10:21:56 +0200
From: @grobian
When importing the VOC database which creates the
following table from SQL:
CREATE TABLE sys.voyages (
number mediumint(9),
number_sup character(1),
trip mediumint(9),
trip_sup character(1),
boatname varchar(50),
master varchar(50),
tonnage mediumint(9),
type_of_boat varchar(30),
built varchar(15),
bought varchar(15),
hired varchar(15),
yard character(1),
chamber character(1),
departure_date varchar(15),
departure_harbour varchar(30),
cape_arrival varchar(15),
cape_departure varchar(15),
arrival_date varchar(15),
arrival_harbour varchar(30),
next_voyage mediumint(9),
particulars varchar(507)
);
the output of the table once imported seems to be: (all
character(1) columns seem to have astronomical values
not even close to what was originally created.)
Database: MonetDB 4.3.19 (4.3)
Driver: MonetDB Native Driver 0.5 beta release (0.5)
Type \q to quit, \h for a list of available commands
auto commit mode: on
monetdb-> \d voyages
CREATE TABLE "sys"."voyages" (
"number" mediumint(9),
"number_sup" character(1160998989),
"trip" mediumint(9),
"trip_sup" character(1160999031),
"boatname" varchar(50),
"master" varchar(50),
"tonnage" mediumint(9),
"type_of_boat" varchar(30),
"built" varchar(15),
"bought" varchar(15),
"hired" varchar(15),
"yard" character(1160999198),
"chamber" character(1160999220),
"departure_date" varchar(15),
"departure_harbour" varchar(30),
"cape_arrival" varchar(15),
"cape_departure" varchar(15),
"arrival_date" varchar(15),
"arrival_harbour" varchar(30),
"next_voyage" mediumint(9),
"particulars" varchar(507)
);
monetdb->
The problem is inline reproducable:
(pictor:~/develop/monetjdbc) fabian% java -jar
jars/MonetJDBC.jar
Welcome to the MonetDB interactive JDBC terminal!
Database: MonetDB 4.3.19 (4.3)
Driver: MonetDB Native Driver 0.5 beta release (0.5)
Type \q to quit, \h for a list of available commands
auto commit mode: on
monetdb-> start transaction;
auto commit mode: off
monetdb-> CREATE TABLE sys.test (
number mediumint(9),
number_sup character(1),
trip mediumint(9),
trip_sup character(1),
boatname varchar(50),
master varchar(50),
tonnage mediumint(9),
type_of_boat varchar(30),
built varchar(15),
bought varchar(15),
hired varchar(15),
yard character(1),
chamber character(1),
departure_date varchar(15),
departure_harbour varchar(30),
cape_arrival varchar(15),
cape_departure varchar(15),
arrival_date varchar(15),
arrival_harbour varchar(30),
next_voyage mediumint(9),
particulars varchar(507)
);
monetdb-( monetdb-( monetdb-( monetdb-( monetdb-(
monetdb-( monetdb-( monetdb-(
monetdb-( monetdb-( monetdb-( monetdb-( monetdb-(
monetdb-( monetdb-( monetdb-(
monetdb-( monetdb-( monetdb-( monetdb-( monetdb-(
monetdb-( affected rows
-------------
-1
monetdb-> \d
TABLE sys.craftsmen
TABLE sys.impotenten
TABLE sys.invoices
TABLE sys.passengers
TABLE sys.seafarers
TABLE sys.soldiers
TABLE sys.test
TABLE sys.total
TABLE sys.voyages
monetdb-> \d test
CREATE TABLE "sys"."test" (
"number" mediumint(9),
"number_sup" character(194024720),
"trip" mediumint(9),
"trip_sup" character(194024772),
"boatname" varchar(50),
"master" varchar(50),
"tonnage" mediumint(9),
"type_of_boat" varchar(30),
"built" varchar(15),
"bought" varchar(15),
"hired" varchar(15),
"yard" character(194024958),
"chamber" character(194024980),
"departure_date" varchar(15),
"departure_harbour" varchar(30),
"cape_arrival" varchar(15),
"cape_departure" varchar(15),
"arrival_date" varchar(15),
"arrival_harbour" varchar(30),
"next_voyage" mediumint(9),
"particulars" varchar(507)
);
monetdb->
## Comment 1455
Date: 2004-07-12 15:30:33 +0200
From: @drstmane
Logged In: YES
user_id=572415
hm, looks as if these huge values are addresses.
is there somewhere a "*" missing or a "&" too much in the code?
## Comment 1456
Date: 2004-07-15 08:54:00 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed typo in parser
## Comment 1457
Date: 2005-10-06 15:29:25 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06
REASSIGN meltdown
## Comment 1458
Date: 2005-10-06 16:00:53 +0200
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-10-06: CLAIMED BY meltdown
BugDay_2005-10-06: TEST ADDED / SUCCESS
sql/src/test/BugDay_2005-10-06_2.9.3/Tests/type_dump_test.SF-989257.*
fixed sql
## Comment 1459
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 989257 at http://sourceforge.net/support/tracker.php?aid=989257
| SQL: SQL server transforms size of character(1) columns | https://api.github.com/repos/MonetDB/MonetDB/issues/272/comments | 0 | 2020-11-30T08:26:23Z | 2024-06-27T10:57:36Z | https://github.com/MonetDB/MonetDB/issues/272 | 753,267,207 | 272 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-08 07:54:15 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-07-08 08:22:40 +0200
## Comment 1450
Date: 2004-07-08 19:54:15 +0200
From: @drstmane
This bug was originally reported by Agustin Schapira
from UMass@Amherst.
When kunion is used on two BATs who's concatenated
heads form a consecutive range of oid's, kunion
correctly marks the head of the result BAT "sorted",
"key", and hence, "dense", but incorrectly sets the
seqbase to "nil".
Hence, subsequent operations that detect the denseness
of the result BAT's head, and try to use the seqbase
for there processing are bound to fail.
See example below.
Fix is about to be finished and checked in.
========
Monet Database Server V4.3.18
Copyright (c) 1993-2004, CWI. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl for further information.
monet>a:=new(oid,int).insert(0@0,0).access(BAT_READ);
monet>b:=new(oid,int).insert(1@0,1).access(BAT_READ);
monet>x:=new(oid,int).insert(a).insert(b).access(BAT_READ).reverse;
monet>c:=b.kunion(a);
monet>d:=a.kunion(b);
monet>x.print;
-----------------
t tmp_28 name
int oid type
-----------------
[ 0, 0@0 ]
[ 1, 1@0 ]
monet>c.print;
-----------------
h tmp_31 name
oid int type
-----------------
[ 1@0, 1 ]
[ 0@0, 0 ]
monet>d.print;
-----------------
h tmp_32 name
oid int type
-----------------
[ 0@0, 0 ]
[ 1@0, 1 ]
monet>x.reverse.seqbase.print;
[ 0@0 ]
monet>c.seqbase.print;
[ 1@0 ]
monet>d.seqbase.print;
monet>e:=x.join(c);
monet>f:=x.join(d);
monet>e.count.print;
[ 2 ]
monet>f.count.print;
[ 0 ]
monet>e.print;
-----------------
h tmp_33 name
int int type
-----------------
[ 0, 0 ]
[ 1, 1 ]
monet>f.print;
-----------------
h tmp_34 name
int int type
-----------------
monet>quit();
========
## Comment 1451
Date: 2004-07-08 20:22:40 +0200
From: @drstmane
Logged In: YES
user_id=572415
Fixed in CVS, both in the MonetDB_4-3-18 branch and in the
main branch (MonetDB-4.3.19).
NOTE: The fix is not (yet?) in the source and binary file
releases.
## Comment 1452
Date: 2005-10-06 15:24:18 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
ALREADY IN TESTWEB
## Comment 1453
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 987455 at http://sourceforge.net/support/tracker.php?aid=987455
| kunion sets wrong seqbase when unioning consecutive ranges | https://api.github.com/repos/MonetDB/MonetDB/issues/271/comments | 0 | 2020-11-30T08:26:20Z | 2024-06-27T10:57:35Z | https://github.com/MonetDB/MonetDB/issues/271 | 753,267,173 | 271 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-08 04:01:33 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2009-11-11 07:54:10 +0100
## Comment 1442
Date: 2004-07-08 16:01:33 +0200
From: @arjan
The astronomers paper inspired me to try a division by
zero in SQL:
sql>select 1/0;
sql_div_single_value name
decimal type
1 tuplecount
0 id
[ --.)*( ]
whereas mil just gives a nil result (which is more
correct).
## Comment 1443
Date: 2004-07-08 16:06:45 +0200
From: @grobian
Logged In: YES
user_id=963970
Is this a bug or a hidden feature? the )*( could be a butter
fly, but I can't seem to figure out what the rest means. A
hidden message from Niels that you shouldn't try to divide
by zero?
## Comment 1444
Date: 2004-07-15 08:53:27 +0200
From: @njnes
Logged In: YES
user_id=43556
proberly handle nil's in dec_tostr
## Comment 1445
Date: 2005-10-06 15:11:37 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06
REASSIGN: meltdown
## Comment 1446
Date: 2005-10-06 15:18:46 +0200
From: @grobian
Logged In: YES
user_id=963970
BugDay_2005-10-06: CLAIMED BY meltdown
BugDay_2005-10-06: TEST ADDED / SUCCESS
src/test/BugDay_2005-10-06_2.9.3/Tests/div_by_zero.SF-987304.*
## Comment 1447
Date: 2009-08-13 18:47:06 +0200
From: @drstmane
re-opened as the test fails since checkins on Thursday Aug 06 2009:
the (IMHO) expected division by zero error is gone; instead, a NULL seems to be returned without comment;
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugDay_2005-10-06_2.9.3/div_by_zero.SF-987304.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugDay_2005-10-06_2.9.3/div_by_zero.SF-987304.err.00.html
## Comment 1448
Date: 2009-11-11 19:54:05 +0100
From: @njnes
closing as the bug is fixed (finally)
## Comment 1449
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 987304 at http://sourceforge.net/support/tracker.php?aid=987304
| SQL: div by zero results in ascii art | https://api.github.com/repos/MonetDB/MonetDB/issues/270/comments | 0 | 2020-11-30T08:26:14Z | 2024-06-27T10:57:34Z | https://github.com/MonetDB/MonetDB/issues/270 | 753,267,107 | 270 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-07 02:30:26 +0200
From: @swingbit
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-07-09 12:49:51 +0200
## Comment 1438
Date: 2004-07-07 14:30:26 +0200
From: @swingbit
If I try this:
*"print"(2);
I get a parsing error, as I expected.
If I type:
(*"print")(2);
this works correctly, as it was print(2).
They both behave as expected when issued separately,
but if you try to use both of them, first the wrong
one, then the correct one, you'll get a segfault.
## Comment 1439
Date: 2004-07-09 12:49:51 +0200
From: @drstmane
Logged In: YES
user_id=572415
In the parser "ll_sugarnode" was not cleared after a parse
error.
Fixed in CVS, both in the MonetDB_4-3-18 branch and the main
branch.
NOTE: The fix is not (yet?) in the source and binary file
releases.
## Comment 1440
Date: 2005-10-06 14:40:15 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
ALREADY IN TESTWEB
## Comment 1441
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 986551 at http://sourceforge.net/support/tracker.php?aid=986551
| Mserver segfault on *"func_name"() | https://api.github.com/repos/MonetDB/MonetDB/issues/269/comments | 0 | 2020-11-30T08:26:11Z | 2024-06-27T10:57:33Z | https://github.com/MonetDB/MonetDB/issues/269 | 753,267,073 | 269 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-07 01:38:19 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-07-13 06:49:11 +0200
## Comment 1434
Date: 2004-07-07 13:38:19 +0200
From: @arjan
Bulk loading from the standard input is not possible.
echo "set auto_commit=true;create table t (i int);copy
into t from stdin;1" | MapiClient -l sql
MapiClient: MapiClient.mx:565: doFileByLines: Assertion
`hdl == ((void *)0)' failed.
Note that when you know on beforehand how many lines
you want to insert, it goes ok: (because the server
stops giving the 'more>' prompt after that number of
lines):
echo "set auto_commit=true;create table t (i int);copy
1 records into t from stdin;1" | MapiClient -l sql
It would be even nicer to have an 'end of file marker'
option, so we can give normal SQL commands again,
afterwards, like Postgres does in the following way
('\.' is the 'eof' marker):
copy into t from stdin;
1
2
3
\.
select count(*) from t;
## Comment 1435
Date: 2004-07-13 18:48:55 +0200
From: @njnes
Logged In: YES
user_id=43556
Following statement works just fine!
echo "create table test ( i int ); copy 1 records into test
from stdin using delimiters ',', '|';1|select * from test;"
| MapiClient -lsql
## Comment 1436
Date: 2005-10-06 14:37:35 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / INVALID BUG
## Comment 1437
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 986525 at http://sourceforge.net/support/tracker.php?aid=986525
| SQL: Bulk load from stdin | https://api.github.com/repos/MonetDB/MonetDB/issues/268/comments | 0 | 2020-11-30T08:26:08Z | 2024-06-28T13:36:22Z | https://github.com/MonetDB/MonetDB/issues/268 | 753,267,033 | 268 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-07-05 10:04:21 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-07-15 08:53:02 +0200
## Comment 1429
Date: 2004-07-05 10:04:21 +0200
From: @arjan
SQL does not handle strange characters inside
identifiers in a correct way, even though the
identifiers are quoted.
sql>create table "\t" (id int);
MAPI = monetdb@localhost:45123
ACTION= read_into_cache
QUERY = create table "\t" (id int);
ERROR = !ERROR: mvc_sql_wrap: operation failed.
Whereas a
create table " " (id int);
*does* work.
Even worse, the server crashes when strange characters
are used inside field names:
create table x ("\t" int); <-- this one works
but then:
select * from x
crashes the server without a message.
Although these queries are pretty rare, Monet should be
able to handle them...
## Comment 1430
Date: 2004-07-05 11:41:24 +0200
From: @arjan
Logged In: YES
user_id=20087
Fabians comment:
dat je een kolom met een - of _ erin wilt hebben, ok, maar
een kolom met \t of \n erin......
boek van niels:
... is up to 128 characters long, from one character set.
regular identifier = 128 char, consists of only letters,
digits and underscores. Starts with a letter. A letter can
also be an accented character.
sql language identifier: regular identifier with only latin
characters
Very scary.
----
However, the server should not crash, but give a decent
error message instead, if anything (table / view / schema)
with illegal identifier names is created.
## Comment 1431
Date: 2004-07-15 08:53:02 +0200
From: @njnes
Logged In: YES
user_id=43556
disallow strange characters in identifiers
## Comment 1432
Date: 2005-10-06 14:36:31 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
ALREADY IN TESTWEB
## Comment 1433
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 985242 at http://sourceforge.net/support/tracker.php?aid=985242
| SQL: quotes in identifiers | https://api.github.com/repos/MonetDB/MonetDB/issues/267/comments | 0 | 2020-11-30T08:26:05Z | 2024-06-27T10:57:31Z | https://github.com/MonetDB/MonetDB/issues/267 | 753,266,994 | 267 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-30 11:22:21 +0200
From: @arjan
To: @mlkersten
Version: -- development
Last updated: 2004-09-10 10:21:51 +0200
## Comment 1422
Date: 2004-06-30 11:22:21 +0200
From: @arjan
1) The config setting 'monet_clients' does not work as
expected. The number of clients seems to be hardcoded
at 32 (monet_client.mx:47).
2) The documentation in monet_client.mx says this is
maxclients setting is a compile-time option, but this
is not true either.
3) The mapi_listen procs have a maxclients parameter,
but this has no effect on the max number of clients; 32
is still the max.
## Comment 1423
Date: 2004-06-30 12:34:51 +0200
From: @arjan
Logged In: YES
user_id=20087
Test script is attached.
gcc -o clientmeltdown clientmeltdown.c `monet-config
--cflags --libs` -lMapi -lpthread
## Comment 1424
Date: 2004-06-30 17:01:46 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
There was a bug in kernel.mx where it assumed that
forkClient would return a valid pointer, which wasn't
necessarily the case.
I also added pthread_join calls to the end of the
clientmeltdown program so that the threads get time to do
something before the main thread exits.
There remains the problem that the meltdown program doesn't
report failures and just hangs, so not closing yet.
## Comment 1425
Date: 2004-09-09 23:45:12 +0200
From: @mlkersten
Logged In: YES
user_id=490798
working on it
## Comment 1426
Date: 2004-09-10 22:21:51 +0200
From: @mlkersten
Logged In: YES
user_id=490798
MAXCLIENTS is increased.
It is possible to change the code base to handle a larger
number of concurrent client connections. The easiest way is
to change the constant MAXCLIENTS and recompile the system.
Note, each actual connection requires 4 Mb of stack space.
A more flexible way is to introduce an externally changable
parameter. This track was not followed, because we should
minimize the number of 'knobs' to turn. The option has been
removed from the configuration file.
## Comment 1427
Date: 2005-10-06 14:34:37 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / OBSOLETE
note: see bug: 1305797
## Comment 1428
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 982608 at http://sourceforge.net/support/tracker.php?aid=982608
| max. number of clients | https://api.github.com/repos/MonetDB/MonetDB/issues/266/comments | 0 | 2020-11-30T08:26:01Z | 2024-06-28T13:36:21Z | https://github.com/MonetDB/MonetDB/issues/266 | 753,266,958 | 266 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-30 04:01:57 +0200
From: William Dowling <<wdowling>>
To: @sjoerdmullender
Version: -- development
Last updated: 2004-06-30 04:35:19 +0200
## Comment 1415
Date: 2004-06-30 04:01:57 +0200
From: William Dowling <<wdowling>>
I have a failure running make after a clean unpack and
configure of MonetDB-4.3.18_rc02. Here is the failure.
My (Debian) configuration info follows.
make[9]: Entering directory
`/usr/local/src/MonetDB-4.3.18_rc02/src/mapi/clients/python/Cimpl'
/bin/sh ../../../../../libtool --mode=compile gcc
-DHAVE_CONFIG_H -I. -I. -I../../../../.. -I. -I../../C
-I -g -O2 -Wall -W -c -o MapiLib.py.lo `test -f
'MapiLib.py.c' || echo './'`MapiLib.py.c
gcc -DHAVE_CONFIG_H -I. -I. -I../../../../.. -I.
-I../../C -I -g -O2 -Wall -W -c MapiLib.py.c -fPIC
-DPIC -o MapiLib.py.lo
MapiLib.py.c:13: Python.h: No such file or directory
MapiLib.py.c:289: Python.h: No such file or directory
make[9]: *** [MapiLib.py.lo] Error 1
make[9]: Leaving directory
`/usr/local/src/MonetDB-4.3.18_rc02/src/mapi/clients/python/Cimpl'
make[8]: *** [all-recursive] Error 1
make[8]: Leaving directory
`/usr/local/src/MonetDB-4.3.18_rc02/src/mapi/clients/python/Cimpl'
make[7]: *** [all] Error 2
make[7]: Leaving directory
`/usr/local/src/MonetDB-4.3.18_rc02/src/mapi/clients/python/Cimpl'
make[6]: *** [all-recursive] Error 1
make[6]: Leaving directory
`/usr/local/src/MonetDB-4.3.18_rc02/src/mapi/clients/python'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory
`/usr/local/src/MonetDB-4.3.18_rc02/src/mapi/clients'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/usr/local/src/MonetDB-4.3.18_rc02/src/mapi'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/usr/local/src/MonetDB-4.3.18_rc02/src/mapi'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/usr/local/src/MonetDB-4.3.18_rc02/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/usr/local/src/MonetDB-4.3.18_rc02'
make: *** [all] Error 2
OS: Debian GNU/Linux (testing)
$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20011002 (Debian prerelease)
$ flex --version
flex version 2.5.4
$ yacc --version
bison (GNU Bison) 1.875a
Written by Robert Corbett and Richard Stallman.
$ autoconf --version
autoconf (GNU Autoconf) 2.59
$ automake --version
automake (GNU automake) 1.4-p4
$ libtool --version
ltmain.sh (GNU libtool) 1.5.2 (1.1220.2.60 2004/01/25
12:25:08) Debian: 192 $
$ swig -version
SWIG Version 1.3.21
$ python -V
Python 2.3.3
## Comment 1416
Date: 2004-06-30 09:31:13 +0200
From: @drstmane
Logged In: YES
user_id=572415
William,
thank you very much for your report.
I'm not quite sure, but it could be that the python-dev
package (which contains a.o. then Python.h file) is not
installed on your system.
Hence, could you please check that? (See below for a log of
what I just did on our Debian-3.0 machine.)
In case the python-dev package is not (yet) installed on
your machine, you need to install it to be able to compile
this part of MonetDB.
In case the python-dev package *is* installed on your
machine, but the compilation does (still) fail, please let
us know!
Of course, we should check (during configure), whether the
Python.h is indeed available, and skip compilation of those
parts of MonetDB that do require Python.h, instead of
running into a compilation error. Sorry for the
inconvenience; we'll fix this asap.
Sjoerd,
could you please take care of adding the proper checks for
Python.h to
configure / conf/monet.m4 ?
Thanks you very much in advance.
Stefan
========
Linux spin 2.4.24 2 SMP Sat Jan 10 02:30:19 CET 2004 x86_64
GNU/Linux
09:22:00 manegold@spin:~ $ locate Python.h
/usr/include/python2.2/Python.h
09:22:04 manegold@spin:~ $ dpkg -S
/usr/include/python2.2/Python.h
python2.2-dev: /usr/include/python2.2/Python.h
09:22:08 manegold@spin:~ $ dpkg -l | grep -i 'python.*-dev'
ii python2.2-dev 2.2.1-4.3 Header files and a static
library for Python
09:22:11 manegold@spin:~ $
========
## Comment 1417
Date: 2004-06-30 10:21:02 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
William, what does this command print (all on one line):
python -c 'import distutils.sysconfig; print
distutils.sysconfig.get_python_inc()'
Stefan, I'll make the changes you requested. In fact, I
started already before I saw your reply :-).
## Comment 1418
Date: 2004-06-30 16:26:19 +0200
From: William Dowling <<wdowling>>
Logged In: YES
user_id=95118
Thanks for your quick and helpful response. I followed the
suggestion to install the python-dev Debian package, which
had not previously been installed. After rerunning the
configure script the build went through to completion
without error.
Thanks again,
William Dowling
## Comment 1419
Date: 2004-06-30 16:35:19 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Closing as fixed.
The bug was not so much that swig didn't compile without
python development libraries, but that it was attempted at
all. By fixing conf/monet.m4 I hope to have solved the problem.
## Comment 1420
Date: 2005-10-06 14:28:24 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / COMPILATION
## Comment 1421
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 982393 at http://sourceforge.net/support/tracker.php?aid=982393
| build failure: swig/python | https://api.github.com/repos/MonetDB/MonetDB/issues/265/comments | 0 | 2020-11-30T08:25:58Z | 2024-06-27T10:57:29Z | https://github.com/MonetDB/MonetDB/issues/265 | 753,266,919 | 265 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-29 03:42:56 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2004-08-18 12:42:07 +0200
## Comment 1408
Date: 2004-06-29 15:42:56 +0200
From: Jan Rittinger <<jan.rittinger>>
MapiClient gives the following output (and Mserver crashes without a
word):
!WARNING: CTcheck_hl: histogram disappeared!
!ERROR: Mserver internal error (Segmentation fault), please restart.
!ERROR: (One potential cause could be that your disk might be full...
)
The problem is triggered with more or less the following idea (see
attachement for real example):
var a := bat(.....
var b := a;
a := a.tunique;
a := nil;
var c := b.dosomething;
b := nil;
If b is a explicit copy of a it works fine. Without the tunique it also
avoids a crash.
## Comment 1409
Date: 2004-06-29 15:46:01 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Sorry, already posted the same bug before (http://sourceforge.
net/tracker/index.php?
func=detail&aid=978814&group_id=56967&atid=482468). It seemed to
me like it was caused by something different - perhaps not.
## Comment 1410
Date: 2004-07-14 20:38:13 +0200
From: @drstmane
Logged In: YES
user_id=572415
added test script to CVS
## Comment 1411
Date: 2004-08-17 20:22:57 +0200
From: @drstmane
Logged In: YES
user_id=572415
assigned to Peter, as he took care of this;
report should be closed, once testing (by hand or
automatically tonight)
confirms that Peter's today's changes do indeed solve the
problem.
## Comment 1412
Date: 2004-08-18 12:42:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just to get a "clean desk":
Since the respective test[s] work[s] fine, now, I assume
that Peter's yesterday's changes do indeed fix the bug, and
hence close this report.
## Comment 1413
Date: 2005-10-06 14:27:25 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_1005-10-06: Done.
ALREADY IN TESTWEB
note: test is located in XQuery module (although it should
be in MonetDB module)
## Comment 1414
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 981954 at http://sourceforge.net/support/tracker.php?aid=981954
| !WARNING: CTcheck_hl: histogram disappeared! | https://api.github.com/repos/MonetDB/MonetDB/issues/264/comments | 0 | 2020-11-30T08:25:55Z | 2024-06-27T10:57:28Z | https://github.com/MonetDB/MonetDB/issues/264 | 753,266,879 | 264 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-28 06:57:44 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2004-08-18 01:13:01 +0200
## Comment 1399
Date: 2004-06-28 18:57:44 +0200
From: Jan Rittinger <<jan.rittinger>>
Mserver runs with module(aggrX3)
var var_usage := bat(oid,oid).insert(0@0,1@0).insert(1@0,1@0);
without the next line it doesn't crash
var_usage := var_usage.unique.reverse;
var vu_vid := var_usage.reverse.mark(1000@0).reverse;
var vu_fid := var_usage.mark(1000@0).reverse;
var sorting := vu_fid.CTrefine(vu_vid);
Mserver: /ufs/rittinge/work/MonetDB/src/gdk/gdk_qsort.mx:323:
GDKqsort: Assertion `tpe != 0' failed.
Aborted
var var_usage := bat(oid,oid).insert(0@0,1@0).insert(1@0,1@0);
without the next line it doesn't crash
var_usage := var_usage.reverse.sort;
var vu_vid := var_usage.reverse.mark(1000@0).reverse;
var vu_fid := var_usage.mark(1000@0).reverse;
var sorting := vu_fid.CTrefine(vu_vid);
Mserver: /ufs/rittinge/work/MonetDB/src/gdk/gdk_qsort.mx:323:
GDKqsort: Assertion `tpe != 0' failed.
Aborted
## Comment 1400
Date: 2004-06-28 23:14:55 +0200
From: @drstmane
Logged In: YES
user_id=572415
CTrefine fails, if the tail of the second argument is void,
since GDKqsort (obviously) does not work on voids.
"wild guess": we simply can skip the local (re-)sorting,
if the seconds argument'\''s tail is void.
Jan,
could you please check, whether this indeed solves your problem?
Stefan
## Comment 1401
Date: 2004-06-29 10:11:05 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
My problem is already solved, by rewritting the query.
But in theory a view with (void,void) can be the input as second
parameter. Example: You have to columns sorted on the first then on the
second - the first one is dense and now you want to change the sorting.
The originally second one will change the order and so the old first one
which is void in tail has to be materialized and rearranged.
Jan
## Comment 1402
Date: 2004-06-29 16:58:24 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Ok found an example, where the actual solution doesn't solve the
problem. Unique is needed because it is not clear before translation if
doubles occur and here the head of var_usage gets void after unique:
var_usage := bat(oid,oid);
var_usage.insert(0@0,1@0);
var_usage.insert(1@0,1@0);
var_usage := var_usage.unique;
var_usage := var_usage.reverse;
var_usage.access(BAT_READ);
vu_fid := var_usage.mark(1000@0).reverse;
vu_vid := var_usage.reverse.mark(1000@0).reverse;
var_usage := nil;
var sorting := vu_fid.reverse.sort.reverse;
sorting := sorting.CTrefine(vu_vid);
sorting := sorting.mark(1000@0).reverse;
vu_vid := sorting.leftfetchjoin(vu_vid);
vu_fid := sorting.leftfetchjoin(vu_fid);
sorting := nil;
## Comment 1403
Date: 2004-06-29 22:11:09 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jan,
With my yesterdays' fixes in the main branch (4.3.19),
you latest example does not crash (anymore), and give the
result below.
Is that, what you would expect?
Stefan
========
22:09:57 manegold@draco:~/Monet/4.3/MonetDB $ Mserver
--trace < /tmp/ID.981374.mil.2
Monet Database Server V4.3.19
Copyright (c) 1993-2004, CWI. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl for further information.
monet>module(xtables);
monet>module(malalgebra);
monet>
monet>var_usage := bat(oid,oid);
monet>var_usage.insert(0@0,1@0);
monet>var_usage.insert(1@0,1@0);
monet>var_usage := var_usage.unique;
monet>var_usage := var_usage.reverse;
monet>var_usage.access(BAT_READ);
monet>vu_fid := var_usage.mark(1000@0).reverse;
monet>vu_fid.print;
-----------------
h tmp_30 name
void oid type
-----------------
[ 1000@0, 1@0 ]
[ 1001@0, 1@0 ]
monet>vu_vid := var_usage.reverse.mark(1000@0).reverse;
monet>vu_vid.print;
-----------------
t tmp_28 name
void void type
-----------------
[ 1000@0, 0@0 ]
[ 1001@0, 1@0 ]
monet>var_usage := nil;
monet>var sorting := vu_fid.reverse.sort.reverse;
monet>sorting.print;
-----------------
h tmp_31 name
void oid type
-----------------
[ 1000@0, 1@0 ]
[ 1001@0, 1@0 ]
monet>sorting := sorting.CTrefine(vu_vid);
monet>sorting.print;
-----------------
h tmp_32 name
oid oid type
-----------------
[ 1000@0, 1@0 ]
[ 1001@0, 1@0 ]
monet>sorting := sorting.mark(1000@0).reverse;
monet>sorting.print;
-----------------
t tmp_31 name
void oid type
-----------------
[ 1000@0, 1000@0 ]
[ 1001@0, 1001@0 ]
monet>vu_vid := sorting.leftfetchjoin(vu_vid);
monet>vu_vid.print;
-----------------
h tmp_33 name
void oid type
-----------------
[ 1000@0, 0@0 ]
[ 1001@0, 1@0 ]
monet>vu_fid := sorting.leftfetchjoin(vu_fid);
monet>vu_fid.print;
-----------------
h tmp_28 name
void oid type
-----------------
[ 1000@0, 1@0 ]
[ 1001@0, 1@0 ]
monet>sorting := nil;
monet>quit();
22:10:06 manegold@draco:~/Monet/4.3/MonetDB $
========
## Comment 1404
Date: 2004-08-18 10:39:44 +0200
From: @drstmane
Logged In: YES
user_id=572415
Peter,
my "hacky fix" was the following. Could you please check,
whether that's OK, or whether (and how) it should be fixed
instead?
Thanks in advance!
========
date: 2004/06/28 21:13:18; author: stmane; state: Exp;
lines: +12 -7
CTrefine fails, if the tail of the second argument is void
(cf. BUG #981374: "Mserver crashes with CTrefine + not
sorted argument"),
since GDKqsort (obviously) does not work on voids.
"wild guess": we simply can skip the local (re-)sorting,
if the seconds argument's tail is void.
========
10:36:02 manegold@draco:~/Monet/4.3/MonetDB $ cvs diff
-r1.3{1,2} src/modules/plain/xtables.mx
Index: src/modules/plain/xtables.mx
===================================================================
RCS file:
/cvsroot/monetdb/MonetDB/src/modules/plain/xtables.mx,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- src/modules/plain/xtables.mx 24 Jun 2004 20:01:46
-0000 1.31
+++ src/modules/plain/xtables.mx 28 Jun 2004 21:13:18
-0000 1.32
@@ -21,7 +21,7 @@
@' Niels Nes <Niels.Nes@cwi.nl>
@' Stefan Manegold <Stefan.Manegold@cwi.nl>
-@a M.L. Kersten, P. Boncz, A.P. de Vries -- $Id:
xtables.mx,v 1.31 2004/06/24 20:01:46 stmane Exp $
+@a M.L. Kersten, P. Boncz, A.P. de Vries -- $Id:
xtables.mx,v 1.32 2004/06/28 21:13:18 stmane Exp $
@f xtables
@t Cross Table Module
@v 2.2
@@ -1176,12 +1176,16 @@
oid id = *idp + 1;
ptr cur, val;
- /* qsort works fine for small amount of tuples; with
few duplicates */
- if (reverse) {
- GDKqsort_rev(buf, base, size,
(int)sizeof(struct refine), tpe, offsetof(struct refine, off));
- } else {
- GDKqsort(buf, base, size, (int)sizeof(struct
refine), tpe, offsetof(struct refine, off));
+ /* StM: we don't need to sort voids, do we??? */
+ if (tpe != TYPE_void) {
+ /* qsort works fine for small amount of
tuples; with few duplicates */
+ if (reverse) {
+ GDKqsort_rev(buf, base, size,
(int)sizeof(struct refine), tpe, offsetof(struct refine, off));
+ } else {
+ GDKqsort(buf, base, size,
(int)sizeof(struct refine), tpe, offsetof(struct refine, off));
+ }
}
+
cur = base + buf->off;
while(buf < end) {
val = base + buf->off;
@@ -1263,7 +1267,8 @@
GDKfree(buf);
bn->batBuns->free = ((BUN) dst) - bn->batBuns->base;
bn->tsorted = 1;
- } *res = bn;
+ }
+ *res = bn;
return GDK_SUCCEED;
}
10:36:25 manegold@draco:~/Monet/4.3/MonetDB $
========
## Comment 1405
Date: 2004-08-18 13:13:01 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Hi Stefan,
I think your fix is ok.
- gdk_qsort asserts on void sequences
- void sequences indeed do not need sorting
## Comment 1406
Date: 2005-10-06 14:18:35 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
CLAIMED BY vzzzbx
TEST ADDED / SUCCESS
## Comment 1407
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 981374 at http://sourceforge.net/support/tracker.php?aid=981374
| Mserver crashes with CTrefine + not sorted argument | https://api.github.com/repos/MonetDB/MonetDB/issues/263/comments | 0 | 2020-11-30T08:25:52Z | 2024-06-28T13:36:21Z | https://github.com/MonetDB/MonetDB/issues/263 | 753,266,852 | 263 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-25 05:30:58 +0200
From: georgina ramirez <<grcamps>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-06-28 04:55:27 +0200
## Comment 1395
Date: 2004-06-25 17:30:58 +0200
From: georgina ramirez <<grcamps>>
When using the "import" function from the ascii_io
module and importing a file that contains strings
"nil", the bat obtained contains nil values instead of
the "nil" strings.
Example of file to be imported:
0@0,"hello"
1@0,"nil"
2@0,"world"
3@0,"nil"
4@0,"bye"
5@0,"world"
result table:
-------------------------
h tmp_29 name
oid str type
-------------------------
[ 0@0, "hello" ]
[ 1@0, nil ]
[ 2@0, "world" ]
[ 3@0, nil ]
[ 4@0, "bye" ]
[ 5@0, "world" ]
Tryied on spin with MonetDB 4.3.18 compiled with 64 bits.
Attached is a small test: 'word_file.txt' contains the
file to import and 'import_nil.mil' is the script that
imports the table.
## Comment 1396
Date: 2004-06-28 16:55:26 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in 4.3.18
## Comment 1397
Date: 2005-10-06 13:39:09 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
ALREADY IN TESTWEB
## Comment 1398
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 979809 at http://sourceforge.net/support/tracker.php?aid=979809
| import (ascii_io) converts "nil" words to nil values | https://api.github.com/repos/MonetDB/MonetDB/issues/262/comments | 0 | 2020-11-30T08:25:49Z | 2024-06-27T10:57:26Z | https://github.com/MonetDB/MonetDB/issues/262 | 753,266,813 | 262 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-25 09:59:00 +0200
From: @joerivanruth
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-06-29 09:53:44 +0200
## Comment 1391
Date: 2004-06-25 09:59:00 +0200
From: @joerivanruth
The documentation talks about a .monet.conf which can
be put in your $HOME directory. This doesn't seem to
work.
Grepping through the source makes clear why:
; fgrep .monet.conf **/*(.)
doc/monet.mx:The third possibility, a {\tt .monet.conf}
in your home directory is the most common approach
doc/monet.mx:and installation paths, copy it to {\tt
\$HOME/.monet.conf} and start editing it.\\
src/gdk/gdk_utils.mx:Parse a possible .monet.conf file
lying around in the current directory,
src/gdk/gdk_utils.mx:to keep the absolute path to the
.monet.conf file for top-levels
src/gdk/gdk_utils.mx: fprintf(stderr,"\t\tdefault:
.monet.conf in current/home directory\n");
.monet.conf is only mentioned in documentation, not in
the code.
Please remove the documentation or implement the feature.
Joeri
## Comment 1392
Date: 2004-06-29 21:53:44 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed documentation about "monet.conf":
MonetDB looks for "monet.conf" only in three place:
- the default: <prefix>/etc/monet.conf
- the one specified via environment variable $MONET_CONFIG
- the one give via commandline option "-c"/"--config"
## Comment 1393
Date: 2005-10-06 13:36:29 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
NO TEST / DOCUMENTATION
## Comment 1394
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 979556 at http://sourceforge.net/support/tracker.php?aid=979556
| .monet.conf does not work as promised. | https://api.github.com/repos/MonetDB/MonetDB/issues/261/comments | 0 | 2020-11-30T08:25:46Z | 2024-06-27T10:57:25Z | https://github.com/MonetDB/MonetDB/issues/261 | 753,266,778 | 261 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-25 09:51:11 +0200
From: @joerivanruth
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-06-25 04:17:49 +0200
## Comment 1387
Date: 2004-06-25 09:51:11 +0200
From: @joerivanruth
Currently, "make html" puts the documentation directly
in the $(prefix)/doc directory. This is inconsistent
with, say, the $(prefix)/lib and $(prefix)/include,
where a directory MonetDB is created.
From the name /usr/local/doc/www it is not entirely
clear that we are looking at Monet documentation. I
suggest switching to $(prefix)/doc/MonetDB.
Joeri
## Comment 1388
Date: 2004-06-25 16:17:49 +0200
From: @drstmane
Logged In: YES
user_id=572415
"make html" now installs the documentation in
$(prefix)/doc/MonetDB.
## Comment 1389
Date: 2005-10-06 13:34:46 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
CLAIMED BY vzzzbx
NO TEST / COMPILATION
## Comment 1390
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 979549 at http://sourceforge.net/support/tracker.php?aid=979549
| make html should create $(prefix)/doc/MonetDB | https://api.github.com/repos/MonetDB/MonetDB/issues/260/comments | 0 | 2020-11-30T08:25:43Z | 2024-06-27T10:57:24Z | https://github.com/MonetDB/MonetDB/issues/260 | 753,266,751 | 260 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-24 11:35:33 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2004-08-18 12:41:49 +0200
## Comment 1381
Date: 2004-06-24 11:35:33 +0200
From: Jan Rittinger <<jan.rittinger>>
MapiClient produces this error message:
!WARNING: CTcheck_hl: histogram disappeared!
and Mserver crashes with the following message:
Mserver: .../work/MonetDB/src/gdk/gdk_utils.mx:953: GDKfree:
Assertion `(size&2) == 0' failed.
Used MonetDB V4.3.17 with module(xtables) and module(pathfinder)
Added a new PROC (merged_union) to the pathfinder module
(summer branch) and used it inside the code generation for testing
if the ouput is correct.
The error only appears if both old version of merged union and new
version are used together and only the second time (line 237- ...).
The code producing the error is in the attachment.
## Comment 1382
Date: 2004-07-14 20:37:55 +0200
From: @drstmane
Logged In: YES
user_id=572415
added test script to CVS
## Comment 1383
Date: 2004-08-17 20:23:23 +0200
From: @drstmane
Logged In: YES
user_id=572415
assigned to Peter, as he took care of this;
report should be closed, once testing (by hand or
automatically tonight)
confirms that Peter's today's changes do indeed solve the
problem.
## Comment 1384
Date: 2004-08-18 12:41:49 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just to get a "clean desk":
Since the respective test[s] work[s] fine, now, I assume
that Peter's yesterday's changes do indeed fix the bug, and
hence close this report.
## Comment 1385
Date: 2005-10-06 13:22:52 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done
CLAIMED BY vzzzbx
ALREADY IN TESTWEB
(test is in in XQuery module)
## Comment 1386
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 978814 at http://sourceforge.net/support/tracker.php?aid=978814
| !WARNING: CTcheck_hl: histogram disappeared! | https://api.github.com/repos/MonetDB/MonetDB/issues/259/comments | 0 | 2020-11-30T08:25:41Z | 2024-06-27T10:57:23Z | https://github.com/MonetDB/MonetDB/issues/259 | 753,266,725 | 259 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-23 10:25:12 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-07-15 08:52:26 +0200
## Comment 1374
Date: 2004-06-23 10:25:12 +0200
From: @arjan
Any union query:
select name from tables union select name from tables;
crashes server without a message.
## Comment 1375
Date: 2004-06-23 12:54:35 +0200
From: @arjan
Logged In: YES
user_id=20087
OK, so the syntax is wrong (apparently). That should not
crash the server, however.
Especially since MySQL and postgres do support this
particular syntax.
## Comment 1376
Date: 2004-06-24 08:51:20 +0200
From: @njnes
Logged In: YES
user_id=43556
added missing scope
## Comment 1377
Date: 2004-07-05 21:27:13 +0200
From: @drstmane
Logged In: YES
user_id=572415
re-opend this bug report, as Niels' fix seems to have
"disappeared" somewhere --- at least the respective test
script still fails both with the stable and the current
version...
## Comment 1378
Date: 2004-07-15 08:52:26 +0200
From: @njnes
Logged In: YES
user_id=43556
initialized a scope for union queries
## Comment 1379
Date: 2005-10-06 13:32:56 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
CLAIMED BY vzzzbx
ALREADY IN TESTWEB
## Comment 1380
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 978045 at http://sourceforge.net/support/tracker.php?aid=978045
| SQL: UNION queries | https://api.github.com/repos/MonetDB/MonetDB/issues/258/comments | 0 | 2020-11-30T08:25:38Z | 2024-06-27T10:57:22Z | https://github.com/MonetDB/MonetDB/issues/258 | 753,266,694 | 258 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-23 10:22:58 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-06-24 08:55:44 +0200
## Comment 1370
Date: 2004-06-23 10:22:58 +0200
From: @arjan
Following INSERT crashes server:
create table test2 (x integer, y varchar(255));
insert into test2 (y) select name from tables;
sql_session.mx:429: sqlexecute: Assertion `s' failed.
## Comment 1371
Date: 2004-06-24 08:55:44 +0200
From: @njnes
Logged In: YES
user_id=43556
the missing columns for a partial insert where not properly
added
## Comment 1372
Date: 2005-10-06 13:30:43 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
CLAIMED BY vzzzbx
ALREADY IN TESTWEB
## Comment 1373
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 978043 at http://sourceforge.net/support/tracker.php?aid=978043
| SQL: INSERT...SELECT on column subset | https://api.github.com/repos/MonetDB/MonetDB/issues/257/comments | 0 | 2020-11-30T08:25:35Z | 2024-06-27T10:57:22Z | https://github.com/MonetDB/MonetDB/issues/257 | 753,266,658 | 257 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-22 09:53:32 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-06-24 09:14:56 +0200
## Comment 1364
Date: 2004-06-22 21:53:32 +0200
From: @grobian
creating odbcsample1
make[4]: Leaving directory
`/home/fabian/monet/sql/src/odbc/samples'
Making all in python
make[4]: Entering directory
`/home/fabian/monet/sql/src/odbc/python'
swig -python -DHAVE_LONG_LONG -I./../include -outdir .
-o odbc.py.c odbc.py.i
odbc.py.i:40: Unable to find '/usr/include/sqltypes.h'
odbc.py.i:1083: Unable to find '/usr/include/sql.h'
odbc.py.i:1102: Unable to find '/usr/include/sqlext.h'
make[4]: *** [odbc.py.c] Error 1
make[4]: Leaving directory
`/home/fabian/monet/sql/src/odbc/python'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/home/fabian/monet/sql/src/odbc'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/fabian/monet/sql/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/fabian/monet/sql'
make: *** [all] Error 2
Looking in '/usr/include/' for monet includes is just
wrong if I use a different prefix, IMHO.
## Comment 1365
Date: 2004-06-22 22:18:38 +0200
From: @drstmane
Logged In: YES
user_id=572415
Both automatic testing and me always use "configure
--prefix=something/else", but we never have problems ... !??
Which version of MonetDB/SQL do you use ("Group" not
specified ...)?
Did you compile from scratch? (i.e., rm -rf <BUILD_DIR> ;
de-bootstrap ; bootstrap ; configure --prefix=something/else
; make ; make install) ?
## Comment 1366
Date: 2004-06-23 07:25:44 +0200
From: @grobian
Logged In: YES
user_id=963970
I had it both on a complete clean anonymous checkout on a
PPC/Linux and with an update using my dev-acct on my PC.
So in the first case it was all clean, in the second I threw
away the build dir, like you described.
The bootstrap did the following on both machines:
automake 1.6.3 is 1.5 or newer. Good.
autoconf 2.59 is 2.53 or newer. Good.
libtool 1.5.2 is 1.4 or newer. Good.
Python 2.3.4 is 2.0.0 or newer. Good.
/nfs/poseidon/Temp/monet/src-head/sql/conf
/nfs/poseidon/Temp/monet/src-head/sql/src
/nfs/poseidon/Temp/monet/src-head/sql/src/server
/nfs/poseidon/Temp/monet/src-head/sql/src/backends
/nfs/poseidon/Temp/monet/src-head/sql/src/backends/monet4
/nfs/poseidon/Temp/monet/src-head/sql/src/backends/monet5
/nfs/poseidon/Temp/monet/src-head/sql/src/odbc
/nfs/poseidon/Temp/monet/src-head/sql/src/odbc/include
/nfs/poseidon/Temp/monet/src-head/sql/src/odbc/setup
/nfs/poseidon/Temp/monet/src-head/sql/src/odbc/driver
/nfs/poseidon/Temp/monet/src-head/sql/src/odbc/samples
/nfs/poseidon/Temp/monet/src-head/sql/src/odbc/python
/nfs/poseidon/Temp/monet/src-head/sql/src/jdbc
/nfs/poseidon/Temp/monet/src-head/sql/src/tools
Remember to add `AC_PROG_LIBTOOL' to `configure.in'.
Putting files in AC_CONFIG_AUX_DIR, `conf'.
automake/aclocal 1.6.3 is older than 1.7.
Patching aclocal.m4 for Intel compiler on Linux (icc/ecc).
patching file aclocal.m4
Hunk 1 FAILED at 2542.
1 out of 1 hunk FAILED -- saving rejects to file aclocal.m4.rej
patching file aclocal.m4
Hunk 1 FAILED at 1184.
Hunk 2 FAILED at 2444.
Hunk 3 FAILED at 2464.
3 out of 3 hunks FAILED -- saving rejects to file aclocal.m4.rej
## Comment 1367
Date: 2004-06-24 09:14:56 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed wrong include of /usr/include/*
## Comment 1368
Date: 2005-10-06 13:29:17 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
CLAIMED BY vzzzbx
NO TEST / COMPILATION
## Comment 1369
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 977753 at http://sourceforge.net/support/tracker.php?aid=977753
| Compilation error when using --prefix=something/else | https://api.github.com/repos/MonetDB/MonetDB/issues/256/comments | 0 | 2020-11-30T08:25:33Z | 2024-06-27T10:57:21Z | https://github.com/MonetDB/MonetDB/issues/256 | 753,266,632 | 256 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-21 09:40:31 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-06-24 02:40:16 +0200
## Comment 1360
Date: 2004-06-21 21:40:31 +0200
From: @arjan
Don't know if this will make it in the .18 release, but
still:
Updates of this type give incorrect results.
create table test (id varchar(1), x int);
insert into test values ('a', 1);
insert into test values ('b', 2);
select * from test order by id;
-- Expected result:
-- [ "a", 1 ]
-- [ "b", 2 ]
update test set x=x+1 where x >= 2;
select * from test order by id;
-- Expected result:
-- [ "a", 1 ]
-- [ "b", 3 ]
-- However, the following is returned:
-- [ "a", 3 ]
-- [ "b", 2 ]
## Comment 1361
Date: 2004-06-24 14:40:16 +0200
From: @njnes
Logged In: YES
user_id=43556
missed one important join!!
## Comment 1362
Date: 2005-10-06 13:27:39 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06: Done.
CLAIMED BY vzzzbx
ALREADY IN TESTWEB
## Comment 1363
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 976963 at http://sourceforge.net/support/tracker.php?aid=976963
| SQL: x=x+1 updates | https://api.github.com/repos/MonetDB/MonetDB/issues/255/comments | 0 | 2020-11-30T08:25:30Z | 2024-06-27T10:57:20Z | https://github.com/MonetDB/MonetDB/issues/255 | 753,266,607 | 255 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-19 05:03:18 +0200
From: @mlkersten
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2004-09-06 06:21:10 +0200
## Comment 1355
Date: 2004-06-19 17:03:18 +0200
From: @mlkersten
When your create a BATview(b,TRUE) and not delete it
explicitly yourselve, but instead perform a session
exit, then the system ends with an assertion failure on
freeing memory twice.
Sample valgrind output:
=23114== Invalid read of size 4
==23114== at 0x404B65DC: GDKfree (gdk_utils.mx:950)
==23114== by 0x40466E3A: HEAPfree (gdk_heap.mx:232)
==23114== by 0x404E0790: BATfree (gdk_bat.mx:477)
==23114== by 0x4045EBBB: BBPexit (gdk_bbp.mx:610)
==23114== Address 0x48AF1634 is 4 bytes inside a
block of size 432 free'd
==23114== at 0x40029961: free (vg_replace_malloc.c:231)
==23114== by 0x404B6602: GDKfree (gdk_utils.mx:966)
==23114== by 0x40466E3A: HEAPfree (gdk_heap.mx:232)
==23114== by 0x404E0790: BATfree (gdk_bat.mx:477)
Mserver: /ufs/mk/monet5/src/gdk/gdk_utils.mx:953:
GDKfree: Assertion `(size&2) == 0' failed.
Aborted
## Comment 1356
Date: 2004-09-06 18:30:15 +0200
From: @peterboncz
Logged In: YES
user_id=591107
From its description, I understand that this behavior can only
be triggered from C code not MIL code. That would mean a
buggy module. Notice that it is a quite ambitious goal to
protect a kernel against buggy extension modules, and in
MonetDB we have always stayed away from that assumption.
That said, I tried but I could not produce a crash.
By the way, BATview() is a nonexistent function call (tried to
grep), and I assumed while treating this bug report that
VIEWcreate() was meant instead.
what I tried:
gdb Mserver
> b := bat(void,int).insert(nil,1).access(BAT_READ);
CTRL-C
b CMDmax_int;
c
> b.max;
p VIEWcreate(b)
c
> CTRL-D
which exits correctly.
so either this bug was based on old (Monet-5) code, or I
have simply not been able to reproduce the basic
circumstances that require it to trigger - in that case a better
reproduction description is called for.
## Comment 1357
Date: 2004-09-06 19:01:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just for info...
I recall that these (or similar) errors did occur when I
tried to debug Jan's "!WARNING: CTcheck_hl: histogram
disappeared!" bugs (978814 & 981954); hence, it might be
that they have disappeared since the code (view/accellerator
handling) has been fixed; haven't tried it, but anybody
welcome to try it him/herself; the respective test are *of
course* in CVS ...
The Diplomat
## Comment 1358
Date: 2005-10-06 13:25:31 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
BugDay_2005-10-06
REASSIGN stefan
note: the comments suggest that the bug is covered by the
test-scripts created for 978814 and 981954
## Comment 1359
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 975880 at http://sourceforge.net/support/tracker.php?aid=975880
| BATview garbage collection | https://api.github.com/repos/MonetDB/MonetDB/issues/254/comments | 0 | 2020-11-30T08:25:27Z | 2024-06-28T13:37:02Z | https://github.com/MonetDB/MonetDB/issues/254 | 753,266,569 | 254 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-18 03:43:49 +0200
From: @swingbit
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-06-22 06:00:01 +0200
## Comment 1350
Date: 2004-06-18 15:43:49 +0200
From: @swingbit
monet>help("sort");
help("sort");
COMMAND: sort(BAT[any::1,any::2]) : BAT[any::1,any::2]
MODULE: algebra
COMPILED: by adm on Thu Jun 17 14:51:57 2004
Returns a sorted copy of a BAT.
Does it sort on the head or on the tail ?
## Comment 1351
Date: 2004-06-22 18:00:01 +0200
From: @drstmane
Logged In: YES
user_id=572415
sort, sort_rev, order, order_rev work on head.
fixed the help messages.
## Comment 1352
Date: 2005-10-06 13:05:03 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
CLAIMED BY vzzzbx
NO TEST / DOCUMENTATION
## Comment 1353
Date: 2005-12-21 11:35:41 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay: vzzzbx: NO TEST / DOCUMENTATION
## Comment 1354
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 975362 at http://sourceforge.net/support/tracker.php?aid=975362
| ambiguous help for sort | https://api.github.com/repos/MonetDB/MonetDB/issues/253/comments | 0 | 2020-11-30T08:25:24Z | 2024-06-27T10:57:17Z | https://github.com/MonetDB/MonetDB/issues/253 | 753,266,540 | 253 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-18 02:25:06 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-06-20 04:17:29 +0200
## Comment 1345
Date: 2004-06-18 14:25:06 +0200
From: @arjan
The following crashes the server:
CREATE TABLE test (
y INTEGER,
x INTEGER,
PRIMARY KEY(x, y)
);
UPDATE test SET y = 1;
## Comment 1346
Date: 2004-06-20 16:17:29 +0200
From: @njnes
Logged In: YES
user_id=43556
partial key updates weren't handled correctly
## Comment 1347
Date: 2005-10-06 13:00:35 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
CLAIMED BY vzzzbx
ALREADY IN TESTWEB
## Comment 1348
Date: 2005-12-21 11:36:36 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay: vzzzbx: ALREADY IN TESTWEB:
./src/test/bugs/Tests/primary_key-bug-sf-975308.sql.src
## Comment 1349
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 975308 at http://sourceforge.net/support/tracker.php?aid=975308
| SQL: Update on multicol-primary key | https://api.github.com/repos/MonetDB/MonetDB/issues/252/comments | 0 | 2020-11-30T08:25:22Z | 2024-06-27T10:57:17Z | https://github.com/MonetDB/MonetDB/issues/252 | 753,266,517 | 252 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-14 11:33:07 +0200
From: @arjan
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-12-21 10:18:17 +0100
## Comment 1336
Date: 2004-06-14 23:33:07 +0200
From: @arjan
CREATE TABLE test (x VARCHAR(10));
INSERT INTO test VALUES ('a');
INSERT INTO test VALUES ('b');
SELECT * FROM test WHERE x = 'a';
SELECT * FROM test WHERE x = 'a' AND x = 'b';
second query crashes server with:
Mserver: sql_rel2bin.mx:343: stmt_max: Assertion `f'
failed.
Aborted
## Comment 1337
Date: 2004-06-20 16:26:41 +0200
From: @njnes
Logged In: YES
user_id=43556
shrink_select_ranges tries to find a max function for data
of type string.
A string max function doesn't exist leading to the assertion.
Propably needed to call shrink_select_ranges only for types
which
have a max (ie numerical, temporal...)
## Comment 1338
Date: 2004-06-21 10:28:36 +0200
From: @arjan
Logged In: YES
user_id=20087
why does max(string) does not exist? In SQL it does:
sql>select max(name) from tables;
max_name name
varchar type
1 tuplecount
0 id
[ "users" ]
## Comment 1339
Date: 2004-06-21 11:03:39 +0200
From: @njnes
Logged In: YES
user_id=43556
select max(bla); is an aggregate, the max(a,b) however is
missing
## Comment 1340
Date: 2004-06-21 19:15:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed:
do not try to "shrink_select_ranges" in case there is no
binary "max"/"min" available for the respective data type.
However, I see no reason for not having "max(a,b)" and
"min(a,b)" on strings also in SQL; "<"/">" are available on
strings even in SQL, and "max(str,str)" & "min(str,str)" are
available in MIL ...
## Comment 1341
Date: 2005-10-06 12:57:57 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
CLAIMED BY vzzzbx
ALREADY IN TESTWEB
## Comment 1342
Date: 2005-12-21 11:48:05 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay: stmane: TEST ADDED / FAILURE:
test scipt existed in
sql/src/test/bugs/Tests/bug-sf-972833.sql
but was not activated, yet;
re-opened as stable output is still missing.
## Comment 1343
Date: 2005-12-21 22:18:17 +0100
From: @njnes
Logged In: YES
user_id=43556
added stable output
## Comment 1344
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 972833 at http://sourceforge.net/support/tracker.php?aid=972833
| SQL: AND conditions crash | https://api.github.com/repos/MonetDB/MonetDB/issues/251/comments | 0 | 2020-11-30T08:25:19Z | 2024-06-27T10:57:16Z | https://github.com/MonetDB/MonetDB/issues/251 | 753,266,485 | 251 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-11 04:27:24 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2004-06-22 05:18:36 +0200
## Comment 1332
Date: 2004-06-11 16:27:24 +0200
From: Jan Rittinger <<jan.rittinger>>
mil>a := bat (oid,oid);
mil>b := a.mark(0@0);
mil>b.print;
-----------------
h tmp_60 name
oid void type
-----------------
mil>b := b.reverse.mark(0@0).reverse;
mil>b.print;
-----------------
t tmp_59 name
oid void type
-----------------
mil>b.seqbase(0@0);
MAPI = anonymous@localhost:50000
ACTION= mapi_get_row
QUERY = b.seqbase(0@0);
ERROR = !ERROR: interpret: no matching MIL operator to
'seqbase(BAT[oid,void],
oid)'.
!MAYBE YOU MEAN:
! seqbase(BAT[void,any::1], oid) : BAT[void,any::1]
! seqbase(BAT[void,any::1]) : oid
! seqbase(BAT[oid,any::1]) : oid
## Comment 1333
Date: 2004-06-22 17:18:36 +0200
From: @drstmane
Logged In: YES
user_id=572415
this is actually not a bug but a feature:
- since a is writeable, b:=a.mark(0@0); is not a view on a,
but a materialized BAT with a non-materialized "real-" void
tail.
- since b is (hence) also writeable, "b :=
b.reverse.mark(0@0).reverse;" is again not a view, but a
materialized BAT, however, since [void,void] BATs can only
exist as views, the mark must materialze its tail (which
then becomes b's head) as oid.
- obviously, there is no seqbase(oid) on [oid,any] BATs
## Comment 1334
Date: 2005-11-09 09:28:28 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: NO TEST / Bug is invalid
Invalid bug report ie no bug not possible to test
## Comment 1335
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 971158 at http://sourceforge.net/support/tracker.php?aid=971158
| bat header wrong (seqbase gives an error) | https://api.github.com/repos/MonetDB/MonetDB/issues/250/comments | 0 | 2020-11-30T08:20:29Z | 2024-06-28T13:37:01Z | https://github.com/MonetDB/MonetDB/issues/250 | 753,263,183 | 250 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-11 01:30:12 +0200
From: @joerivanruth
To: @mlkersten
Version: -- development
Last updated: 2004-09-12 01:35:54 +0200
## Comment 1324
Date: 2004-06-11 13:30:12 +0200
From: @joerivanruth
Lex and Yacc reserve the yy* and YY* namespace, yet Monet
uses it for its own purposes in yytree.mx.
On my system, both lex and and yytree.mx define a
function yyfree(), resulting in a conflict.
As a quick and dirty fix, I attach a patch to rules.mk that
replaces every instance of yyfree by yy_free in *.yy.c
files.
A better way to fix it would be to leave the yy* names
to lex and
pick another prefix for Monet parse trees.
System information:
Debian sarge (testing) on x86.
; uname -a
Linux zout 2.4.22joeri3 1 Mon Dec 8 14:00:35 CET 2003
i686 GNU/Linux
; gcc --version
gcc (GCC) 3.3.3 (Debian 20040422)
; flex --version
flex 2.5.31
; bison --version
bison (GNU Bison) 1.875a
; autoconf --version
autoconf (GNU Autoconf) 2.59
; automake --version
automake (GNU automake) 1.7.9
; libtool --version
ltmain.sh (GNU libtool) 1.5.6 (1.1220.2.95 2004/04/11
05:50:42) Debian: 203 $
; make --version
GNU Make 3.80
## Comment 1325
Date: 2004-06-22 17:01:56 +0200
From: @drstmane
Logged In: YES
user_id=572415
Joeri,
that's a bit of a strange problem, which I cannot recreate
on any of our test systems.
Well, in a way, you're right, we shoudl actually use a
different prefix than the default "yy" in the parser, but
I'm afraid, we won't manage to do this in 4.3.18. We'll keep
it on the list for 4.4 ...
Appart from that, could you please send us (or attach to
this bug report) the complete output of your "bootstrap",
"configure", and "make" with the non-patched version, thus
that we could analyze the problem ourselves?
Thank you very much in advance, and sorry for the
inconvenience...
Stefan
## Comment 1326
Date: 2004-06-23 11:16:51 +0200
From: @joerivanruth
Logged In: YES
user_id=901389
Stefan,
I attached a bunch of files.
The output of the commands you asked for, the generated
lex.yy.c (now named monet_parse.yy.c) and the notes I kept
when compiling Monet.
I hope they are of any use.
Joeri
## Comment 1327
Date: 2004-06-23 12:45:06 +0200
From: @drstmane
Logged In: YES
user_id=572415
Apparently, flex 2.5.31 seems to work significatly different
that flex <= 2.5.4 (on our testing machines, we only have
flex 2.5.2 through 2.5.4): among others, it adds definitions
of functions yyalloc, yyrealloc, yyfree, with the latter
giving the reported problems.
(compare the attached "monet_parse.yy.c" and
"monet_parse.yy.c_flex-2.5.4" for details)
I'm afraid, we'll have to look deeper into this problems;
hence, do not expect a solution in 4.3.18, but only in 4.4.
(Using another prefix than the default "yy" should solve the
problem, I hope...)
## Comment 1328
Date: 2004-09-12 13:35:54 +0200
From: @mlkersten
Logged In: YES
user_id=490798
The external visible commands yy* in yytree.mx have been
replaced by Myy*
## Comment 1329
Date: 2004-09-12 13:42:05 +0200
From: @drstmane
Logged In: YES
user_id=572415
Joeri,
once you have time, could you please check, whether Martins
changes do indeed solve your problem --- we don't have any
flex-2.5.31 available ...
Thanks in advance,
Stefan
## Comment 1330
Date: 2005-11-09 09:26:14 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: NO TEST / COMPILATION
## Comment 1331
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 971059 at http://sourceforge.net/support/tracker.php?aid=971059
| yytree.mx name conflict with flex | https://api.github.com/repos/MonetDB/MonetDB/issues/249/comments | 0 | 2020-11-30T08:20:26Z | 2024-06-27T10:57:14Z | https://github.com/MonetDB/MonetDB/issues/249 | 753,263,154 | 249 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-11 10:07:48 +0200
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2004-06-20 06:20:13 +0200
## Comment 1317
Date: 2004-06-11 10:07:48 +0200
From: @mlkersten
Rolling forward to the release candidate 2.0.18-rc
with existing SQL database fails. The SQL server should
detect the version and automatically roll forward the
necessary changes in the catalog structures.
Alternatively, a script should be supplied to roll your
database forward with minimal effort.
## Comment 1318
Date: 2004-06-11 22:48:53 +0200
From: @njnes
Logged In: YES
user_id=43556
dump/restore ?
## Comment 1319
Date: 2004-06-11 23:06:20 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Sure, that's an option. But now you bring out a new version
of SQL that crashes. It should be better if the sql module
could at least detect the invalid dictionary and advice the
user accordingly. Furthermore, this situation should be
clearly indicated in a distribution message.
We have to think about a better scheme to roll forward the
DB. (Aside, gdk from the beginning was able to detect a
version change)
## Comment 1320
Date: 2004-06-11 23:06:34 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Sure, that's an option. But now you bring out a new version
of SQL that crashes. It should be better if the sql module
could at least detect the invalid dictionary and advice the
user accordingly. Furthermore, this situation should be
clearly indicated in a distribution message.
We have to think about a better scheme to roll forward the
DB. (Aside, gdk from the beginning was able to detect a
version change)
## Comment 1321
Date: 2004-06-20 18:20:13 +0200
From: @njnes
Logged In: YES
user_id=43556
the logs now store a CATALOG_VERSION nr. Loading sql_server
will fail if the versions (running server vs stored) do not
match.
## Comment 1322
Date: 2005-11-09 09:24:21 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: NO TEST
Testing repository changes is complicated as new versions
cannot create old repos. So its currently impossible to
check. Someday we should do testing agains repositories
created by the stable. This is (should) be done before an
release (not everynight)
## Comment 1323
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 970958 at http://sourceforge.net/support/tracker.php?aid=970958
| SQL: incompatible sql admin crashes server | https://api.github.com/repos/MonetDB/MonetDB/issues/248/comments | 0 | 2020-11-30T08:20:22Z | 2024-06-27T10:57:13Z | https://github.com/MonetDB/MonetDB/issues/248 | 753,263,101 | 248 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-09 09:37:07 +0200
From: @MarcinZukowski
To: @sjoerdmullender
Version: -- development
Last updated: 2004-06-21 04:25:34 +0200
## Comment 1311
Date: 2004-06-09 21:37:07 +0200
From: @MarcinZukowski
In Mserver it is allowed to do sth like:
b:=str("\nline1\n\
line2\n");
printf("%s",b);
Attached script makes MapiClient hang.
It works without any problems in Mserver.
AFAIR it also didn't work with Mknife, hence it can be some inherent
protocol problem.
It's a bit of a problem for me, since I send x100 queries to Mserver
through Mapi protocol. I used to remove all x100 comments and
EOLs in x100->MIL compiler, but it makes debugging a bit harder (I
lose x100 line number).
## Comment 1312
Date: 2004-06-09 21:45:36 +0200
From: @grobian
Logged In: YES
user_id=963970
Dunno if it's relevant, but using SQL, it seems to work:
monetdb-> select '\nline1\nline2\n';
+----------
| single_value
+----------
|
line1
line2
+----------
1 rows
monetdb-> \q
(pictor:~/develop/monetjdbc) fabian% MapiClient -lsql
sql>select '\nline1\nline2\n';
single_value name
character type
1 tuplecount
0 id
[ "\nline1\nline2\n" ]
sql>
## Comment 1313
Date: 2004-06-09 21:50:42 +0200
From: @grobian
Logged In: YES
user_id=963970
Sorry. See your \ at the end is absent in the mail from SF.
So my comment was not relevant.
If the \ is sent over by the server on the protocol,
MapiClient will have a problem I think since it will do
something like
[ "\nline1\" ]
[ "line2\n" ]
which of course means that a quote does not get terminated.
Just theory here.
## Comment 1314
Date: 2004-06-21 16:25:34 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
There was a slight problem in readClient which is now fixed.
## Comment 1315
Date: 2005-11-09 09:18:51 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: TEST ADDED / SUCCESS
tests/BugDay_2005-11-09_2.9.3/Tests/mapi_hangs_on_eol.SF-969839.sql
## Comment 1316
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 969839 at http://sourceforge.net/support/tracker.php?aid=969839
| Mapi doesn't like EOLs | https://api.github.com/repos/MonetDB/MonetDB/issues/247/comments | 0 | 2020-11-30T08:20:19Z | 2024-06-27T10:57:12Z | https://github.com/MonetDB/MonetDB/issues/247 | 753,263,076 | 247 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-09 01:07:09 +0200
From: @arjan
To: @sjoerdmullender
Version: -- development
Last updated: 2004-08-17 03:50:40 +0200
## Comment 1305
Date: 2004-06-09 13:07:09 +0200
From: @arjan
There is an inconsistency between the mil and sql
version of mapi_get_row_count. When called in MIL mode
after a query, it always returns 1 instead of the
actual row count (doing a mapi_fetch_all_rows before
mapi_get_row_count fixes this).
In SQL mode, get_row_count returns the right number of
rows directly, without needing to call
mapi_fetch_all_rows first. This is inconsistent with
its behaviour in MIL mode. Which one is correct?
The following program demonstrates this:
include "Mapi.h"
int main() {
Mapi mid;
MapiHdl hdl;
mid = mapi_connect("localhost", 50000, "monetdb",
"monetdb", "mil");
hdl = mapi_query(mid, "ls;");
printf("Num rows: %d\n", mapi_get_row_count(hdl));
mapi_destroy(mid);
mid = mapi_connect("localhost", 45123, "monetdb",
"monetdb", "sql");
hdl = mapi_query(mid, "SELECT name FROM tables;");
printf("Num rows: %d\n", mapi_get_row_count(hdl));
mapi_destroy(mid);
return 0;
}
This outputs:
Num rows: 1
Num rows: 15
## Comment 1306
Date: 2004-06-13 22:16:45 +0200
From: @arjan
Logged In: YES
user_id=20087
A related problem is that the Mapi interface does not like
multiple query handles lying around which have not all rows
fetched yet through the connection. It displays incorrect
behaviour in this case. More details will follow.
## Comment 1307
Date: 2004-06-21 16:33:01 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
The problem is that the number of rows is not available in
MIL unless all rows have been read. In SQL the number of
rows *is* known when the header of the table is printed.
In MIL, the table is generated by BATmultijoin in
BATmultiprintf and it is not necessarily known how many rows
this will generate when the table header is printed.
The cop-out is that mapi_get_row_count returns what it knows
when it is called, i.e. everything in SQL, but only what has
been read so far in MIL.
## Comment 1308
Date: 2004-08-17 15:50:40 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Closing this as "Won't fix". Unless somebody comes up with
a workable solution to the problem that the row count is not
known in MIL until the whole table was printed without
having to do the join that produces the output table twice,
there will remain a discrepancy between MIL and SQL.
Arjan, the comment about a related problem will be ignored
unless you open a bug report in which it is described.
## Comment 1309
Date: 2005-11-09 09:09:35 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: NO TEST / BUG 'won't fix'
As the bug is considered to much work to fix (and therefor
isn't fixed) we cannot test it as it will allways fail.
## Comment 1310
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 969522 at http://sourceforge.net/support/tracker.php?aid=969522
| Inconsistent mapi_get_row_count | https://api.github.com/repos/MonetDB/MonetDB/issues/246/comments | 0 | 2020-11-30T08:20:15Z | 2024-06-28T13:37:01Z | https://github.com/MonetDB/MonetDB/issues/246 | 753,263,042 | 246 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-05 05:58:27 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-06-11 10:49:38 +0200
## Comment 1301
Date: 2004-06-05 17:58:27 +0200
From: @grobian
for instance the now() function:
monetdb-> select now();
Error on line 3: ERROR syntax error at token (40) in
statement: select now(
Executed query: select now();
monetdb-> select now;
+----------
| current_timestamp
+----------
| 2004-06-05 17:54:01.000
+----------
1 rows
monetdb->
Without the () it works, but this seems wrong to me,
since it is a function, not a constant, column, or
environment variable.
Other functions are for instance current_date() and
current_time().
## Comment 1302
Date: 2004-06-05 18:08:13 +0200
From: @grobian
Logged In: YES
user_id=963970
According to JDBC USER() is a function as well. It now only
works as select user;
## Comment 1303
Date: 2005-11-09 09:05:43 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: TEST ADDED / SUCCESS
src/test/BugDay_2005-11-09_2.9.3/Tests/date_functions.SF-967145.sql
## Comment 1304
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 967145 at http://sourceforge.net/support/tracker.php?aid=967145
| SQL: argumentless functions not callable with () | https://api.github.com/repos/MonetDB/MonetDB/issues/245/comments | 0 | 2020-11-30T08:20:12Z | 2024-06-27T10:57:10Z | https://github.com/MonetDB/MonetDB/issues/245 | 753,263,002 | 245 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-05 03:35:16 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-06-11 10:50:03 +0200
## Comment 1298
Date: 2004-06-05 15:35:16 +0200
From: @grobian
The functions
for(t=floats; t < dates; t++){
sql_create_func( "floor", "floor", *t, NULL, *t,
SCALE_FIX );
sql_create_func( "ceil", "ceil", *t, NULL, *t,
SCALE_FIX );
sql_create_func( "ceil", "ceiling", *t, NULL, *t,
SCALE_FIX ); /* JDBC */
sql_create_func( "sin", "sin", *t, NULL, *t, SCALE_FIX );
sql_create_func( "cos", "cos", *t, NULL, *t, SCALE_FIX );
sql_create_func( "tan", "tan", *t, NULL, *t, SCALE_FIX );
sql_create_func( "asin", "asin", *t, NULL, *t,
SCALE_FIX );
sql_create_func( "acos", "acos", *t, NULL, *t,
SCALE_FIX );
sql_create_func( "atan", "atan", *t, NULL, *t,
SCALE_FIX );
sql_create_func( "sinh", "sinh", *t, NULL, *t,
SCALE_FIX );
sql_create_func( "cosh", "cosh", *t, NULL, *t,
SCALE_FIX );
sql_create_func( "tanh", "tanh", *t, NULL, *t,
SCALE_FIX );
sql_create_func( "sqrt", "sqrt", *t, NULL, *t,
SCALE_FIX );
sql_create_func( "exp", "exp", *t, NULL, *t, SCALE_FIX );
sql_create_func( "log", "log", *t, NULL, *t, SCALE_FIX );
sql_create_func( "log10", "log10", *t, NULL, *t,
SCALE_FIX );
}
can only be used on float datatypes.
A simple select floor(3.5) fails, and has to be written
like
select floor(cast(3.5 as float)) in order to work. This
looks odd, since one would expect that 3.5 is by
default of float type.
## Comment 1299
Date: 2005-11-09 08:57:26 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
src/test/bugs/floor-bug-sf-967066.sql
## Comment 1300
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 967066 at http://sourceforge.net/support/tracker.php?aid=967066
| SQL: some functions require explicit cast | https://api.github.com/repos/MonetDB/MonetDB/issues/244/comments | 0 | 2020-11-30T08:20:09Z | 2024-06-27T10:57:09Z | https://github.com/MonetDB/MonetDB/issues/244 | 753,262,972 | 244 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-04 04:50:38 +0200
From: Jan Rittinger <<jan.rittinger>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2010-05-04 10:55:21 +0200
## Comment 1295
Date: 2004-06-04 16:50:38 +0200
From: Jan Rittinger <<jan.rittinger>>
mil>a := bat(void, oid).seqbase(0@0);
mil>a.insert(0@0,1@0);
mil>a.print;
-----------------
h tmp_59 name
void oid type
-----------------
[ 0@0, 1@0 ]
mil>b := bat(void, oid).seqbase(0@0);
mil>b.insert(0@0,0@0);
mil>b := b.select(0@0);
mil>b := b.mark(0@0).reverse;
mil>b.print;
-----------------
t tmp_62 name
void void type
-----------------
[ 0@0, 0@0 ]
mil>c := b.join(a);
mil>c.print;
-----------------
t tmp_69 name
void void type
-----------------
[ 0@0, 1@0 ]
expected:
-----------------
h tmp_69 name
void oid type
-----------------
[ 0@0, 1@0 ]
## Comment 1296
Date: 2005-11-09 08:55:46 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: NO TEST / NOT A BUG
No bug, no test to check for incorrect output
## Comment 1297
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 966581 at http://sourceforge.net/support/tracker.php?aid=966581
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
| change of types without casting (void instead of oid) | https://api.github.com/repos/MonetDB/MonetDB/issues/243/comments | 0 | 2020-11-30T08:20:06Z | 2024-06-28T13:37:00Z | https://github.com/MonetDB/MonetDB/issues/243 | 753,262,940 | 243 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-06-01 12:15:55 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-06-06 09:39:58 +0200
## Comment 1290
Date: 2004-06-01 12:15:55 +0200
From: @arjan
CAST on columns does not work.
create table t2 (x varchar(10));
insert into t2 values ('1');
insert into t2 values ('2');
select cast(x as integer) from t2;
convert_x name
mediumint type
2 tuplecount
1 id
[ "1" ]
[ "2" ]
e.g. the values remain varchars instead of becoming
ints. For a single row it works as expected:
sql>select cast('1' as integer);
convert_single_value name
mediumint type
1 tuplecount
3 id
[ 1 ]
## Comment 1291
Date: 2004-06-01 12:30:32 +0200
From: @arjan
Logged In: YES
user_id=20087
'Works-for-me' fix:
Index: sql_gencode.mx
===================================================================
RCS file:
/cvsroot/monetdb/sql/src/backends/monet4/sql_gencode.mx,v
retrieving revision 1.28
diff -u -r1.28 sql_gencode.mx
--- sql_gencode.mx 11 May 2004 13:32:37 -0000 1.28
+++ sql_gencode.mx 1 Jun 2004 10:29:03 -0000
@@ -685,7 +685,6 @@
strcmp(s->op4.funcval->func->name,
"convert") == 0 ) {
buflen = BUFSIZ;
buf = NEW_ARRAY(char, buflen+1);
- len = snprintf( buf, buflen, "var s%d :=
s%d;\n", -s->nr, l);+ len = snprintf( buf,
buflen, "var s%d := [%s](s%d);\n", -s->nr,
s->op4.funcval->func->imp, l);
assert(len <= buflen);
} else {
buflen =
strlen(s->op4.funcval->func->imp) + 64;
## Comment 1292
Date: 2004-06-06 21:39:58 +0200
From: @njnes
Logged In: YES
user_id=43556
Seems to work for me. See new test bug-sf-964165
## Comment 1293
Date: 2005-11-09 08:49:23 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
src/test/bugs/cast_varchar2int-bug-sf-964165.sql
## Comment 1294
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 964165 at http://sourceforge.net/support/tracker.php?aid=964165
| SQL: CAST on columns | https://api.github.com/repos/MonetDB/MonetDB/issues/242/comments | 0 | 2020-11-30T08:20:02Z | 2024-06-28T13:37:00Z | https://github.com/MonetDB/MonetDB/issues/242 | 753,262,902 | 242 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-31 09:13:04 +0200
From: @MarcinZukowski
To: @mlkersten
Version: -- development
Last updated: 2004-05-31 09:40:42 +0200
## Comment 1286
Date: 2004-05-31 21:13:04 +0200
From: @MarcinZukowski
Mx consumes full line after @f, meaning if somebody accidentaly
put space at the end, it is added to prefix of all created files.
Example:
Mx -c bug.mx
bug.mx attached.
## Comment 1287
Date: 2004-05-31 21:40:42 +0200
From: @mlkersten
Logged In: YES
user_id=490798
A test has been added to @f files.
the file name is trimmed at the first
isspace() character
## Comment 1288
Date: 2005-11-09 08:46:21 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: NO TEST / COMPILATION
## Comment 1289
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 963759 at http://sourceforge.net/support/tracker.php?aid=963759
| Mx @f doesn't trim string | https://api.github.com/repos/MonetDB/MonetDB/issues/241/comments | 0 | 2020-11-30T08:19:59Z | 2024-06-27T10:57:05Z | https://github.com/MonetDB/MonetDB/issues/241 | 753,262,859 | 241 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-31 04:42:56 +0200
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2004-05-31 06:36:39 +0200
## Comment 1282
Date: 2004-05-31 16:42:56 +0200
From: @mlkersten
> MapiClient -l sql
sql>create schema mine;
sql>grant all on mine to monetdb;
MAPI = monetdb@localhost:45123
ACTION= mapi_fetch_line
QUERY = grant all on mine to monetdb;
ERROR = Connection terminated
## Comment 1283
Date: 2004-05-31 18:36:39 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed (ie correctly ?) give error back of unknown table/function
## Comment 1284
Date: 2005-11-09 08:42:08 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: TEST ADDED / SUCCESS
src/test/BugDay_2005-11-09_2.9.3/Tests/schema_change_grant_crash.SF-963620.sql
## Comment 1285
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 963620 at http://sourceforge.net/support/tracker.php?aid=963620
| SQL: grant statement crashes server | https://api.github.com/repos/MonetDB/MonetDB/issues/240/comments | 0 | 2020-11-30T08:19:56Z | 2024-06-27T10:57:05Z | https://github.com/MonetDB/MonetDB/issues/240 | 753,262,824 | 240 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-28 11:37:52 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-06-11 10:50:50 +0200
## Comment 1279
Date: 2004-05-28 11:37:52 +0200
From: @arjan
sql>select 1, 2;
single_value, single_value name
decimal, decimal type
1, tuplecount
4, id
[ 1, 2 ]
The following query should give the same result as the
above query, but it does not:
sql>select * from (select 1, 2) as t;
single_value name
decimal type
1 tuplecount
3 id
[ 1 ]
This only happens in a subselect which results in a
single row.
## Comment 1280
Date: 2005-11-09 08:18:43 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
src/test/bugs/subselect_single_value-bug-sf-962099.sql
## Comment 1281
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 962099 at http://sourceforge.net/support/tracker.php?aid=962099
| SQL: invalid output of single row subselect | https://api.github.com/repos/MonetDB/MonetDB/issues/239/comments | 0 | 2020-11-30T08:19:53Z | 2024-06-27T10:57:04Z | https://github.com/MonetDB/MonetDB/issues/239 | 753,262,803 | 239 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-26 11:11:11 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-28 10:11:27 +0200
## Comment 1275
Date: 2004-05-26 11:11:11 +0200
From: @arjan
CREATE TABLE h (a int, b int);
INSERT INTO h VALUES (0, 10);
INSERT INTO h VALUES (10, 20);
INSERT INTO h VALUES (20, 30);
CREATE TABLE d (x int);
INSERT INTO d VALUES (5);
INSERT INTO d VALUES (6);
INSERT INTO d VALUES (11);
-- This one works:
SELECT h.a, h.b, COUNT(*)
FROM h
INNER JOIN d
ON (h.a <= d.x AND d.x < h.b)
GROUP BY h.a, h.b
ORDER BY a, b
;
-- But this one crashes the server:
SELECT h.a, h.b, COUNT(*)
FROM h
INNER JOIN d
ON (d.x BETWEEN h.a AND h.b)
GROUP BY h.a, h.b
ORDER BY a, b
;
## Comment 1276
Date: 2004-05-28 10:11:27 +0200
From: @njnes
Logged In: YES
user_id=43556
between assumed right hand were atoms, now also columns are
possible.
## Comment 1277
Date: 2005-11-09 08:17:34 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
src/test/bugs/innerjoin_between-bug-sf-960672.sql
## Comment 1278
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 960672 at http://sourceforge.net/support/tracker.php?aid=960672
| SQL: BETWEEN in join condition crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/238/comments | 0 | 2020-11-30T08:19:50Z | 2024-06-27T10:57:03Z | https://github.com/MonetDB/MonetDB/issues/238 | 753,262,766 | 238 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-25 04:27:07 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-28 09:21:52 +0200
## Comment 1271
Date: 2004-05-25 16:27:07 +0200
From: @arjan
Following query crashes the server:
sql>select current_date = '2004-05-25';
Ofcourse, this query is not correct, but it should not
crash anyway. The following correct query does behave
nicely:
sql>select current_date = date '2004-05-25';
=_current_date name
boolean type
1 tuplecount
3 id
[ true ]
## Comment 1272
Date: 2004-05-28 09:21:52 +0200
From: @njnes
Logged In: YES
user_id=43556
stmt was destroyed twice!
## Comment 1273
Date: 2005-11-09 08:16:21 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
src/test/bugs/date_parsing-bug-sf-960166.sql
## Comment 1274
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 960166 at http://sourceforge.net/support/tracker.php?aid=960166
| SQL: server crash on date typecast | https://api.github.com/repos/MonetDB/MonetDB/issues/237/comments | 0 | 2020-11-30T08:19:47Z | 2024-06-27T10:57:02Z | https://github.com/MonetDB/MonetDB/issues/237 | 753,262,726 | 237 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-21 03:09:02 +0200
From: Jens Teubner <<teubner>>
To: @sjoerdmullender
Version: -- development
Last updated: 2004-06-21 04:35:12 +0200
## Comment 1262
Date: 2004-05-21 15:09:02 +0200
From: Jens Teubner <<teubner>>
The current pathfinder CVS snapshot does not compile with MonetDB 4.3.
16 (tarball from sf.net).
$ ./configure --enable-assert --enable-debug
...
$ make
...
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I. -I../include -I./../include
-I/local_tmp/teubner/monet/include/MonetDB
-I/local_tmp/teubner/monet/include/MonetDB/common
-I/local_tmp/teubner/monet/include/MonetDB/gdk
-I/local_tmp/teubner/monet/include/MonetDB/monet
-I/local_tmp/teubner/monet/include/MonetDB/plain
-I/local_tmp/teubner/monet/include/MonetDB/contrib
-I/local_tmp/teubner/monet/include/MonetDB/mapi -ansi -std=c99
-D_POSIX_SOURCE -D_POSIX_C_SOURCE=199506L
-D_XOPEN_SOURCE=600 -Wall -W -g -Werror-implicit-function-declaration
-Werror -Wno-format -Wno-unused-function -Wno-unused-label -c daemon.
c -fPIC -DPIC -o daemon.lo
In file included from ../include/pathfinder.h:39,
from daemon.c:34:
../../pf_config.h:165:1: "HOST" redefined
In file included from ../../pf_config.h:4,
from ../include/pathfinder.h:39,
from daemon.c:34:
/local_tmp/teubner/monet/include/MonetDB/monetdb_config.h:416:1: this
is the location of the previous definition
The very first line of pf_config.h includes monetdb_config.h, which contains
the HOST macro. Several lines down, pf_config.h defines HOST again,
resulting in the above error. Uncommenting the include for
monetdb_config.h in pf_config.h solves the problem.
## Comment 1263
Date: 2004-05-21 18:22:27 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jens,
I just tried it, and it did work on my machine; but that's
the same machine the tarball was built on.
Usually, compilers do not complain about re-defined marcos,
if both definitions are identical. Hence, in your case, HOST
must be defined differently in monetdb_config.h and pf_config.h.
A closer look revealed the following:
- monetdb_config.h is in the tarball.
- monetdb_config.h does NOT get re-created during
./configure with the tarball version
- removing monetdb_config.h before calling ./configure does
force the re-creation of monetdb_config.h during ./configure
After that, the proper HOST definition for your build host
should be in monetdb_config.h and be identical to the one in
pf_config.h.
Hence, this should solve your problem, even without removing
the include for monetdb_config.h from pf_config.h.
Could you please check this, and let me know, whether it
indeed works also for you? Then, I can close this bug report
Stefan
PS:
Niels, Sjoerd,
we should gather this information "somewhere", just like the
fact, that with the current tarball, configure & make must
be called in the source dir...
## Comment 1264
Date: 2004-05-24 09:38:00 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Stefan,
tried it, without success.
Here's what I did: (I think you should be able to reproduce the problem on
titan03)
$ cd /local_tmp/teubner
$ tar xzf MonetDB-4.3.16.tar.gz
$ cd MonetDB-4.3.16
$ rm monetdb_config.h
$ ./configure --enable-optimize --prefix=/local_tmp/teubner/monet
$ grep 'define HOST' monetdb_config.h
define HOST "i686-pc-linux-gnu"
$ make
$ make install
$ cd /local_tmp/teubner
$ cvs checkout pathfinder
$ cd pathfinder
$ ./bootstrap
$ ./configure --enable-assert --enable-debug --with-gc=/net/lin_local/libgc-devel
$ grep 'define HOST' pf_config.h
define HOST "i686-suse-linux"
$ make
...
(fails again with the same problem)
I'm surprised that HOST has been set to two different values in
MonetDB/pathfinder. I have also re-bootstrapped MonetDB, with no effect on the
problem.
## Comment 1265
Date: 2004-05-24 09:52:07 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jens,
sorry for the inconvenience.
I have to admit, I don't know why/what's going wrong, here.
I'm at least as surprised as you, that HOST is defined
differently in both cases.
I'll have another look at it later...
Stefan
## Comment 1266
Date: 2004-06-03 15:58:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
Jens,
[sorry for the delay ...]
I could indeed reproduce the problem on titan03.
The actual cause seems to be, that the configure script that
is in the MonetDB source distribution (tar file) was created
using a differen version of autoconf, than the one that is
now used (locally on titan03) when running ./bootstrap for
pathfinder. With different versions of autoconf, the
conf/config.* scripts --- that are created during
./bootstrap and then later used by configure --- seem to be
in-compatible, resulting in (e.g.) different values for HOST
(even on the same machine).
For now, there are two work-arounds:
1) The one you already used, i.e., locally remove the
include of monetdb_config.h from pf_config.h (or better,
from pathfinders configure.ag).
2) Use the CVS version of MonetDB_4-3-16 (check-out with
-rMonetDB_4-3-16) instead of the source distribution (tar
file); then, ./bootstrap has to be run for both MonetDB and
pathfinder on the same machine, which obviously avoids the
in-compatibility problem.
We'll have another look, how we can fix this problem
properly --- probabaly, we should abondone the inclusion of
monetdb_config.h in all other *_config.h, again ---
afterall, most setting should be in the "local" *_config.h,
anyway, since we use MonetDB's conf/monet.m4 during
./bootstrap...
Stefan
## Comment 1267
Date: 2004-06-09 16:08:14 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
By not defining HOST in pf_config.h I think I have solved
the problem.
Jens, can you try it with the original MonetDB distribution
and the current HEAD of pathfinder?
## Comment 1268
Date: 2004-06-21 16:35:12 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Closing since I think it's fixed and I haven't heard
anything to the contrary.
Please re-open when you don't agree.
## Comment 1269
Date: 2005-11-09 08:13:58 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: NO TEST / COMPILATION
## Comment 1270
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 957994 at http://sourceforge.net/support/tracker.php?aid=957994
| Pathfinder (CVS) does not compile with MonetDB 4.3.16 | https://api.github.com/repos/MonetDB/MonetDB/issues/236/comments | 0 | 2020-11-30T08:19:42Z | 2024-06-27T10:57:01Z | https://github.com/MonetDB/MonetDB/issues/236 | 753,262,670 | 236 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-19 08:46:44 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2004-05-19 09:45:00 +0200
## Comment 1258
Date: 2004-05-19 20:46:44 +0200
From: @drstmane
some of the changes made between May 12 2004 and May 16
2004 cause test src/mapi/Tests/sample3 to fail; cf.,
http://www.ins.cwi.nl/intern/TestWeb/Current/MonetDB/.mTests103/GNU_32-d_Linux2.4.20-20.9perfctrsmp/src_mapi_examples_C/sample3.out.00.html
sorry for the somewhat later and fuzzy error message,
but testing did not run well while I was abroad...
## Comment 1259
Date: 2004-05-19 21:45:00 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed. The recent changes involved a removal of a call to
mapi_fetch_row inside mapi_seek_row. We now call
mapi_fetch_row explicitly. I had done a grep, but only on
.mx files. :-)
## Comment 1260
Date: 2005-11-09 08:12:28 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
src/mapi/Tests/sample3
## Comment 1261
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 956943 at http://sourceforge.net/support/tracker.php?aid=956943
| test src/mapi/Tests/sample3 failes after recent changes | https://api.github.com/repos/MonetDB/MonetDB/issues/235/comments | 0 | 2020-11-30T08:19:38Z | 2024-06-27T10:57:00Z | https://github.com/MonetDB/MonetDB/issues/235 | 753,262,632 | 235 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-14 12:53:36 +0200
From: @swingbit
To: @sjoerdmullender
Version: -- development
Last updated: 2004-05-15 03:57:06 +0200
## Comment 1252
Date: 2004-05-14 12:53:36 +0200
From: @swingbit
src/odbc/Makefile.am:11: HAVE_SWIG does not appear in
AM_CONDITIONAL
src/odbc/Makefile.am:16: required directory
src/odbc/python does not exist
/export/scratch1/roberto/Monet/stable/src/sql/conf/missing:
Unknown `--run' option
Try
`/export/scratch1/roberto/Monet/stable/src/sql/conf/missing
--help' for more information
configure: WARNING: `missing' script is too old or missing
conflicts: 1 reduce/reduce
conflicts: 1 reduce/reduce
/export/scratch1/roberto/Monet/stable/src/sql/src/odbc/driver/SQLGetConnectAttr.c:
In function `SQLGetConnectAttr_':
/export/scratch1/roberto/Monet/stable/src/sql/src/odbc/driver/SQLGetConnectAttr.c:60:
implicit declaration of function `mapi_is_connected'
make[4]: *** [SQLGetConnectAttr.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
/export/scratch1/roberto/Monet/stable/src/sql/src/odbc/driver/SQLGetConnectAttr.c:
In function `SQLGetConnectAttr_':
/export/scratch1/roberto/Monet/stable/src/sql/src/odbc/driver/SQLGetConnectAttr.c:60:
implicit declaration of function `mapi_is_connected'
make[3]: *** [SQLGetConnectAttr.lo] Error 1
make[2]: *** [install-recursive] Error 1
make[1]: *** [install-recursive] Error 1
make: *** [install-recursive] Error 1
aquila:~/scra/Monet/stable$ cat update.sh
## Comment 1253
Date: 2004-05-14 15:29:13 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Have you updated MonetDB?
Which version (branch) of MonetDB are you using?
The current ODBC driver in SQL only works with an up-to-date
MonetDB from the HEAD (4.3.17) branch.
## Comment 1254
Date: 2004-05-14 15:38:50 +0200
From: @swingbit
Logged In: YES
user_id=883451
> The current ODBC driver in SQL only works with an up-to-date
> MonetDB from the HEAD (4.3.17) branch.
is this clearly stated anywhere?
Probably SQL should be splited in two branches as well...
It shouldn't be allowed to check out a stable version wich
includes something that doesn't compile...
## Comment 1255
Date: 2004-05-15 15:57:06 +0200
From: @mlkersten
Logged In: YES
user_id=490798
The release note clearly indicate the dependencies between
the stable packages. As for the development things are more
complicated because neither head branch is frozen. A note on
this will be added to the website.
## Comment 1256
Date: 2005-11-09 08:09:36 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: NO TEST / COMPILATION
## Comment 1257
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 953873 at http://sourceforge.net/support/tracker.php?aid=953873
| SQL compilation fails | https://api.github.com/repos/MonetDB/MonetDB/issues/234/comments | 0 | 2020-11-30T08:19:35Z | 2024-06-28T13:36:59Z | https://github.com/MonetDB/MonetDB/issues/234 | 753,262,584 | 234 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-13 10:25:50 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-05-18 12:27:57 +0200
## Comment 1248
Date: 2004-05-13 22:25:50 +0200
From: @grobian
Test_Csavepoints currently crashes the server after a
few statements.
START TRANSACTION;
SAVEPOINT MonetSP0;
CREATE TABLE table_Test_Csavepoints ( id int, PRIMARY
KEY (id) );
SAVEPOINT MonetSP1;
SELECT id FROM table_Test_Csavepoints;
INSERT INTO table_Test_Csavepoints VALUES (1);
INSERT INTO table_Test_Csavepoints VALUES (2);
INSERT INTO table_Test_Csavepoints VALUES (3);
SAVEPOINT MonetSP2;
SELECT id FROM table_Test_Csavepoints;
RELEASE SAVEPOINT MonetSP0;
-- Mserver crashes here
SELECT id FROM table_Test_Csavepoints;
ROLLBACK;
Added relevant code snippet to CVS tree
## Comment 1249
Date: 2004-05-18 00:27:57 +0200
From: @njnes
Logged In: YES
user_id=43556
bats where only created (forwarded) from one savepoint to
the next (higher) level savepoint if the higher one was the
toplevel.
This is afcouse wrong as every level needs the bats.
## Comment 1250
Date: 2005-11-09 08:07:58 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
src/test/bug/savepoint_release-bug-sf-953560.sql
## Comment 1251
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 953560 at http://sourceforge.net/support/tracker.php?aid=953560
| SQL: JDBC savepoints test crashes Mserver | https://api.github.com/repos/MonetDB/MonetDB/issues/233/comments | 0 | 2020-11-30T08:19:32Z | 2024-06-27T10:56:58Z | https://github.com/MonetDB/MonetDB/issues/233 | 753,262,553 | 233 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-13 10:13:58 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-05-14 05:45:16 +0200
## Comment 1243
Date: 2004-05-13 22:13:58 +0200
From: @grobian
sql>savepoint a1;
sql>savepoint a2;
sql>savepoint a3;
sql>release savepoint a1;
sql>rollback to savepoint a2;
MAPI = monetdb@localhost:45123
ACTION= mapi_get_row
QUERY = rollback to savepoint a2;
ERROR = !transaction rollback to savepoint (a2) failed
!ERROR: rollback savepoint a2 doesn't exists
## Comment 1244
Date: 2004-05-14 17:45:16 +0200
From: @njnes
Logged In: YES
user_id=43556
a release correctly releases the named savepoint and
all savepoints created after this one!
## Comment 1245
Date: 2004-05-15 17:38:54 +0200
From: @grobian
Logged In: YES
user_id=963970
o
then I am in need of
RELEASE SAVEPOINT a1 ONLY;
:(
## Comment 1246
Date: 2005-11-09 08:05:58 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
src/test/bug/savepoint_rollback-bug-sf-953553.sql
## Comment 1247
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 953553 at http://sourceforge.net/support/tracker.php?aid=953553
| SQL: ROLLBACK TO SAVEPOINT not possible after a RELEASE? | https://api.github.com/repos/MonetDB/MonetDB/issues/232/comments | 0 | 2020-11-30T08:19:28Z | 2024-06-28T13:36:58Z | https://github.com/MonetDB/MonetDB/issues/232 | 753,262,516 | 232 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-13 09:56:05 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-05-14 03:24:25 +0200
## Comment 1239
Date: 2004-05-13 21:56:05 +0200
From: @grobian
sql>commit;
sql>set auto_commit=true;
sql>commit;
MAPI = monetdb@localhost:45123
ACTION= mapi_fetch_line
QUERY = commit;
ERROR = Connection terminated
Mserver dies on this.
Rollback does do what I would expect:
sql>rollback;
MAPI = monetdb@localhost:45123
ACTION= mapi_get_row
QUERY = rollback;
ERROR = !transaction rollback not allowed in auto
commit mode
## Comment 1240
Date: 2004-05-14 15:24:25 +0200
From: @njnes
Logged In: YES
user_id=43556
auto_commit can only commit/rollback if a transaction was
started
## Comment 1241
Date: 2005-11-09 08:04:21 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
sql/src/test/bugs/autocommit_illegal_statements-bug-sf-953545.sql
## Comment 1242
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 953545 at http://sourceforge.net/support/tracker.php?aid=953545
| SQL: Meltdown on COMMIT in auto_commit mode | https://api.github.com/repos/MonetDB/MonetDB/issues/231/comments | 0 | 2020-11-30T08:19:25Z | 2024-06-27T10:56:56Z | https://github.com/MonetDB/MonetDB/issues/231 | 753,262,477 | 231 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-12 08:18:06 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-05-12 10:52:58 +0200
## Comment 1235
Date: 2004-05-12 20:18:06 +0200
From: @grobian
sql>create table test(num numeric(2,8));
MAPI = monetdb@localhost:45123
ACTION= mapi_get_row
QUERY = create table test(num numeric(2,8));
ERROR = !ERROR syntax error at token (44) in statement:
create table test(num numeric(2,
but....
sql>create table test(num numeric(8));
works fine...
I think numeric should behave like decimal.
## Comment 1236
Date: 2004-05-12 22:52:58 +0200
From: @njnes
Logged In: YES
user_id=43556
alias(digits,scale) as indeed missing in the parser
## Comment 1237
Date: 2005-11-09 12:27:42 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
sql/src/test/bugs/numeric-bug-sf-952758.sql
sql/src/test/bugs/Tests/numeric-bug-sf-952758.stable.out
sql/src/test/bugs/Tests/numeric-bug-sf-952758.stable.err
sql/src/test/bugs/Tests/numeric-bug-sf-952758.sql.src
## Comment 1238
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 952758 at http://sourceforge.net/support/tracker.php?aid=952758
| SQL: NUMERIC datatype not supported completely? | https://api.github.com/repos/MonetDB/MonetDB/issues/230/comments | 0 | 2020-11-30T08:19:22Z | 2024-06-27T10:56:55Z | https://github.com/MonetDB/MonetDB/issues/230 | 753,262,439 | 230 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-12 08:15:35 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-05-12 10:45:20 +0200
## Comment 1231
Date: 2004-05-12 20:15:35 +0200
From: @grobian
(compiled by removing odbc to get it compiling)
$ bin/Mserver
Monet Database Server V4.3.17
Copyright (c) 1993-2004, CWI. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit; dynamically linked.
Visit http://monetdb.cwi.nl for further information.
monet>module(sql_server);
monet>Killed
when doing in a client:
$ /nfs/poseidon/Temp/monet/program/bin/MapiClient -lsql
sql>start transaction;
MAPI = monetdb@localhost:45123
ACTION= mapi_fetch_line
QUERY = start transaction;
ERROR = Connection terminated
## Comment 1232
Date: 2004-05-12 22:45:20 +0200
From: @njnes
Logged In: YES
user_id=43556
wrong transaction initializer was called
## Comment 1233
Date: 2005-11-09 12:27:03 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
sql/src/test/bugs/Tests/start_transaction-bug-sf-952755.stable.out
sql/src/test/bugs/Tests/start_transaction-bug-sf-952755.stable.err
sql/src/test/bugs/Tests/start_transaction-bug-sf-952755.sql.src
sql/src/test/bugs/start_transaction-bug-sf-952755.sql
## Comment 1234
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 952755 at http://sourceforge.net/support/tracker.php?aid=952755
| SQL: Meltdown on START TRANSACTION | https://api.github.com/repos/MonetDB/MonetDB/issues/229/comments | 0 | 2020-11-30T08:19:18Z | 2024-06-27T10:56:54Z | https://github.com/MonetDB/MonetDB/issues/229 | 753,262,392 | 229 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-12 08:06:17 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2004-05-12 08:31:46 +0200
## Comment 1227
Date: 2004-05-12 20:06:17 +0200
From: @grobian
make[3]: Entering directory
`/nfs/poseidon/Temp/monet/build-head/sql/src/odbc/python'
swig -python -DHAVE_LONG_LONG
-I/nfs/poseidon/Temp/monet/program//include -outdir .
-o odbc.py.c
../../../../../src-head/sql/src/odbc/python/odbc.py.i
../../../../../src-head/sql/src/odbc/python/odbc.py.i:40:
Unable to find '/usr/include/sqltypes.h'
../../../../../src-head/sql/src/odbc/python/odbc.py.i:1064:
Unable to find '/usr/include/sql.h'
../../../../../src-head/sql/src/odbc/python/odbc.py.i:1083:
Unable to find '/usr/include/sqlext.h'
make[3]: *** [odbc.py.c] Error 1
make[3]: Leaving directory
`/nfs/poseidon/Temp/monet/build-head/sql/src/odbc/python'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory
`/nfs/poseidon/Temp/monet/build-head/sql/src/odbc'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/nfs/poseidon/Temp/monet/build-head/sql/src'
make: *** [install-recursive] Error 1
it refers to /usr/include, but there is no monetdb to
be found...
## Comment 1228
Date: 2004-05-12 20:31:46 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed by referring to the source directory of the sql*.h
include files.
## Comment 1229
Date: 2005-11-09 12:26:27 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: NO TEST / COMPILATION
## Comment 1230
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 952743 at http://sourceforge.net/support/tracker.php?aid=952743
| SQL compilation fails on odbc/python | https://api.github.com/repos/MonetDB/MonetDB/issues/228/comments | 0 | 2020-11-30T08:19:15Z | 2024-06-27T10:56:53Z | https://github.com/MonetDB/MonetDB/issues/228 | 753,262,359 | 228 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-11 11:12:14 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-11 02:29:08 +0200
## Comment 1224
Date: 2004-05-11 11:12:14 +0200
From: @arjan
Casting from bool to int on variable argument does not
work. On constant arguments its OK:
sql>select cast(true as integer);
[ 1 ]
But:
create table a (i integer);
insert into a values (1);
insert into a values (3);
select i<2 from a;
[ true ]
[ false ]
select cast(i<2 as integer) from a;
[ true ]
[ false ]
But this should return
[ 1 ]
[ 0 ]
By the way: i use this cast to compensate for the
missing 'case' statement. I would like to write 'select
case when i<2 then 1 else 0 end from a;'
## Comment 1225
Date: 2005-11-09 12:26:04 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
sql/src/test/bugs/cast_bool2int-bug-sf-951800.sql
sql/src/test/bugs/Tests/cast_bool2int-bug-sf-951800.stable.err
sql/src/test/bugs/Tests/cast_bool2int-bug-sf-951800.sql.src
sql/src/test/bugs/Tests/cast_bool2int-bug-sf-951800.stable.out
## Comment 1226
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 951800 at http://sourceforge.net/support/tracker.php?aid=951800
| SQL: CAST from bool on var. arg | https://api.github.com/repos/MonetDB/MonetDB/issues/227/comments | 0 | 2020-11-30T08:19:11Z | 2024-06-28T13:36:57Z | https://github.com/MonetDB/MonetDB/issues/227 | 753,262,322 | 227 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-10 02:19:25 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-11 02:35:04 +0200
## Comment 1220
Date: 2004-05-10 14:19:25 +0200
From: @arjan
The following query complains about a unknown alias:
select x from (select count(*) as x from tables) as t;
MAPI = monetdb@localhost:45123
ACTION= mapi_get_row
QUERY = select x from (select count(*) as x from
tables) as t;
ERROR = !Identifier: x unknown or ambigious
But,
select x from (select name as x from tables) as t;
gives a correct result indeed.
## Comment 1221
Date: 2004-05-11 14:35:04 +0200
From: @njnes
Logged In: YES
user_id=43556
result of count(*) is a single value. This single value of
the sub query
was put in a column hiding the name.
## Comment 1222
Date: 2005-11-09 12:25:27 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
sql/src/test/bugs/subselect_column-bug-sf-951206.sql
sql/src/test/bugs/Tests/subselect_column-bug-sf-951206.sql.src
sql/src/test/bugs/Tests/subselect_column-bug-sf-951206.stable.out
sql/src/test/bugs/Tests/subselect_column-bug-sf-951206.stable.err
## Comment 1223
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 951206 at http://sourceforge.net/support/tracker.php?aid=951206
| SQL: count(*) alias in subselect | https://api.github.com/repos/MonetDB/MonetDB/issues/226/comments | 0 | 2020-11-30T08:19:07Z | 2024-06-27T10:56:51Z | https://github.com/MonetDB/MonetDB/issues/226 | 753,262,273 | 226 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-08 12:55:40 +0200
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2004-05-08 02:08:23 +0200
## Comment 1216
Date: 2004-05-08 12:55:40 +0200
From: @grobian
During a totally clean checkout + compile on Gentoo
Linux I spotted these warnings (there were more numerous:
MapiLib.py.c:2818: warning: missing initializer
MapiLib.py.c:2818: warning: (near initialization for
`SwigMethods[82].ml_doc')
MapiLib.py.c:2819: warning: missing initializer
MapiLib.py.c:2819: warning: (near initialization for
`SwigMethods[83].ml_doc')
MapiLib.py.c:2820: warning: missing initializer
MapiLib.py.c:2820: warning: (near initialization for
`SwigMethods[84].ml_doc')
MapiLib.py.c:2821: warning: missing initializer
MapiLib.py.c:2821: warning: (near initialization for
`SwigMethods[85].ml_doc')
MapiLib.py.c:2822: warning: missing initializer
MapiLib.py.c:2822: warning: (near initialization for
`SwigMethods[86].ml_doc')
MapiLib.py.c:2823: warning: missing initializer
MapiLib.py.c:2823: warning: (near initialization for
`SwigMethods[87].ml_doc')
MapiLib.py.c:2824: warning: missing initializer
bootstrap version part:
automake 1.6.3 is 1.5 or newer. Good.
autoconf 2.58 is 2.53 or newer. Good.
libtool 1.4.3 is 1.4 or newer. Good.
Python 2.3.3 is 2.0.0 or newer. Good.
Compilation just finishes fine.
(Sorry Martin, I wasn't able to do this yesterday night
:) )
## Comment 1217
Date: 2004-05-08 14:08:23 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Known problem in generated code.
## Comment 1218
Date: 2005-11-09 12:24:48 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: NO TEST / COMPILATION
## Comment 1219
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 950358 at http://sourceforge.net/support/tracker.php?aid=950358
| Clean MonetDB gives lots of pythin warnings | https://api.github.com/repos/MonetDB/MonetDB/issues/225/comments | 0 | 2020-11-30T08:19:04Z | 2024-06-28T13:36:57Z | https://github.com/MonetDB/MonetDB/issues/225 | 753,262,239 | 225 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-06 05:09:01 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-07 10:56:54 +0200
## Comment 1213
Date: 2004-05-06 17:09:01 +0200
From: @arjan
Last bug for the day:
create table x (f float);
insert into x values (3.14);
select f/f from x;
sql_div_f name
float type
1 tuplecount
63 id
[ 1 ]
select cast(f/f as integer) from x;
MAPI = monetdb@localhost:45123
ACTION= mapi_get_row
QUERY = select cast(f/f as integer) from x;
ERROR = !Types float(51,0) (dbl) and mediumint(9,0)
(int) are not equal
*** But, using just constants *does* work (they're not
of type float, i guess)
select cast(3.14/3.14 as integer);
scale_up_single_value name
mediumint type
1 tuplecount
64 id
[ 1 ]
## Comment 1214
Date: 2005-11-09 12:23:39 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
sql/src/test/bugs/Tests/float_arith_cast2int-bug-sf-949255.stable.err
sql/src/test/bugs/Tests/float_arith_cast2int-bug-sf-949255.sql.src
sql/src/test/bugs/Tests/float_arith_cast2int-bug-sf-949255.stable.out
sql/src/test/bugs/float_arith_cast2int-bug-sf-949255.sql
## Comment 1215
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 949255 at http://sourceforge.net/support/tracker.php?aid=949255
| SQL: variable arguments in CAST function | https://api.github.com/repos/MonetDB/MonetDB/issues/224/comments | 0 | 2020-11-30T08:19:01Z | 2024-06-27T10:56:49Z | https://github.com/MonetDB/MonetDB/issues/224 | 753,262,191 | 224 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-06 04:44:42 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-07 10:53:03 +0200
## Comment 1209
Date: 2004-05-06 16:44:42 +0200
From: @arjan
Stumbled upon yet another bug....
This query is correct:
sql>select 1.0001/1.0001;
scale_up_single_value name
decimal type
1 tuplecount
24 id
[ 1.0000 ]
But then the errors start:
sql>select 1.000/1.0001;
convert_single_value name
decimal type
1 tuplecount
25 id
[ 0.0000 ]
sql>select 1.00001/1.00001;
scale_up_single_value name
decimal type
1 tuplecount
26 id
[ 0.14101 ]
sql>select 1.0/0.1;
scale_up_single_value name
decimal type
1 tuplecount
34 id
[ 1.0 ]
## Comment 1210
Date: 2004-05-07 22:53:03 +0200
From: @njnes
Logged In: YES
user_id=43556
We now cast to large types if needed. Also the 'a/b'
operator for
decimal types is changed. It now results in a type with the
max scale
of a and b.
## Comment 1211
Date: 2005-11-09 12:22:54 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
sql/src/test/bugs/arith-bug-sf-949228.sql
sql/src/test/bugs/Tests/arith-bug-sf-949228.stable.out
sql/src/test/bugs/Tests/arith-bug-sf-949228.stable.err
sql/src/test/bugs/Tests/arith-bug-sf-949228.sql.src
## Comment 1212
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 949228 at http://sourceforge.net/support/tracker.php?aid=949228
| SQL: Floating point '/' broken? | https://api.github.com/repos/MonetDB/MonetDB/issues/223/comments | 0 | 2020-11-30T08:18:58Z | 2024-06-27T10:56:48Z | https://github.com/MonetDB/MonetDB/issues/223 | 753,262,151 | 223 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-06 03:28:56 +0200
From: @arjan
To: Arjan Scherpenisse <<arjan>>
Version: -- development
Last updated: 2004-05-25 03:57:14 +0200
## Comment 1202
Date: 2004-05-06 15:28:56 +0200
From: @arjan
Sometimes, when I quit the server (using quit()), and I
restart it again, sql_server fails to load the database
and dies with the message:
Mserver: sql_mvc.mx:981: load_idxcolumn: Assertion `c'
failed.
The only option left then is removing the dbfarm and
log directories and rebuilding the database.
Sometimes, the server complains about wrong REFCOUNTs
when quitting the server, but I dont see how this is
connected with this problem.
I dont know how to reproduce the bug, this one just
happens sometimes, especially while I quit the server
during it having a high load from processing some query.
## Comment 1203
Date: 2004-05-06 19:00:33 +0200
From: @grobian
Logged In: YES
user_id=963970
confirming...
## Comment 1204
Date: 2004-05-11 15:23:40 +0200
From: @njnes
Logged In: YES
user_id=43556
Indeed the refcount is just a memory leak, so isn't
something to worry much
about.
I'll assign this bug to arjen and/or mr-meltdown to come up
with a
small script (could include stops and start of the server),
which triggers
this bug.
## Comment 1205
Date: 2004-05-25 15:57:14 +0200
From: @arjan
Logged In: YES
user_id=20087
Have not been able to reproduce this behaviour in last 2 weeks.
## Comment 1206
Date: 2005-11-09 12:21:48 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: RELEASED
REASSIGN to: Fabian, or Arjan Scherpenisse
Couldn't reproduce the bug, Fabian or Arjan might have a
script to trigger this bug.
## Comment 1207
Date: 2005-11-09 15:34:47 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-11-09, Stefan: NO TEST / REDUNDANT
"sometimes" cannot be tested;
there are tests that stop and restart Mserver (+sql_server)
on one database.
## Comment 1208
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 949164 at http://sourceforge.net/support/tracker.php?aid=949164
| irregular database messups | https://api.github.com/repos/MonetDB/MonetDB/issues/222/comments | 0 | 2020-11-30T08:18:54Z | 2024-06-28T13:36:56Z | https://github.com/MonetDB/MonetDB/issues/222 | 753,262,111 | 222 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-06 02:42:27 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-07 10:50:59 +0200
## Comment 1195
Date: 2004-05-06 14:42:27 +0200
From: @arjan
CREATE TABLE a (S varchar(255) PRIMARY KEY);
CREATE TABLE b (S varchar(255) PRIMARY KEY);
INSERT INTO a VALUES ('hallo');
INSERT INTO b SELECT S FROM a GROUP BY S;
MAPI = monetdb@localhost:45123
ACTION= mapi_get_row
QUERY = INSERT INTO b SELECT S FROM a GROUP BY S;
ERROR = !ERROR: null constraint b.s failed
Whereas the query
SELECT S FROM a GROUP BY S;
Yields the single "hallo" tuple (which is not null,
obviously). Without GROUP BY this is ok.
## Comment 1196
Date: 2004-05-06 14:44:01 +0200
From: @arjan
Logged In: YES
user_id=20087
Workaround:
INSERT INTO b SELECT * FROM (SELECT S FROM a GROUP BY S) AS t;
does work.
## Comment 1197
Date: 2004-05-06 15:05:08 +0200
From: @grobian
Logged In: YES
user_id=963970
you're not using an aggregate function, do you?
Why don't you use "SELECT DISTINCT S from a" ?
(I don't think this is related to the bug anyhow)
## Comment 1198
Date: 2004-05-06 15:17:12 +0200
From: @arjan
Logged In: YES
user_id=20087
My original query is ofcourse more complicated (using indeed
aggregate functions in the select), but this was the
simplest case I could reproduce the bug with.
## Comment 1199
Date: 2004-05-07 22:50:59 +0200
From: @njnes
Logged In: YES
user_id=43556
code incorrectly choose the single value route.
## Comment 1200
Date: 2005-11-09 12:15:11 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
sql/src/test/bugs/insert_into_groupby-bug-sf-949135.sql
sql/src/test/bugs/Tests/insert_into_groupby-bug-sf-949135.sql.src
sql/src/test/bugs/Tests/insert_into_groupby-bug-sf-949135.stable.err
sql/src/test/bugs/Tests/insert_into_groupby-bug-sf-949135.stable.out
## Comment 1201
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 949135 at http://sourceforge.net/support/tracker.php?aid=949135
| SQL: 'insert..select..group by' fails null constraint | https://api.github.com/repos/MonetDB/MonetDB/issues/221/comments | 0 | 2020-11-30T08:18:51Z | 2024-06-27T10:56:46Z | https://github.com/MonetDB/MonetDB/issues/221 | 753,262,078 | 221 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-06 12:59:45 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-07 10:50:07 +0200
## Comment 1191
Date: 2004-05-06 12:59:45 +0200
From: @arjan
select * from tables, (select count(*) from tables) as t2;
ERROR = !ERROR: interpret: no matching MIL operator to
'reverse(int)'.
!MAYBE YOU MEAN:
! reverse(BAT[any::1,any::2]) :
BAT[any::2,any::1]
---
A somewhat similar query yields a different error:
select * from (select count(*) from tables) as t2, tables;
ERROR = !ERROR: interpret: no matching MIL operator to
'project(int, int)'.
!MAYBE YOU MEAN:
! project(BAT[any::1,any]) : BAT[any::1,void]
! project(BAT[any::1,any], any::2) :
BAT[any::1,any::2]
!ERROR: join(param 1): evaluation error.
---
This query even crashes the server if executed multiple
times. Test script:
select * from (select count(*) from tables) as t2, tables;
rollback;
select * from (select count(*) from tables) as t2, tables;
rollback;
select * from (select count(*) from tables) as t2, tables;
monet>Mserver: sql_mvc.mx:2936: mvc_bind: Assertion
`b->dims.headtype == 0 && b->dims.hseq == 0' failed.
Afgebroken
## Comment 1192
Date: 2004-05-07 22:50:07 +0200
From: @njnes
Logged In: YES
user_id=43556
subquery wasn't marked as single value
## Comment 1193
Date: 2005-11-09 12:11:25 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
src/test/bugs/Tests/subselect_ambigious_columns-bug-sf-949071.stable.out
src/test/bugs/Tests/subselect_ambigious_columns-bug-sf-949071.stable.err
src/test/bugs/Tests/subselect_ambigious_columns-bug-sf-949071.sql.src
src/test/bugs/subselect_ambigious_columns-bug-sf-949071.sql
## Comment 1194
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 949071 at http://sourceforge.net/support/tracker.php?aid=949071
| SQL: Join with single-row subquery does not work | https://api.github.com/repos/MonetDB/MonetDB/issues/220/comments | 0 | 2020-11-30T08:18:47Z | 2024-06-27T10:56:45Z | https://github.com/MonetDB/MonetDB/issues/220 | 753,262,045 | 220 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-05 09:57:31 +0200
From: @mlkersten
To: @sjoerdmullender
Version: -- development
CC: xubochin
Last updated: 2012-02-11 10:55:58 +0100
## Comment 1184
Date: 2004-05-05 21:57:31 +0200
From: @mlkersten
Compilation error after freshly compile in SQL on
Linux/orion
Martin Kersten wrote:
...opensource/sql/src/odbc/driver/SQLFetch.c -fPIC
-DPIC -o SQLFetch.lo
> cc1: warnings being treated as errors
> ...opensource/sql/src/odbc/driver/SQLFetch.c:57:
warning: static declaration for `strncasecmp' follows
non-static
> make[4]: *** [SQLFetch.lo] Error 1
(temporary solution, remove: 'static')
## Comment 1185
Date: 2004-05-05 22:11:17 +0200
From: @njnes
Logged In: YES
user_id=43556
Were fresh checkouts of both MonetDB and sql used?
## Comment 1186
Date: 2004-05-05 22:11:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Martin,
the latest version of SQL is supposed to compile with both
the latest head (4.3.17) and the latest stable
(MonetDB_4-3-16) of MonetDB --- at least it does for me on
draco (which is supposed to be identical with orion) and
during nightly testing (at least on those platforms where
MonetDB did compile last night; cf
http://stem.ins.cwi.nl:8000/projects/monetdb/Development/TestWeb/Stable/sql/sql/.Makes3/index.html
and
http://stem.ins.cwi.nl:8000/projects/monetdb/Development/TestWeb/Current/sql/sql/.Makes3/index.html
Hence, are you sure, you have both MonetDB and SQL up to
date, re-bootstrapped, make-d and installed properly?
could you please check the output of
grep STRNCASECMP $MONET_PREFIX/include/MonetDB/monetdb_config.h
It should say
define HAVE_STRNCASECMP 1
did you use any other than the default configure options?
## Comment 1187
Date: 2004-05-05 22:38:46 +0200
From: @mlkersten
Logged In: YES
user_id=490798
MonetDB version is 4.3.17
SQLversion 2.0.16
MonetDB updated and compiled this morning.
SQL updated and compiled from scratch.
Redone both with de-boot initialy solved it
## Comment 1188
Date: 2004-05-06 10:27:12 +0200
From: @mlkersten
Logged In: YES
user_id=490798
It should have been closed
## Comment 1189
Date: 2005-11-09 12:06:33 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: NO TEST / COMPILATION
## Comment 1190
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 948753 at http://sourceforge.net/support/tracker.php?aid=948753
| Compilation ODBC failed | https://api.github.com/repos/MonetDB/MonetDB/issues/219/comments | 0 | 2020-11-30T08:18:44Z | 2024-06-28T13:36:55Z | https://github.com/MonetDB/MonetDB/issues/219 | 753,262,012 | 219 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-05 02:04:53 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2004-05-06 05:19:16 +0200
## Comment 1180
Date: 2004-05-05 14:04:53 +0200
From: @drstmane
With the latest changes in
src/mapi/clients/python/Cimpl/, "make rpm" (and "make
distcheck") fail as
src/mapi/clients/python/Cimpl/Makefile.in is not
included in the source distribution during "make dist".
see
~monet/Current/.Logs..2004.05.05_06-51-54./MdoClient..GNU..32..d..Linux2.4.20-20.9perfctrsmp..draco.ins..One..MonetDB..Mrpm
for details.
## Comment 1181
Date: 2004-05-06 17:19:15 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed by switching over to autogen.
## Comment 1182
Date: 2005-11-09 12:06:14 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: NO TEST / COMPILATION
## Comment 1183
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 948424 at http://sourceforge.net/support/tracker.php?aid=948424
| "make rpm" fails | https://api.github.com/repos/MonetDB/MonetDB/issues/218/comments | 0 | 2020-11-30T08:18:41Z | 2024-06-27T10:56:43Z | https://github.com/MonetDB/MonetDB/issues/218 | 753,261,982 | 218 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-05 01:02:58 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2004-05-06 04:37:36 +0200
## Comment 1176
Date: 2004-05-05 13:02:58 +0200
From: @drstmane
On Cygwin, compilation of src/mapi/clients/python/Cimpl
failes due to problems with swig (se below) and cannot
even be ignored by "make -k".
Our Cygwin has swig-1.3.19 installed.
========
make[7]: Entering directory
`/var/tmp/monet.GNU_32-s.10394/MonetDB/CYGWIN1.5.7/src/mapi/clients/python/Cimpl'
swig -outdir . -o Mapi_wrap.c -python -I../../C
/var/tmp/monet.GNU_32-s.10394/MonetDB/src/mapi/clients/python/Cimpl/Mapi.i
swig error : Unrecognized option -outdir
swig error : Unrecognized option .
Use 'swig -help' for available options.
make[7]: *** [Mapi_wrap.c] Error 1
cp
/var/tmp/monet.GNU_32-s.10394/MonetDB/src/mapi/clients/python/Cimpl/Mapi.py
.
tar cf - -C
/var/tmp/monet.GNU_32-s.10394/MonetDB/src/mapi/clients/python/Cimpl
MonetSQLdb | tar xf -
make[7]: Target `all' not remade because of errors.
make[7]: Leaving directory
`/var/tmp/monet.GNU_32-s.10394/MonetDB/CYGWIN1.5.7/src/mapi/clients/python/Cimpl'
make[6]: *** [all-recursive] Error 1
========
## Comment 1177
Date: 2004-05-06 16:37:36 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed by testing whether swig understands the -outdir option
at configure time.
## Comment 1178
Date: 2005-11-09 12:05:50 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: NO TEST / COMPILATION
## Comment 1179
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 948382 at http://sourceforge.net/support/tracker.php?aid=948382
| compiling MonetDB failes on Cygwin | https://api.github.com/repos/MonetDB/MonetDB/issues/217/comments | 0 | 2020-11-30T08:18:38Z | 2024-06-27T10:56:42Z | https://github.com/MonetDB/MonetDB/issues/217 | 753,261,946 | 217 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-05 12:50:10 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2004-05-06 04:37:28 +0200
## Comment 1172
Date: 2004-05-05 12:50:10 +0200
From: @drstmane
With the latest changes in autogen, bootstrap fails on
apps (SunOS5.8) and spin (Debian3.0, 64bit); see below.
Note: apps and spin are the only testing machines with
python 2.1.x; all others have python >= 2.2 .
========
07:04:53 > ./bootstrap
07:04:53 >
automake 1.7.4 is 1.5 or newer. Good.
autoconf 2.57 is 2.53 or newer. Good.
libtool 1.5 is 1.4 or newer. Good.
Python 2.1.1 is 2.0.0 or newer. Good.
src/utils/autogen/autogen.py:130: SyntaxWarning: local
name 'cwd' in 'main' shadows use of 'cwd' as global in
nested scope '
def main(cwd, topdir, automake, incdirsmap):
src/utils/autogen/autogen.py:130: SyntaxWarning: local
name 'topdir' in 'main' shadows use of 'topdir' as
global in nested s
def main(cwd, topdir, automake, incdirsmap):
/var/tmp/monet.ntv_64-d.10394/MonetDB/src
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/utils
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/utils/Mx
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/utils/autogen
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/mel
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/common
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/gdk
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/monet
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/modules
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/modules/plain
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/modules/contrib
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/modules/calibrator
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/mapi
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/mapi/clients
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/mapi/clients/C
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/mapi/clients/perl
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/mapi/clients/perl/DBD
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/mapi/clients/python
/var/tmp/monet.ntv_64-d.10394/MonetDB/src/mapi/clients/python/Cimpl
Traceback (most recent call last):
File "src/utils/autogen/autogen.py", line 156, in ?
(InstallList, OutList) = main(topdir, topdir,
automake, [])
File "src/utils/autogen/autogen.py", line 147, in main
(deltaInstallList, deltaOutList) = \
File "src/utils/autogen/autogen.py", line 147, in main
(deltaInstallList, deltaOutList) = \
File "src/utils/autogen/autogen.py", line 147, in main
(deltaInstallList, deltaOutList) = \
File "src/utils/autogen/autogen.py", line 147, in main
(deltaInstallList, deltaOutList) = \
File "src/utils/autogen/autogen.py", line 147, in main
(deltaInstallList, deltaOutList) = \
File "src/utils/autogen/autogen.py", line 133, in main
filter(lambda x: x[-3:] == '.in', os.listdir(cwd)))
File "src/utils/autogen/autogen.py", line 132, in
<lambda>
OutList = map(lambda x: os.path.join(cwd,
x)[len(topdir) + 1:-3],
NameError: global name 'cwd' is not defined
cat: acout.in: No such file or directory
Remember to add `AC_PROG_LIBTOOL' to `configure.in'.
You should add the contents of
`/var/tmp/soft/libtool-1.5/share/aclocal/libtool.m4' to
`aclocal.m4'.
Putting files in AC_CONFIG_AUX_DIR, `conf'.
configure.in: installing `conf/install-sh'
configure.in: installing `conf/mkinstalldirs'
automake: no `Makefile.am' found or specified
========
## Comment 1173
Date: 2004-05-06 16:37:27 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed by using a completely different approach to
integrating SWIG into the build process. This approach
doesn't use the code in autogen which failed on older
versions of Python.
## Comment 1174
Date: 2005-11-09 12:05:29 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: NO TEST / COMPILATION
## Comment 1175
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 948376 at http://sourceforge.net/support/tracker.php?aid=948376
| bootstrap fails on apps and spin | https://api.github.com/repos/MonetDB/MonetDB/issues/216/comments | 0 | 2020-11-30T08:18:34Z | 2024-06-27T10:56:41Z | https://github.com/MonetDB/MonetDB/issues/216 | 753,261,903 | 216 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-04 01:04:17 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-12 10:40:02 +0200
## Comment 1167
Date: 2004-05-04 13:04:17 +0200
From: @arjan
Although the query below is incorrect it should not
crash the server:
select name from tables having 1=1;
Message is: missing tail column 53: ptable
Mserver: sql_statement.mx:1707: tail_column: Assertion
`0' failed.
----
The query:
select name from tables group by name having 1=1;
Causes a infinite loop (?).. the Mserver process takes
100% cpu and does not produce results.
## Comment 1168
Date: 2004-05-11 15:19:36 +0200
From: @njnes
Logged In: YES
user_id=43556
added support for predicates in having.
It seems
select name from tables having 1=1;
is allowed by sql spec's
## Comment 1169
Date: 2004-05-12 13:57:30 +0200
From: @arjan
Logged In: YES
user_id=20087
The second case still seems to produce an error:
sql>select name from tables group by name having 1=1;
MAPI = monetdb@localhost:45123
ACTION= mapi_get_row
QUERY = select name from tables group by name having 1=1;
ERROR = !ERROR: interpret: no matching MIL operator to
'semijoin(BAT[oid,oid], bit)'.
!MAYBE YOU MEAN:
! semijoin(BAT[any::1,any::2],
BAT[any::1,any]) : BAT[any::1,any::2]
## Comment 1170
Date: 2005-11-09 12:04:05 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: TEST ADDED / SUCCESS
sql/src/test/BugDay_2005-11-09_2.9.3/Tests/having_clause_quirks.SF-947601.*
## Comment 1171
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 947601 at http://sourceforge.net/support/tracker.php?aid=947601
| SQL: HAVING clause quirks | https://api.github.com/repos/MonetDB/MonetDB/issues/215/comments | 0 | 2020-11-30T08:18:31Z | 2024-06-27T10:56:41Z | https://github.com/MonetDB/MonetDB/issues/215 | 753,261,866 | 215 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-04 12:58:39 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-07 10:48:54 +0200
## Comment 1163
Date: 2004-05-04 12:58:39 +0200
From: @arjan
SELECT a.id, b.id, COUNT(*)
FROM artist a, track ta,
artist b, track tb
WHERE a.id < b.id AND
a.id = ta.artist AND
b.id = tb.artist AND
ta.title = tb.title
GROUP BY a.id, b.id
HAVING COUNT(*) >= 1
crashes the server w/ message "missing head type 42:
derive"
without the HAVING clause, this goes ok.
Unfortunately I am not able to produce this error using
a small test database.
## Comment 1164
Date: 2004-05-07 22:48:54 +0200
From: @njnes
Logged In: YES
user_id=43556
group columns are kept arround, ie making the semantic checks
in the selection part simpler. No longer need the head/column
bits
## Comment 1165
Date: 2005-11-09 10:44:23 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-11-09, Jennie: ALREADY IN TESTWEB
src/test/bugs/groupby_having-bug-sf-947600.sql
src/test/bugs/Tests/groupby_having-bug-sf-947600.stable.err
src/test/bugs/Tests/groupby_having-bug-sf-947600.stable.out
src/test/bugs/Tests/groupby_having-bug-sf-947600.sql.src
## Comment 1166
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 947600 at http://sourceforge.net/support/tracker.php?aid=947600
| SQL: Server crash in HAVING clause | https://api.github.com/repos/MonetDB/MonetDB/issues/214/comments | 0 | 2020-11-30T08:18:28Z | 2024-06-27T10:56:40Z | https://github.com/MonetDB/MonetDB/issues/214 | 753,261,833 | 214 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-03 03:24:58 +0200
From: @arjan
To: @njnes
Version: -- development
Last updated: 2004-05-03 08:10:24 +0200
## Comment 1158
Date: 2004-05-03 15:24:58 +0200
From: @arjan
Using a function in a group by clause yields a parse error:
create table test (s string);
insert into test values('a');
insert into test values('b');
insert into test values('c');
insert into test values('aa');
insert into test values('aaa');
insert into test values('aa');
insert into test values('bbb');
commit;
select char_length(s) from test group by char_length(s);
MAPI = monetdb@localhost:45123
ACTION= mapi_get_row
QUERY = select char_length(s) from test group by
char_length(s);
ERROR = !ERROR parse error at token (40) in statement:
select char_length(s) from test group by char_length(
## Comment 1159
Date: 2004-05-03 20:10:24 +0200
From: @njnes
Logged In: YES
user_id=43556
expressions in the group by clause are not allowed (see
sql'99 spec)
## Comment 1160
Date: 2004-05-03 20:33:37 +0200
From: @MarcinZukowski
Logged In: YES
user_id=607094
Geeee.
Yet another point in which X100 is not SQL'99 compliant :D
## Comment 1161
Date: 2005-10-06 18:23:05 +0200
From: @BitGrit
Logged In: YES
user_id=1292024
BugDay_2005-10-06: Claimed by Sandor.
BugDay_2005-10-06: NO TEST / INVALID
Invalid bug report according to Niels' comment
## Comment 1162
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 946935 at http://sourceforge.net/support/tracker.php?aid=946935
| GROUP BY on functions | https://api.github.com/repos/MonetDB/MonetDB/issues/213/comments | 0 | 2020-11-30T08:18:24Z | 2024-06-28T13:36:55Z | https://github.com/MonetDB/MonetDB/issues/213 | 753,261,788 | 213 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-05-02 12:54:08 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-05-02 02:28:31 +0200
## Comment 1154
Date: 2004-05-02 12:54:08 +0200
From: @grobian
in the latest head branch it seems that sending some
command over SQL crashes the server (on a clean
database (var dir))
Also if a new var directory has been created by
Mserver, issueing module(sql_server) seems to crash
Mserver silently.
Since Mserver receives SIGKILL gdb thinks the program
no longer exists.
Linux 2.6.5-gentoo-r1 2 SMP
## Comment 1155
Date: 2004-05-02 14:28:31 +0200
From: @njnes
Logged In: YES
user_id=43556
As can be seen using the testweb, this bugreport isn't valid.
http://monetdb.cwi.nl/Development/TestWeb/Current/sql/sql/.mTests103/index.html
## Comment 1156
Date: 2005-10-06 18:19:34 +0200
From: @BitGrit
Logged In: YES
user_id=1292024
BugDay_2005-10-06: Claimed by Sandor.
BugDay_2005-10-06: NO TEST / REDUNDANT
Invalid bugreport, according to Niels' comment
## Comment 1157
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 946345 at http://sourceforge.net/support/tracker.php?aid=946345
| SQL: Meltdown module(sql_server) ? | https://api.github.com/repos/MonetDB/MonetDB/issues/212/comments | 0 | 2020-11-30T08:18:22Z | 2024-06-28T13:36:54Z | https://github.com/MonetDB/MonetDB/issues/212 | 753,261,759 | 212 |
[
"MonetDB",
"MonetDB"
] | Date: 2004-04-29 10:35:14 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2004-05-01 03:06:31 +0200
## Comment 1149
Date: 2004-04-29 10:35:14 +0200
From: @grobian
The newest Monet, with the newest SQL module (both head
branch) crash on getTables query.
SELECT * FROM (
SELECT null AS "TABLE_CAT", "schemas"."name" AS
"TABLE_SCHEM", "tables"."name" AS "TABLE_NAME",
'SYSTEM TABLE' AS "TABLE_TYPE", '' AS "REMARKS", null
AS "TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'id' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS "REF_GENERATION"
FROM "tables", "schemas" WHERE "tables"."schema_id" =
"schemas"."id" AND "tables"."type" = 1
UNION ALL
SELECT null AS "TABLE_CAT", "schemas"."name" AS
"TABLE_SCHEM", "tables"."name" AS "TABLE_NAME",
'TABLE' AS "TABLE_TYPE", '' AS "REMARKS", null AS
"TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'id' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS "REF_GENERATION"
FROM "tables", "schemas" WHERE "tables"."schema_id" =
"schemas"."id" AND "tables"."type" = 0
UNION ALL
SELECT null AS "TABLE_CAT", "schemas"."name" AS
"TABLE_SCHEM", "tables"."name" AS "TABLE_NAME",
'VIEW' AS "TABLE_TYPE", '' AS "REMARKS", null AS
"TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'id' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS "REF_GENERATION"
FROM "tables", "schemas" WHERE "tables"."schema_id" =
"schemas"."id" AND "tables"."type" = 2
UNION ALL
SELECT null AS "TABLE_CAT", "schemas"."name" AS
"TABLE_SCHEM", "tables"."name" AS "TABLE_NAME",
'SESSION TEMPORARY TABLE' AS "TABLE_TYPE", '' AS
"REMARKS", null AS "TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'id' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS "REF_GENERATION"
FROM "tables", "schemas" WHERE "tables"."schema_id" =
"schemas"."id" AND "tables"."type" = 3
UNION ALL
SELECT null AS "TABLE_CAT", "schemas"."name" AS
"TABLE_SCHEM", "tables"."name" AS "TABLE_NAME",
'TEMPORARY TABLE' AS "TABLE_TYPE", '' AS "REMARKS",
null AS "TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'id' AS
"SELF_REFERENCING_COL_NAME", 'SYSTEM' AS "REF_GENERATION"
FROM "tables", "schemas" WHERE "tables"."schema_id" =
"schemas"."id" AND "tables"."type" = 4
) AS "tables" WHERE 1 = 1
AND ("TABLE_TYPE" LIKE 'TABLE' OR "TABLE_TYPE" LIKE
'VIEW')
ORDER BY "TABLE_TYPE", "TABLE_SCHEM", "TABLE_NAME";
without the where clause with AND and OR the query runs
fine.
(the attached file contains the same query)
## Comment 1150
Date: 2004-04-29 10:41:10 +0200
From: @grobian
Logged In: YES
user_id=963970
Could have done this immediately:
A smaller variant:
SELECT * FROM (
SELECT null AS "TABLE_CAT", "schemas"."name" AS
"TABLE_SCHEM", "tables"."name" AS "TABLE_NAME",
'SYSTEM TABLE' AS "TABLE_TYPE", '' AS "REMARKS", null AS
"TYPE_CAT", null AS "TYPE_SCHEM",
null AS "TYPE_NAME", 'id' AS "SELF_REFERENCING_COL_NAME",
'SYSTEM' AS "REF_GENERATION"
FROM "tables", "schemas" WHERE "tables"."schema_id" =
"schemas"."id" AND "tables"."type" = 1
) AS "tables" WHERE 1 = 1
AND ("TABLE_TYPE" LIKE 'TABLE' OR "TABLE_TYPE" LIKE 'VIEW')
ORDER BY "TABLE_TYPE", "TABLE_SCHEM", "TABLE_NAME";
this variant is TOO small:
SELECT * FROM (
SELECT 'SYSTEM TABLE' AS "TABLE_TYPE"
) AS "tables" WHERE 1 = 1
AND ("TABLE_TYPE" LIKE 'TABLE' OR "TABLE_TYPE" LIKE 'VIEW')
ORDER BY "TABLE_TYPE";
for it generates:
MAPI = monetdb@localhost:45123
ACTION= mapi_get_row
QUERY = SELECT * FROM (
ERROR = !ERROR: interpret: no matching MIL operator to
'reverse(str)'.
!MAYBE YOU MEAN:
! reverse(BAT[any::1,any::2]) : BAT[any::2,any::1]
!ERROR: sort(param 1): evaluation error.
!ERROR: reverse(param 1): evaluation error.
!ERROR: sql0: 3.thash.
## Comment 1151
Date: 2004-05-01 15:06:31 +0200
From: @njnes
Logged In: YES
user_id=43556
missed the case st_basetable in tail_column (this
gave an assertion)
## Comment 1152
Date: 2005-10-06 18:16:47 +0200
From: @BitGrit
Logged In: YES
user_id=1292024
BugDay_2005-10-06: Claimed by Sandor.
BugDay_2005-10-06: TEST ADDED / SUCCESS
(jdbc_crashes_on_getTables.SF_944316.sql)
## Comment 1153
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 944316 at http://sourceforge.net/support/tracker.php?aid=944316
| SQL: Meltdown on JDBC query | https://api.github.com/repos/MonetDB/MonetDB/issues/211/comments | 0 | 2020-11-30T08:18:18Z | 2024-06-27T10:56:37Z | https://github.com/MonetDB/MonetDB/issues/211 | 753,261,727 | 211 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.