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: 2005-12-20 08:25:28 +0100
From: @mlkersten
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-01-15 09:11:05 +0100
## Comment 4697
Date: 2005-12-20 20:25:28 +0100
From: @mlkersten
./BugsViaSourgeforce/Tests/ID.1200626.valgrind.out:==25496==
ERROR SUMMARY: 38 errors from 4 contexts (suppressed:
13 from 5)
==26334== Use of uninitialised value of size 8
==26334== at 0x134EFDFA: _itoa_word (in
/lib64/libc-2.3.5.so)
==26334== by 0x134F2D5A: vfprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x13513B69: vsnprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x134F9972: snprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x1202EAB0: local_itoa (bat.mx:1201)
==26334== by 0x12030303: CMDinfo (bat.mx:1332)
==26334== by 0x1202BE53: CMDinfo_unpack1272454829
(bat.glue.c:1297)
==26334== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26334== by 0x11C466D4: interpret_params
(monet_interpreter.mx:410)
==26334== by 0x11C3C266: interpret
(monet_interpreter.mx:973)
==26334== by 0x11C466D4: interpret_params
(monet_interpreter.mx:410)
==26334== by 0x11C3C266: interpret
(monet_interpreter.mx:973)
==26334==
==26334== Conditional jump or move depends on
uninitialised value(s)
==26334== at 0x134EFE04: _itoa_word (in
/lib64/libc-2.3.5.so)
==26334== by 0x134F2D5A: vfprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x13513B69: vsnprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x134F9972: snprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x1202EAB0: local_itoa (bat.mx:1201)
==26334== by 0x12030303: CMDinfo (bat.mx:1332)
==26334== by 0x1202BE53: CMDinfo_unpack1272454829
(bat.glue.c:1297)
==26334== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26334== by 0x11C466D4: interpret_params
(monet_interpreter.mx:410)
==26334== by 0x11C3C266: interpret
(monet_interpreter.mx:973)
==26334== by 0x11C466D4: interpret_params
(monet_interpreter.mx:410)
==26334== by 0x11C3C266: interpret
(monet_interpreter.mx:973)
==26334==
==26334== Conditional jump or move depends on
uninitialised value(s)
==26334== at 0x134F347A: vfprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x13513B69: vsnprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x134F9972: snprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x1202EAB0: local_itoa (bat.mx:1201)
==26334== by 0x12030303: CMDinfo (bat.mx:1332)
==26334== by 0x1202BE53: CMDinfo_unpack1272454829
(bat.glue.c:1297)
==26334== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26334== by 0x11C466D4: interpret_params
(monet_interpreter.mx:410)
==26334== by 0x11C3C266: interpret
(monet_interpreter.mx:973)
==26334== by 0x11C466D4: interpret_params
(monet_interpreter.mx:410)
==26334== by 0x11C3C266: interpret
(monet_interpreter.mx:973)
==26334== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26334==
==26334== Conditional jump or move depends on
uninitialised value(s)
==26334== at 0x134F1B77: vfprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x13513B69: vsnprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x134F9972: snprintf (in
/lib64/libc-2.3.5.so)
==26334== by 0x1202EAB0: local_itoa (bat.mx:1201)
==26334== by 0x12030303: CMDinfo (bat.mx:1332)
==26334== by 0x1202BE53: CMDinfo_unpack1272454829
(bat.glue.c:1297)
==26334== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26334== by 0x11C466D4: interpret_params
(monet_interpreter.mx:410)
==26334== by 0x11C3C266: interpret
(monet_interpreter.mx:973)
==26334== by 0x11C466D4: interpret_params
(monet_interpreter.mx:410)
==26334== by 0x11C3C266: interpret
(monet_interpreter.mx:973)
==26334== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
## Comment 4698
Date: 2005-12-31 17:50:42 +0100
From: @drstmane
Logged In: YES
user_id=572415
The "void hack fields" in the BAT header (void_tid,
void_cnt, void_seq1, void_seq2) were never initialized with
BATnew.
Fixed in CVS.
Martin,
could you please check, whether valgrind is now "satisfied"?
## Comment 4699
Date: 2006-01-01 18:04:47 +0100
From: @mlkersten
Logged In: YES
user_id=490798
UNfortunately the patches do not yet solve the problem.
[ "65" ]
==18236== Use of uninitialised value of size 8
==18236== at 0x134F1DFA: _itoa_word (in /lib64/libc-2.3.5.so)
==18236== by 0x134F4D5A: vfprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x13515B69: vsnprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x134FB972: snprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x12030260: local_itoa (bat.mx:1201)
==18236== by 0x12031AA3: CMDinfo (bat.mx:1332)
==18236== by 0x1202D403: CMDinfo_unpack1935170689
(bat.glue.c:1297)
==18236== by 0x11C3D829: interpret
(monet_interpreter.mx:1169)
==18236== by 0x11C46744: interpret_params
(monet_interpreter.mx:410)
==18236== by 0x11C3C2D6: interpret (monet_interpreter.mx:973)
==18236== by 0x11C46744: interpret_params
(monet_interpreter.mx:410)
==18236== by 0x11C3C2D6: interpret (monet_interpreter.mx:973)
==18236==
==18236== Conditional jump or move depends on uninitialised
value(s)
==18236== at 0x134F1E04: _itoa_word (in /lib64/libc-2.3.5.so)
==18236== by 0x134F4D5A: vfprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x13515B69: vsnprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x134FB972: snprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x12030260: local_itoa (bat.mx:1201)
==18236== by 0x12031AA3: CMDinfo (bat.mx:1332)
==18236== by 0x1202D403: CMDinfo_unpack1935170689
(bat.glue.c:1297)
==18236== by 0x11C3D829: interpret
(monet_interpreter.mx:1169)
==18236== by 0x11C46744: interpret_params
(monet_interpreter.mx:410)
==18236== by 0x11C3C2D6: interpret (monet_interpreter.mx:973)
==18236== by 0x11C46744: interpret_params
(monet_interpreter.mx:410)
==18236== by 0x11C3C2D6: interpret (monet_interpreter.mx:973)
==18236==
==18236== Conditional jump or move depends on uninitialised
value(s)
==18236== at 0x134F547A: vfprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x13515B69: vsnprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x134FB972: snprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x12030260: local_itoa (bat.mx:1201)
==18236== by 0x12031AA3: CMDinfo (bat.mx:1332)
==18236== by 0x1202D403: CMDinfo_unpack1935170689
(bat.glue.c:1297)
==18236== by 0x11C3D829: interpret
(monet_interpreter.mx:1169)
==18236== by 0x11C46744: interpret_params
(monet_interpreter.mx:410)
==18236== by 0x11C3C2D6: interpret (monet_interpreter.mx:973)
==18236== by 0x11C46744: interpret_params
(monet_interpreter.mx:410)
==18236== by 0x11C3C2D6: interpret (monet_interpreter.mx:973)
==18236== by 0x11C454FE: interpret_seqblock
(monet_interpreter.mx:1817)
==18236==
==18236== Conditional jump or move depends on uninitialised
value(s)
==18236== at 0x134F3B77: vfprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x13515B69: vsnprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x134FB972: snprintf (in /lib64/libc-2.3.5.so)
==18236== by 0x12030260: local_itoa (bat.mx:1201)
==18236== by 0x12031AA3: CMDinfo (bat.mx:1332)
==18236== by 0x1202D403: CMDinfo_unpack1935170689
(bat.glue.c:1297)
==18236== by 0x11C3D829: interpret
(monet_interpreter.mx:1169)
==18236== by 0x11C46744: interpret_params
(monet_interpreter.mx:410)
==18236== by 0x11C3C2D6: interpret (monet_interpreter.mx:973)
==18236== by 0x11C46744: interpret_params
(monet_interpreter.mx:410)
==18236== by 0x11C3C2D6: interpret (monet_interpreter.mx:973)
==18236== by 0x11C454FE: interpret_seqblock
(monet_interpreter.mx:1817)
[ "65" ]
[ "0" ]
[ "65" ]
[ "65" ]
[ "65" ]
## Comment 4700
Date: 2006-01-15 17:08:03 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Initialize static variables did not help to resolve it
## Comment 4701
Date: 2006-01-15 21:11:05 +0100
From: @peterboncz
Logged In: YES
user_id=591107
sorry, but this is a warning about the system libraries
## Comment 4702
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1386441 at http://sourceforge.net/support/tracker.php?aid=1386441
| Mserver: Valgrind detected error 7 | https://api.github.com/repos/MonetDB/MonetDB/issues/810/comments | 0 | 2020-11-30T09:00:09Z | 2024-06-28T07:36:45Z | https://github.com/MonetDB/MonetDB/issues/810 | 753,289,523 | 810 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-20 08:23:35 +0100
From: @mlkersten
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-01-15 09:10:37 +0100
## Comment 4693
Date: 2005-12-20 20:23:35 +0100
From: @mlkersten
./BugsViaSourgeforce/Tests/ID.602463.valgrind.out:==25506==
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 10
from 5)
==26327== Conditional jump or move depends on
uninitialised value(s)
==26327== at 0x12A2FA0C: batfetchjoin (gdk_relop.mx:805)
==26327== by 0x12A3F82A: BATjoin (gdk_relop.mx:1107)
==26327== by 0x11DC465D: CMDjoin (algebra.mx:1772)
==26327== by 0x11DBFCC6: CMDjoin_unpack697001
(algebra.glue.c:1695)
==26327== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26327== by 0x11C3CC43: interpret
(monet_interpreter.mx:819)
==26327== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26327== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26327== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26327== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26327== by 0x11C3C68A: interpret
(monet_interpreter.mx:1155)
==26327== by 0x11C466D4: interpret_params
(monet_interpreter.mx:410)
## Comment 4694
Date: 2006-01-15 17:09:39 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Check the urgency of this error
## Comment 4695
Date: 2006-01-15 21:10:37 +0100
From: @peterboncz
Logged In: YES
user_id=591107
code is obviously correct; line 805 contains variables
that are obviously initialied (in the previous lines).
valgrind is wrong here.
## Comment 4696
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1386439 at http://sourceforge.net/support/tracker.php?aid=1386439
| Mserver: Valgrind detected error 6 | https://api.github.com/repos/MonetDB/MonetDB/issues/809/comments | 0 | 2020-11-30T09:00:07Z | 2024-06-28T07:36:45Z | https://github.com/MonetDB/MonetDB/issues/809 | 753,289,487 | 809 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-20 08:21:56 +0100
From: @mlkersten
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-01-24 08:15:53 +0100
## Comment 4686
Date: 2005-12-20 20:21:56 +0100
From: @mlkersten
./BugsViaSourgeforce/Tests/ID.602271.valgrind.out:==25503==
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 10
from 5)
==26317== Conditional jump or move depends on
uninitialised value(s)
==26317== at 0x12A2FA0C: batfetchjoin (gdk_relop.mx:805)
==26317== by 0x12A3F82A: BATjoin (gdk_relop.mx:1107)
==26317== by 0x11DC465D: CMDjoin (algebra.mx:1772)
==26317== by 0x11DBFCC6: CMDjoin_unpack697001
(algebra.glue.c:1695)
==26317== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26317== by 0x11C3CC43: interpret
(monet_interpreter.mx:819)
==26317== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26317== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26317== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26317== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26317== by 0x11C3C68A: interpret
(monet_interpreter.mx:1155)
==26317== by 0x11C45813: interpret_assignment
(monet_interpreter.mx:1767)
## Comment 4687
Date: 2006-01-15 17:10:46 +0100
From: @mlkersten
Logged In: YES
user_id=490798
seems related to valgrind 6 problem
## Comment 4688
Date: 2006-01-15 21:09:05 +0100
From: @peterboncz
Logged In: YES
user_id=591107
the code is obviously correct to any casual observer
it initializes 4 variables on the stack, en then uses
these in a comparison.
valgrind must be wrong here; or at least the issue is
another one.
## Comment 4689
Date: 2006-01-15 21:43:17 +0100
From: @drstmane
Logged In: YES
user_id=572415
Martin,
how was your Mserver compiled for the valgrind run?
(1) default, (2) --enable-optimize, (3) --enable-debug?
only in the latter case, I'd trust valgrind; the default
uses "-g -O2" with gcc, and that might confuse valgrind,
just as it confuses gdb ...
## Comment 4690
Date: 2006-01-15 22:09:14 +0100
From: @mlkersten
Logged In: YES
user_id=490798
All my compilations of M4 (and M5) uses the default settings
only. I trust valgrind in the sense that warnings indeed
point to mistakes, some major/some minor. A failure in a
library routine, like vnprintf, may be the result of passing
a non-initialized data item. So don't take a short cut
disposal of the problem on first sight.
Typical problems encountered are passing 'static arrays',
which are assumed zero, and therefore not necessarily set.
The problem here is tricky, I have seen it before and it was
related to malicious reuse of freed uninitialized
space(malloc/free).
## Comment 4691
Date: 2006-01-24 08:15:53 +0100
From: @njnes
Logged In: YES
user_id=43556
valgrind no longer gives the errors. So this bug is fixed. I
guess it was related to the non initialized variables in aggrX3.
## Comment 4692
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1386437 at http://sourceforge.net/support/tracker.php?aid=1386437
| Mserver: Valgrind detected error 5 | https://api.github.com/repos/MonetDB/MonetDB/issues/808/comments | 0 | 2020-11-30T09:00:03Z | 2024-06-27T11:08:09Z | https://github.com/MonetDB/MonetDB/issues/808 | 753,289,441 | 808 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-20 08:19:48 +0100
From: @mlkersten
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-01-15 09:07:08 +0100
## Comment 4682
Date: 2005-12-20 20:19:48 +0100
From: @mlkersten
./BugsViaSourgeforce/Tests/ID.1049942.valgrind.out:==25480==
ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 16
from 5)
==26302== Thread 7:
==26302== Syscall param socketcall.sendto(msg) points
to uninitialised byte(s)
==26302== at 0x1307D751: send (in
/lib64/libpthread-2.3.5.so)
==26302== by 0x1D187771: socket_write (tcpip.mx:236)
==26302== by 0x1D1893FC: TCPexport (tcpip.mx:1520)
==26302== by 0x1D18AF4E: conn_waiter (tcpip.mx:849)
==26302== by 0x1307897B: start_thread (in
/lib64/libpthread-2.3.5.so)
==26302== by 0x1357992D: clone (in /lib64/libc-2.3.5.so)
==26302== Address 0x207BB044 is 20 bytes inside a
block of size 1600008 alloc'd
==26302== at 0x11B1FE96: malloc
(vg_replace_malloc.c:149)
==26302== by 0x129DA289: GDKmallocmax
(gdk_utils.mx:1056)
==26302== by 0x12986560: HEAPalloc (gdk_heap.mx:125)
==26302== by 0x129FBB90: BATnewstorage (gdk_bat.mx:206)
==26302== by 0x129FBE75: BATnew (gdk_bat.mx:250)
==26302== by 0x129FBFE3: batcopy (gdk_bat.mx:540)
==26302== by 0x12A034A7: BATcopy (gdk_bat.mx:618)
==26302== by 0x11DC451B: CMDcopy (algebra.mx:1753)
==26302== by 0x11DBE08A: CMDcopy_unpack6720415
(algebra.glue.c:928)
==26302== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26302== by 0x11C45813: interpret_assignment
(monet_interpreter.mx:1767)
==26302== by 0x11C45B7C: interpret_var
(monet_interpreter.mx:1324)
## Comment 4683
Date: 2006-01-15 17:11:50 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Please check severity
## Comment 4684
Date: 2006-01-15 21:07:08 +0100
From: @peterboncz
Logged In: YES
user_id=591107
sorry, but this is a warning about the system libraries
## Comment 4685
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1386435 at http://sourceforge.net/support/tracker.php?aid=1386435
| Mserver: Valgrind detected error 4 | https://api.github.com/repos/MonetDB/MonetDB/issues/807/comments | 0 | 2020-11-30T08:59:59Z | 2024-06-28T07:36:45Z | https://github.com/MonetDB/MonetDB/issues/807 | 753,289,405 | 807 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-20 08:14:57 +0100
From: @mlkersten
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-01-15 09:06:01 +0100
## Comment 4676
Date: 2005-12-20 20:14:57 +0100
From: @mlkersten
./BugsViaSourgeforce/Tests/making_void-void_BAT_appendable.SF-1340615.valgrind.out:==25588==
ERROR SUMMARY: 6 errors from 3 contexts (suppressed: 10
from 5)
==26285== Source and destination overlap in
memcpy(0x1CFC2420, 0x1CFC2420, 80)
==26285== at 0x11B21E72: memcpy
(mac_replace_strmem.c:394)
==26285== by 0x1297C47E: VIEWreset (gdk_align.mx:575)
==26285== by 0x12A03329: BATsetaccess (gdk_bat.mx:1819)
==26285== by 0x1202E9FD: CMDsetaccess (bat.mx:1174)
==26285== by 0x1202C7EE:
CMDsetaccess_unpack692827713 (bat.glue.c:1649)
==26285== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26285== by 0x11C45813: interpret_assignment
(monet_interpreter.mx:1767)
==26285== by 0x11C3CA91: interpret
(monet_interpreter.mx:759)
==26285== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26285== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26285== by 0x11C47399: interpret_str
(monet_interpreter.mx:245)
==26285== by 0x11C47695: interpret_file
(monet_interpreter.mx:290)
==26285==
==26285== Source and destination overlap in
memcpy(0x1CFC2370, 0x1CFC2370, 72)
==26285== at 0x11B21E72: memcpy
(mac_replace_strmem.c:394)
==26285== by 0x1297C4BE: VIEWreset (gdk_align.mx:577)
==26285== by 0x12A03329: BATsetaccess (gdk_bat.mx:1819)
==26285== by 0x1202E9FD: CMDsetaccess (bat.mx:1174)
==26285== by 0x1202C7EE:
CMDsetaccess_unpack692827713 (bat.glue.c:1649)
==26285== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26285== by 0x11C45813: interpret_assignment
(monet_interpreter.mx:1767)
==26285== by 0x11C3CA91: interpret
(monet_interpreter.mx:759)
==26285== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26285== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26285== by 0x11C47399: interpret_str
(monet_interpreter.mx:245)
==26285== by 0x11C47695: interpret_file
(monet_interpreter.mx:290)
==26285==
==26285== Source and destination overlap in
memcpy(0x1CFC23B8, 0x1CFC23B8, 72)
==26285== at 0x11B21E72: memcpy
(mac_replace_strmem.c:394)
==26285== by 0x1297C4CF: VIEWreset (gdk_align.mx:578)
==26285== by 0x12A03329: BATsetaccess (gdk_bat.mx:1819)
==26285== by 0x1202E9FD: CMDsetaccess (bat.mx:1174)
==26285== by 0x1202C7EE:
CMDsetaccess_unpack692827713 (bat.glue.c:1649)
==26285== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26285== by 0x11C45813: interpret_assignment
(monet_interpreter.mx:1767)
==26285== by 0x11C3CA91: interpret
(monet_interpreter.mx:759)
==26285== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26285== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26285== by 0x11C47399: interpret_str
(monet_interpreter.mx:245)
==26285== by 0x11C47695: interpret_file
(monet_interpreter.mx:290)
## Comment 4677
Date: 2005-12-31 17:50:51 +0100
From: @drstmane
Logged In: YES
user_id=572415
Not checked/analyzed, yet.
Might be related to the [void,void]-BAT bugs:
1385067 "bug appending to [void,void] bat"
https://sourceforge.net/tracker/index.php?func=detail&aid=1385067&group_id=56967&atid=482468
1353017 "access(BAT_WRITE) on a void|void bat crashes Mserver"
https://sourceforge.net/tracker/index.php?func=detail&aid=1353017&group_id=56967&atid=482468
1334536 "data changes by appending/inserting void|void bats"
https://sourceforge.net/tracker/index.php?func=detail&aid=1334536&group_id=56967&atid=482468
## Comment 4678
Date: 2006-01-01 18:03:07 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Unfortunately, the patches do not solve the volgrind problems.
Visit http://monetdb.cwi.nl/ for further information.
-----------------
t h name
void void type
-----------------
[ 0@0, 0@0 ]
[ 1 ]
==18229== Source and destination overlap in
memcpy(0x1CFBD0A0, 0x1CFBD0A0, 80)
==18229== at 0x11B21E72: memcpy (mac_replace_strmem.c:394)
==18229== by 0x1297E12C: VIEWreset (gdk_align.mx:576)
==18229== by 0x12A054F9: BATsetaccess (gdk_bat.mx:1797)
==18229== by 0x120301AD: CMDsetaccess (bat.mx:1174)
==18229== by 0x1202DE3E: CMDsetaccess_unpack1234616031
(bat.glue.c:1649)
==18229== by 0x11C3D829: interpret
(monet_interpreter.mx:1169)
==18229== by 0x11C45873: interpret_assignment
(monet_interpreter.mx:1767)
==18229== by 0x11C3CB01: interpret (monet_interpreter.mx:759)
==18229== by 0x11C454FE: interpret_seqblock
(monet_interpreter.mx:1817)
==18229== by 0x11C3CB69: interpret (monet_interpreter.mx:766)
==18229== by 0x11C473F9: interpret_str
(monet_interpreter.mx:245)
==18229== by 0x11C476F5: interpret_file
(monet_interpreter.mx:290)
==18229==
==18229== Source and destination overlap in
memcpy(0x1CFBCFF0, 0x1CFBCFF0, 72)
==18229== at 0x11B21E72: memcpy (mac_replace_strmem.c:394)
==18229== by 0x1297E16C: VIEWreset (gdk_align.mx:578)
==18229== by 0x12A054F9: BATsetaccess (gdk_bat.mx:1797)
==18229== by 0x120301AD: CMDsetaccess (bat.mx:1174)
==18229== by 0x1202DE3E: CMDsetaccess_unpack1234616031
(bat.glue.c:1649)
==18229== by 0x11C3D829: interpret
(monet_interpreter.mx:1169)
==18229== by 0x11C45873: interpret_assignment
(monet_interpreter.mx:1767)
==18229== by 0x11C3CB01: interpret (monet_interpreter.mx:759)
==18229== by 0x11C454FE: interpret_seqblock
(monet_interpreter.mx:1817)
==18229== by 0x11C3CB69: interpret (monet_interpreter.mx:766)
==18229== by 0x11C473F9: interpret_str
(monet_interpreter.mx:245)
==18229== by 0x11C476F5: interpret_file
(monet_interpreter.mx:290)
==18229==
==18229== Source and destination overlap in
memcpy(0x1CFBD038, 0x1CFBD038, 72)
==18229== at 0x11B21E72: memcpy (mac_replace_strmem.c:394)
==18229== by 0x1297E17D: VIEWreset (gdk_align.mx:579)
==18229== by 0x12A054F9: BATsetaccess (gdk_bat.mx:1797)
==18229== by 0x120301AD: CMDsetaccess (bat.mx:1174)
==18229== by 0x1202DE3E: CMDsetaccess_unpack1234616031
(bat.glue.c:1649)
==18229== by 0x11C3D829: interpret
(monet_interpreter.mx:1169)
==18229== by 0x11C45873: interpret_assignment
(monet_interpreter.mx:1767)
==18229== by 0x11C3CB01: interpret (monet_interpreter.mx:759)
==18229== by 0x11C454FE: interpret_seqblock
(monet_interpreter.mx:1817)
==18229== by 0x11C3CB69: interpret (monet_interpreter.mx:766)
==18229== by 0x11C473F9: interpret_str
(monet_interpreter.mx:245)
==18229== by 0x11C476F5: interpret_file
(monet_interpreter.mx:290)
## Comment 4679
Date: 2006-01-15 17:14:52 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Check logic of code. If we overwrite the target with
itself here there is room for improvement.
## Comment 4680
Date: 2006-01-15 21:05:43 +0100
From: @peterboncz
Logged In: YES
user_id=591107
took 5 minutes: ATOMput does memcpy for voids (with size 0)
avoided at the cost of another if
## Comment 4681
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1386429 at http://sourceforge.net/support/tracker.php?aid=1386429
| Mserver: Valgrind detected error 3 | https://api.github.com/repos/MonetDB/MonetDB/issues/806/comments | 0 | 2020-11-30T08:59:56Z | 2024-06-27T11:08:07Z | https://github.com/MonetDB/MonetDB/issues/806 | 753,289,366 | 806 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-20 08:12:46 +0100
From: @mlkersten
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-01-01 05:59:16 +0100
## Comment 4672
Date: 2005-12-20 20:12:46 +0100
From: @mlkersten
ANother example of a serious error
./suite_01/Tests/test_40.valgrind.out:==24900== ERROR
SUMMARY: 5 errors from 3 contexts (suppressed: 16 from 5)
==26264== Invalid read of size 1
==26264== at 0x1D29005D: insert_line (ascii_io.mx:694)
==26264== by 0x1D2906B4: ASCIIload_file
(ascii_io.mx:924)
==26264== by 0x1D290AB7: ASCIIinput (ascii_io.mx:1094)
==26264== by 0x1D290C26: ASCIIload (ascii_io.mx:1078)
==26264== by 0x1D290C7A: ascii_io_load
(ascii_io.mx:1180)
==26264== by 0x1D28E291:
ascii_io_load_unpack66974523 (ascii_io.glue.c:66)
==26264== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26264== by 0x11C45813: interpret_assignment
(monet_interpreter.mx:1767)
==26264== by 0x11C45B7C: interpret_var
(monet_interpreter.mx:1324)
==26264== by 0x11C3CD08: interpret
(monet_interpreter.mx:828)
==26264== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26264== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26264== Address 0x1D39302F is 1 bytes before a block
of size 1048577 alloc'd
==26264== at 0x11B1FE96: malloc
(vg_replace_malloc.c:149)
==26264== by 0x12E6BA5E: bstream_create (stream.mx:2483)
==26264== by 0x1D290C0C: ASCIIload (ascii_io.mx:1078)
==26264== by 0x1D290C7A: ascii_io_load
(ascii_io.mx:1180)
==26264== by 0x1D28E291:
ascii_io_load_unpack66974523 (ascii_io.glue.c:66)
==26264== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26264== by 0x11C45813: interpret_assignment
(monet_interpreter.mx:1767)
==26264== by 0x11C45B7C: interpret_var
(monet_interpreter.mx:1324)
==26264== by 0x11C3CD08: interpret
(monet_interpreter.mx:828)
==26264== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26264== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26264== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26264==
==26264== Invalid read of size 8
==26264== at 0x12A2F991: batfetchjoin (gdk_relop.mx:800)
==26264== by 0x12A3F2E3: batjoin (gdk_relop.mx:1074)
==26264== by 0x12A3F82A: BATjoin (gdk_relop.mx:1107)
==26264== by 0x11DC465D: CMDjoin (algebra.mx:1772)
==26264== by 0x11DBFCC6: CMDjoin_unpack697001
(algebra.glue.c:1695)
==26264== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26264== by 0x11C3CC43: interpret
(monet_interpreter.mx:819)
==26264== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26264== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26264== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26264== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26264== by 0x11C3C68A: interpret
(monet_interpreter.mx:1155)
==26264== Address 0x1D493324 is 108 bytes inside a
block of size 112 alloc'd
==26264== at 0x11B1FE96: malloc
(vg_replace_malloc.c:149)
==26264== by 0x129DA289: GDKmallocmax
(gdk_utils.mx:1056)
==26264== by 0x129DA464: GDKmalloc (gdk_utils.mx:1077)
==26264== by 0x1297F1AE: BBPcacheit (gdk_bbp.mx:989)
==26264== by 0x129FBC1E: BATnewstorage (gdk_bat.mx:229)
==26264== by 0x129FBE75: BATnew (gdk_bat.mx:250)
==26264== by 0x1D28E72C: void_bat_create
(ascii_io.mx:319)
==26264== by 0x1D28EA42: ASCIIcreate_bats
(ascii_io.mx:543)
==26264== by 0x1D290A9D: ASCIIinput (ascii_io.mx:1093)
==26264== by 0x1D290C26: ASCIIload (ascii_io.mx:1078)
==26264== by 0x1D290C7A: ascii_io_load
(ascii_io.mx:1180)
==26264== by 0x1D28E291:
ascii_io_load_unpack66974523 (ascii_io.glue.c:66)
==26264==
==26264== Invalid read of size 8
==26264== at 0x12A2F9E7: batfetchjoin (gdk_relop.mx:801)
==26264== by 0x12A3F2E3: batjoin (gdk_relop.mx:1074)
==26264== by 0x12A3F82A: BATjoin (gdk_relop.mx:1107)
==26264== by 0x11DC465D: CMDjoin (algebra.mx:1772)
==26264== by 0x11DBFCC6: CMDjoin_unpack697001
(algebra.glue.c:1695)
==26264== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==26264== by 0x11C3CC43: interpret
(monet_interpreter.mx:819)
==26264== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26264== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26264== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==26264== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==26264== by 0x11C3C68A: interpret
(monet_interpreter.mx:1155)
==26264== Address 0x1D493324 is 108 bytes inside a
block of size 112 alloc'd
==26264== at 0x11B1FE96: malloc
(vg_replace_malloc.c:149)
==26264== by 0x129DA289: GDKmallocmax
(gdk_utils.mx:1056)
==26264== by 0x129DA464: GDKmalloc (gdk_utils.mx:1077)
==26264== by 0x1297F1AE: BBPcacheit (gdk_bbp.mx:989)
==26264== by 0x129FBC1E: BATnewstorage (gdk_bat.mx:229)
==26264== by 0x129FBE75: BATnew (gdk_bat.mx:250)
==26264== by 0x1D28E72C: void_bat_create
(ascii_io.mx:319)
==26264== by 0x1D28EA42: ASCIIcreate_bats
(ascii_io.mx:543)
==26264== by 0x1D290A9D: ASCIIinput (ascii_io.mx:1093)
==26264== by 0x1D290C26: ASCIIload (ascii_io.mx:1078)
==26264== by 0x1D290C7A: ascii_io_load
(ascii_io.mx:1180)
==26264== by 0x1D28E291:
ascii_io_load_unpack66974523 (ascii_io.glue.c:66)
## Comment 4673
Date: 2005-12-31 17:51:01 +0100
From: @drstmane
Logged In: YES
user_id=572415
The "Invalid read of size 1" was most probably cause by the
following code in ascii_io.mx:
s = line;
[...]
&& *(line - 1) != '\\')
I fixed it as follows:
&& (line == s || *(line - 1) != '\\'))
Martin,
could you please check, whether valgrind is now "satisfied"?
## Comment 4674
Date: 2006-01-01 17:59:16 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Valgrind does not report any error anymore.
Consider bug as closed.
## Comment 4675
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1386425 at http://sourceforge.net/support/tracker.php?aid=1386425
| Mserver: Valgrind detected error 2 | https://api.github.com/repos/MonetDB/MonetDB/issues/805/comments | 0 | 2020-11-30T08:59:53Z | 2024-06-27T11:08:06Z | https://github.com/MonetDB/MonetDB/issues/805 | 753,289,320 | 805 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-20 08:08:21 +0100
From: @mlkersten
To: MonetDB4 devs <<bugs-monetdb4>>
Version: -- development
Last updated: 2006-01-01 05:57:20 +0100
## Comment 4667
Date: 2005-12-20 20:08:21 +0100
From: @mlkersten
Running valgrind against the milS/milM jobs without
any other constraints leads to the following error
tests/BugReports/Tests> vi no.031.valgrind.out
==25244== Memcheck, a memory error detector.
==25244== Copyright (C) 2002-2005, and GNU GPL'd, by
Julian Seward et al.
==25244== Using LibVEX rev 1367, a library for dynamic
binary translation.
==25244== Copyright (C) 2004-2005, and GNU GPL'd, by
OpenWorks LLP.
==25244== Using valgrind-3.0.1, a dynamic binary
instrumentation framework.
==25244== Copyright (C) 2000-2005, and GNU GPL'd, by
Julian Seward et al.
==25244== For more details, rerun with: -v
==25244==
==25244== Invalid read of size 8
==25244== at 0x12A2F991: batfetchjoin (gdk_relop.mx:800)
==25244== by 0x12A3F2E3: batjoin (gdk_relop.mx:1074)
==25244== by 0x12A3F82A: BATjoin (gdk_relop.mx:1107)
==25244== by 0x11DC465D: CMDjoin (algebra.mx:1772)
==25244== by 0x11DBFCC6: CMDjoin_unpack697001
(algebra.glue.c:1695)
==25244== by 0x11C3D7C4: interpret
(monet_interpreter.mx:1169)
==25244== by 0x11C3CC43: interpret
(monet_interpreter.mx:819)
==25244== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==25244== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==25244== by 0x11C45491: interpret_seqblock
(monet_interpreter.mx:1817)
==25244== by 0x11C3CAF9: interpret
(monet_interpreter.mx:766)
==25244== by 0x11C3C68A: interpret
(monet_interpreter.mx:1155)
==25244== Address 0x1D0B0AF4 is 108 bytes inside a
block of size 112 alloc'd
==25244== at 0x11B1FE96: malloc
(vg_replace_malloc.c:149)
==25244== by 0x129DA289: GDKmallocmax
(gdk_utils.mx:1056)
==25244== by 0x129DA464: GDKmalloc (gdk_utils.mx:1077)
==25244== by 0x1297F1AE: BBPcacheit (gdk_bbp.mx:989)
==25244== by 0x129FBC1E: BATnewstorage (gdk_bat.mx:229)
==25244== by 0x129FBE75: BATnew (gdk_bat.mx:250)
==25244== by 0x1D28E72C: void_bat_create
(ascii_io.mx:319)
==25244== by 0x1D28EA42: ASCIIcreate_bats
(ascii_io.mx:543)
==25244== by 0x1D290A9D: ASCIIinput (ascii_io.mx:1093)
==25244== by 0x1D290C26: ASCIIload (ascii_io.mx:1078)
==25244== by 0x1D290C7A: ascii_io_load
(ascii_io.mx:1180)
==25244== by 0x1D28E291:
ascii_io_load_unpack66974523 (ascii_io.glue.c:66)
==25244==
## Comment 4668
Date: 2005-12-21 10:59:05 +0100
From: @drstmane
Logged In: YES
user_id=572415
Martin,
could you please give the exact commandline you used to run
the valgrind tests?
This would make it much easier to rerun the test the same
way you ran it.
Thanks in advance,
Stefan
## Comment 4669
Date: 2005-12-31 17:51:09 +0100
From: @drstmane
Logged In: YES
user_id=572415
Martin,
did you run the valgrind test(s) with a 64-bit Mserver with
32-bit OIDs?
Then, this problem could have been caused by the fact that
(32-bit) OIDs where read as (64-bit) ssize_t in batfetchjoin.
I fixed that in my latest check-in; could you please check,
whether it fixes this valgrind bug, and also the others that
report an "Invalid read of size 8" in "batfetchjoin
(gdk_relop.mx:800)"?
## Comment 4670
Date: 2006-01-01 17:57:20 +0100
From: @mlkersten
Logged In: YES
user_id=490798
The current system version does not generate this error
any more. The test is closed.
## Comment 4671
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1386420 at http://sourceforge.net/support/tracker.php?aid=1386420
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-monetdb4@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| Mserver: Valgrind detected error | https://api.github.com/repos/MonetDB/MonetDB/issues/804/comments | 0 | 2020-11-30T08:59:49Z | 2024-06-27T11:08:05Z | https://github.com/MonetDB/MonetDB/issues/804 | 753,289,267 | 804 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-19 04:32:11 +0100
From: @yzchang
To: @njnes
Version: -- development
Last updated: 2006-01-19 08:10:20 +0100
## Comment 4659
Date: 2005-12-19 16:32:11 +0100
From: @yzchang
start Mserver with the following options:
Mserver --dbinit="module(sql_server, mapi);
sql_server_start(); mapi_start();"
Then start 'MapiClient -ls' and it directly with '\q'.
Mserver will fail with the following message:
$Mserver --dbinit="module(sql_server, mapi);
sql_server_start();
mapi_start();"
Monet Database Server V4.9.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs;
dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>Mserver: ../../../src/monet/monet_tbl.mx:1706:
TBL_M_decref:
Assertion `p' failed.
Aborted
Note that the order in which the modules are given
matters => the assertion only fails if 'mapi' is given
after 'sql_server' in the same call to 'module'. For
example, the following commands won't cause the
assertion fail:
$Mserver --dbinit="module(sql_server); module(mapi);
sql_server_start(); mapi_start();"
$Mserver --dbinit="module(mapi, sql_server);
mapi_start(); sql_server_start();"
(According to Fabian:) It seems that the module "mapi"
is incorrectly loaded twice, if we call module this
way: module(sql_server, mapi);
This bug is related with http://sourceforge.net/support/tracker.php?aid=852098 "Mserver segfault
with module sql_server"
## Comment 4660
Date: 2005-12-20 00:09:37 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / REDUNDANT:
most probably related to
1385152 "start/exit MapiClient with three servers causes
assertion"
(http://sourceforge.net/tracker/index.php?func=detail&aid=1385152&group_id=56967&atid=482468)
## Comment 4661
Date: 2006-01-09 10:52:23 +0100
From: @drstmane
Logged In: YES
user_id=572415
Most probably also related to
1400200 "Mserver: module-order does matter"
https://sourceforge.net/tracker/index.php?func=detail&aid=1400200&group_id=56967&atid=482468
## Comment 4662
Date: 2006-01-15 03:06:38 +0100
From: @drstmane
Logged In: YES
user_id=572415
Most probably also related to
1254041 "server crashes when multiple modules are supplied"
https://sourceforge.net/tracker/index.php?func=detail&aid=1254041&group_id=56967&atid=482468
## Comment 4663
Date: 2006-01-16 00:17:24 +0100
From: @drstmane
Logged In: YES
user_id=572415
added extended test script in
sql/src/test/BugDay_2005-12-19_0.9.3/Tests/multiple_servers_2.SF-1385247.*
The test starts Mserver, loads modules "mapi" &
"sql_server", and calls "mapi_start()" &
"sql_server_start()" in different orders:
"module(mapi,sql_server); mapi_start(); sql_server_start();"
"module(mapi,sql_server); sql_server_start(); mapi_start();"
"module(sql_server,mapi); mapi_start(); sql_server_start();"
"module(sql_server,mapi); sql_server_start(); mapi_start();"
In each of the 4 cases, 2 MIL- and 2 SQL-clients (try to)
connect in all 6 possible orders.
The tests reveal, that everything works fine, if we first
load module "mapi" and then module "sql_server", no matter
in which order we call "mapi_start()" & "sql_server_start()"
and/or in which order the clients connect.
When module "sql_server" is loaded before module "mapi",
however, the first client connection, no matter whether MIL
or SQL, crashes the Mserver with
Mserver:
/ufs/manegold/_/scratch0/Monet/Testing/Current/MonetDB/src/monet/monet_tbl.mx:1706:
TBL_M_decref: Assertion `p' failed.
no matter in which order we call "mapi_start()" &
"sql_server_start()".
This is even "worse" than the respetive test for MIL +
XQUERY reveals, cf.:
https://sourceforge.net/tracker/index.php?func=detail&aid=1385152&group_id=56967&atid=482468
Hope this helps to locate and eventually fix the bug(s).
## Comment 4664
Date: 2006-01-18 19:32:05 +0100
From: @drstmane
Logged In: YES
user_id=572415
Fixed by Niels'
"
too many bugs related to module(x,y,z) so we simply remove
this feature
ie use module(x);module(y);module(z); instead.
".
To be closed tomorrow, once confirmed by the test web; cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d-Fedora4/src_test_BugDay_2005-12-19_2.9.3/multiple_servers_2.SF-1385247.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d-Fedora4/src_test_BugDay_2005-12-19_2.9.3/multiple_servers_2.SF-1385247.err.00.html
## Comment 4665
Date: 2006-01-19 08:10:18 +0100
From: @drstmane
Logged In: YES
user_id=572415
TestWeb confirmed the fix. Closed.
## Comment 4666
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1385247 at http://sourceforge.net/support/tracker.php?aid=1385247
| Mserver assertion failed with "module(sql_server, mapi);" | https://api.github.com/repos/MonetDB/MonetDB/issues/803/comments | 0 | 2020-11-30T08:59:46Z | 2024-06-27T11:08:04Z | https://github.com/MonetDB/MonetDB/issues/803 | 753,289,236 | 803 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-19 02:12:15 +0100
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2006-01-19 08:15:29 +0100
## Comment 4649
Date: 2005-12-19 14:12:15 +0100
From: @sjoerdmullender
In one window start
Mserver --dbinit 'module(sql_server,pathfinder,mapi);
sql_server_start(); pfstart(); mapi_start();'
In another window start
MapiClient
Immediately exit MapiClient and observe
Mserver: .../src/monet/monet_tbl.mx:1706: TBL_M_decref:
Assertion `p' failed.
Aborted
in first window.
## Comment 4650
Date: 2005-12-20 00:06:11 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/multiple_servers.SF-1385152.py
## Comment 4651
Date: 2005-12-20 00:09:30 +0100
From: @drstmane
Logged In: YES
user_id=572415
most probably related to
1385247: Mserver assertion failed with "module(sql_server,
mapi);"
(http://sourceforge.net/tracker/index.php?func=detail&aid=1385247&group_id=56967&atid=482468)
## Comment 4652
Date: 2006-01-09 10:52:27 +0100
From: @drstmane
Logged In: YES
user_id=572415
Most probably also related to
1400200 "Mserver: module-order does matter"
https://sourceforge.net/tracker/index.php?func=detail&aid=1400200&group_id=56967&atid=482468
## Comment 4653
Date: 2006-01-15 03:06:29 +0100
From: @drstmane
Logged In: YES
user_id=572415
Most probably also related to
1254041 "server crashes when multiple modules are supplied"
https://sourceforge.net/tracker/index.php?func=detail&aid=1254041&group_id=56967&atid=482468
## Comment 4654
Date: 2006-01-15 17:18:08 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Niels, could you have a look at this one.
## Comment 4655
Date: 2006-01-16 00:17:41 +0100
From: @drstmane
Logged In: YES
user_id=572415
added extended test script in
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/multiple_servers_2.SF-1385152.*
The test starts Mserver, loads modules "mapi" &
"pathfinder", and calls "mapi_start()" & "pfstart()" in
different orders:
"module(mapi,pathfinder); mapi_start(); pfstart();"
"module(mapi,pathfinder); pfstart(); mapi_start();"
"module(pathfinder,mapi); mapi_start(); pfstart();"
"module(pathfinder,mapi); pfstart(); mapi_start();"
In each of the 4 cases, 2 MIL- and 2 XQUERY-clients (try to)
connect in all 6 possible orders.
The tests reveal, that everything works fine, if we first
load module "mapi" and then module "pathfinder", no matter
in which order we call "mapi_start()" & "pfstart()" and/or
in which order the clients connect.
When module "pathfinder" is loaded before module "mapi",
anything before the first MIL-client connection works fine,
too, however, the first MIL-client connection crashes the
Mserver with
Mserver:
/ufs/manegold/_/scratch0/Monet/Testing/Current/MonetDB/src/monet/monet_tbl.mx:1706:
TBL_M_decref: Assertion `p' failed.
no matter in which order we call "mapi_start()" & "pfstart()".
With the respective test for MIL + SQL, the situation is
even "worse", cf.:
https://sourceforge.net/tracker/index.php?func=detail&aid=1385247&group_id=56967&atid=482468
Hope this helps to locate and eventually fix the bug(s).
## Comment 4656
Date: 2006-01-18 19:37:58 +0100
From: @drstmane
Logged In: YES
user_id=572415
Fixed by Niels'
"
too many bugs related to module(x,y,z) so we simply remove
this feature
ie use module(x);module(y);module(z); instead.
".
To be closed tomorrow, once confirmed by the test web; cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/multiple_servers_2.SF-1385152.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/multiple_servers_2.SF-1385152.err.00.html
## Comment 4657
Date: 2006-01-19 08:15:29 +0100
From: @drstmane
Logged In: YES
user_id=572415
TestWeb confirmed the fix. Closed.
## Comment 4658
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1385152 at http://sourceforge.net/support/tracker.php?aid=1385152
| start/exit MapiClient with three servers causes assertion | https://api.github.com/repos/MonetDB/MonetDB/issues/802/comments | 0 | 2020-11-30T08:59:42Z | 2024-06-27T11:08:03Z | https://github.com/MonetDB/MonetDB/issues/802 | 753,289,190 | 802 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-19 11:33:49 +0100
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2006-01-18 09:44:52 +0100
## Comment 4644
Date: 2005-12-19 11:33:49 +0100
From: @sjoerdmullender
This bug may be related to http://sourceforge.net/support/tracker.php?aid=1334536.
It is a bug that after the append a only has a single
row and that the head is nil.
I would have hoped for a void-headed bat as result with
two rows.
MonetDB>var a :=
new(void,void).insert(nil,nil).seqbase(1@0).reverse().seqbase(0@0);
MonetDB>a.print();
-----------------
t h name
void void type
-----------------
[ 0@0, 1@0 ]
MonetDB>var b := new(oid,oid).insert(1@0,1@0);
MonetDB>b.print();
-----------------
h t name
oid oid type
-----------------
[ 1@0, 1@0 ]
MonetDB>a.append(b);
MonetDB>a.print();
-----------------
t h name
oid oid type
-----------------
[ nil, 1@0 ]
MonetDB>
## Comment 4645
Date: 2005-12-20 00:06:07 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
MonetDB/tests/BugsViaSourgeforce/Tests/append_empty_oid_bat.SF-1334536.milS
## Comment 4646
Date: 2005-12-20 17:00:08 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
There seem to be two problems:
1. (fixed) because a is a [void,void] bat, it gets
materialized. BATmaterialize contained an error when
materializing non-empty [void,void] bats and returned an
empty [oid,oid] bat. This is fixed in revision 1.65 of
gdk_align.mx.
2. at least in certain cases when appending to an oid-headed
bat, nils are inserted as the head value, apparently in the
hope that they get assigned proper oid values in the
process, but this isn't happening.
## Comment 4647
Date: 2006-01-18 09:44:52 +0100
From: @drstmane
Logged In: YES
user_id=572415
Fixed by Niels void semantic fixes in CVS.
## Comment 4648
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1385067 at http://sourceforge.net/support/tracker.php?aid=1385067
| bug appending to [void,void] bat | https://api.github.com/repos/MonetDB/MonetDB/issues/801/comments | 0 | 2020-11-30T08:59:38Z | 2024-06-27T11:08:02Z | https://github.com/MonetDB/MonetDB/issues/801 | 753,289,147 | 801 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-14 11:10:41 +0100
From: thomaz <<tmensink>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-12-14 02:18:45 +0100
## Comment 4637
Date: 2005-12-14 11:10:41 +0100
From: thomaz <<tmensink>>
When using the following INSERT INTO command
INSERT INTO s4_kwm SELECT kwmTemp.urlId,kwmTemp.kwid
FROM kwmTemp WHERE NOT EXISTS(
SELECT * FROM s4_kwm AS kwm
WHERE kwm.kwid = kwmTemp.kwid
AND kwm.urlid = kwmTemp.urlid
);
The s4_kwm table keeps empty.
When executing only the SELECT statement
SELECT kwmTemp.urlId,kwmTemp.kwid
FROM kwmTemp WHERE NOT EXISTS(
SELECT * FROM s4_kwm AS kwm
WHERE kwm.kwid = kwmTemp.kwid
AND kwm.urlid = kwmTemp.urlid
);
All elements are returned which should be inserted into
s4_kwm.
So somewhere the links is missing.
I added a SQL file, which does such a query two times,
the first time (with a slightly different SELECT part)
Inserts correctly. The second part however, does not
insert any thing, as reported above.
## Comment 4638
Date: 2005-12-14 11:33:44 +0100
From: @grobian
Logged In: YES
user_id=963970
did you check the script whether it works? IMHO some
transaction statements are missing and is not a comment
character (-- is)
## Comment 4639
Date: 2005-12-14 13:06:40 +0100
From: thomaz <<tmensink>>
Logged In: YES
user_id=1388838
The bugreport was checked before the comments were inserterd...
But here again. The sql script is checked with the windows
MonetDBSQLCLient.
(De MonetDB version is 4.8.2, Windows XP sp2, P IV 2,4 Ghz
448MB Ram)
## Comment 4640
Date: 2005-12-14 14:18:45 +0100
From: @grobian
Logged In: YES
user_id=963970
This bug appears to be fixed in the current development version
## Comment 4641
Date: 2005-12-14 14:45:13 +0100
From: @grobian
Logged In: YES
user_id=963970
added script as
sql/src/test/BugTracker/insert_not_exists.SF-1380287.*
## Comment 4642
Date: 2005-12-20 14:33:27 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-12-19, sjoerd: ALREADY IN TESTWEB
sql/src/test/BugTracker/Tests/insert_not_exists.SF-1380287.sql
## Comment 4643
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1380287 at http://sourceforge.net/support/tracker.php?aid=1380287
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.
| INSERT INTO failure | https://api.github.com/repos/MonetDB/MonetDB/issues/800/comments | 0 | 2020-11-30T08:59:36Z | 2024-06-28T07:36:44Z | https://github.com/MonetDB/MonetDB/issues/800 | 753,289,123 | 800 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-12 06:28:42 +0100
From: thomaz <<tmensink>>
To: @njnes
Version: -- development
Last updated: 2005-12-12 08:37:17 +0100
## Comment 4633
Date: 2005-12-12 18:28:42 +0100
From: thomaz <<tmensink>>
We tried to update the value of a table column, with a
value from another table.
Using the following UPDATE SQL syntax:
UPDATE t1 SET id =
(SELECT t2.idNew FROM t2 WHERE t1.id= t2.id)
WHERE url='value';
MySQL returns the following error:
Error: ERROR: interpret: unknown variable 's11'.
ERROR: interpret_params: join(param 2): evaluation error.
There is probably something wrong with the SQL->MIL
translation.
We are using MonetDB version: 4.8.2
SQL client: JDBC driver
Windows XP, Pentium IV 2.4 Ghz, 448MB Ram
-----
SQL commands to create test tables + values
CREATE TABLE t1 (id int, url string);
INSERT INTO t1 VALUES(1,'value');
CREATE TABLE t2 (id int, idNew int);
INSERT INTO t2 VALUES(1,2);
requested output should be
t1 => id:2, url:'value'
## Comment 4634
Date: 2005-12-12 20:37:17 +0100
From: @njnes
Logged In: YES
user_id=43556
Bug has been fixed in the main branch.
Test exist for it in
src/test/BugTracker/Tests/update_with_subselect.SF-1362771.sql
## Comment 4635
Date: 2005-12-20 14:32:34 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-12-19, sjoerd: NO TEST / REDUNDANT
sql/src/test/BugTracker/Tests/update_with_subselect.SF-1362771.sql
## Comment 4636
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1378884 at http://sourceforge.net/support/tracker.php?aid=1378884
| UPDATE evaluation error | https://api.github.com/repos/MonetDB/MonetDB/issues/799/comments | 0 | 2020-11-30T08:59:33Z | 2024-06-27T11:08:00Z | https://github.com/MonetDB/MonetDB/issues/799 | 753,289,091 | 799 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-12 03:04:57 +0100
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2006-01-18 11:42:32 +0100
## Comment 4622
Date: 2005-12-12 15:04:57 +0100
From: Wouter Alink <<alink>>
Given the query:
doc("bug.xml")//volume union
doc("bug.xml")//data[not(.//volume)]
and bug.xml being:
<d>
<data>
<container>
<volume/>
<volume/>
</container>
</data>
</d>
results in:
ERROR: interpret: no matching MIL operator to
'reverse(oid)'.
## Comment 4623
Date: 2005-12-12 15:37:03 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
please rename bug to: yet another materialize() problem :)
and assign it to either Peter (who will probably not fix it
in the following weeks) or Stefan.
The problem also occurs with the following simplified query:
not(<a><b/></a>//b)
It appears because the staircase join returns a constant
iter, which is treated as bat in the following step (here
'not')...
## Comment 4624
Date: 2005-12-20 14:30:40 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-12-19, sjoerd: TEST ADDED / FAILURE
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/not_constant.SF-1378750.xq
## Comment 4625
Date: 2006-01-15 03:01:35 +0100
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS --- was indeed another materialize() problem in
fn:boolean.
could some expert please verify the new output at
http://monetdb.cwi.nl/testing/prhttp://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/not_cojects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/not_constant.SF-1378750.out.00.html
http://monetdb.cwi.nl/testing/prhttp://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/not_cojects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/not_constant_2.SF-1378750.out.00.html
as of Monday Jan 16 2006 ?
## Comment 4626
Date: 2006-01-18 09:48:18 +0100
From: @drstmane
Logged In: YES
user_id=572415
... any verdict on the correctness of the current output ?
## Comment 4627
Date: 2006-01-18 10:25:36 +0100
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Seems to me that the current output:
<volume/><volume/>
is the correct answer to the query. I think this bug can be
closed after the output has been approved. I'll do that just
now.
## Comment 4628
Date: 2006-01-18 10:34:40 +0100
From: @drstmane
Logged In: YES
user_id=572415
Sorry, another set of wrong URLs;
correct are
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/not_constant.SF-1378750.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/not_constant_2.SF-1378750.out.00.html
## Comment 4629
Date: 2006-01-18 10:43:03 +0100
From: @Teggy
Logged In: YES
user_id=642632
Hi,
the output looks OK to me.
Cheers,
--T
## Comment 4630
Date: 2006-01-18 11:07:02 +0100
From: @drstmane
Logged In: YES
user_id=572415
Wouter,
are you fixing the stable output (i.e., just remove the line
"= ? is this the correct/expected result ? ="), or shall I
do it?
Stefan
## Comment 4631
Date: 2006-01-18 11:42:32 +0100
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Done
## Comment 4632
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1378750 at http://sourceforge.net/support/tracker.php?aid=1378750
| XQuery: Reversed Union | https://api.github.com/repos/MonetDB/MonetDB/issues/798/comments | 0 | 2020-11-30T08:59:29Z | 2024-06-27T11:07:59Z | https://github.com/MonetDB/MonetDB/issues/798 | 753,289,057 | 798 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-09 04:41:52 +0100
From: Steffen Goeldner <<sgoeldner>>
To: @njnes
Version: -- development
Last updated: 2005-12-12 11:53:36 +0100
## Comment 4615
Date: 2005-12-09 16:41:52 +0100
From: Steffen Goeldner <<sgoeldner>>
Deleting an empty table returns rows_affected == 1:
use MapiLib;
my $mapi = MapiLib::mapi_connect
('localhost',45123,'monetdb','monetdb','sql');
MapiLib::mapi_query( $mapi,'create table test( i
integer )');
my $hdl = MapiLib::mapi_query( $mapi,"delete from
test");
print MapiLib::mapi_rows_affected( $hdl );
1
## Comment 4616
Date: 2005-12-09 17:58:51 +0100
From: @grobian
Logged In: YES
user_id=963970
Driver: MonetDB Native Driver 1.2 (Blunt+ 20051209)
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 test( i integer );
Operation successful
Connection warning: TODO: maxRows ignored
monetdb-> rollback;
auto commit mode: on
monetdb->
results in under the hood response by the server:
TD 1134146957841: write final block: 32 bytes
TX 1134146957842: screate table test( i integer );
RD 1134146957844: final block: 14 bytes
RD 1134146957845: read chunk: 14 bytes, left: 0 bytes
RX 1134146957845: &3 0 1 1 1
^A^A
giving me the impression that it is not correct, since it
seems to return some bogus data. Probably Mapi returns
hardcoded on this header 1. What would you have expected to
be returned? In JDBC Q_SCHEMA (the &3) is translated into a
SUCCESS_NO_INFO number. (which is -2 for real for JDBC and
ODBC IIRC).
## Comment 4617
Date: 2005-12-09 17:59:55 +0100
From: @grobian
Logged In: YES
user_id=963970
errr... ignore my last comment.
## Comment 4618
Date: 2005-12-09 18:03:15 +0100
From: @grobian
Logged In: YES
user_id=963970
(2nd try:)
Driver: MonetDB Native Driver 1.2 (Blunt+ 20051209)
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 test( i integer );
Operation successful
Connection warning: TODO: maxRows ignored
monetdb-> delete from test;
0 affected rows
monetdb-> rollback;
auto commit mode: on
monetdb->
The relevant transmission log:
TD 1134147703258: write final block: 18 bytes
TX 1134147703258: sdelete from test;
RD 1134147703259: final block: 8 bytes
RD 1134147703259: read chunk: 8 bytes, left: 0 bytes
RX 1134147703259: &2 0
^A^A
which more or less indicates the Mapi library somehow
translates the correct value from the server into an
(incorrect) 1.
## Comment 4619
Date: 2005-12-12 23:53:36 +0100
From: @njnes
Logged In: YES
user_id=43556
Bugs is fixed in cvs head. Adding the dummy affected row
count caused an increase of row_count. Also added a test script.
## Comment 4620
Date: 2005-12-20 14:25:47 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-12-19, sjoerd: ALREADY IN TESTWEB
sql/src/test/BugTracker/Tests/rows_affected.SF-1377180.sql
## Comment 4621
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1377180 at http://sourceforge.net/support/tracker.php?aid=1377180
| Mapi: rows_affected wrong for Q_UPDATE | https://api.github.com/repos/MonetDB/MonetDB/issues/797/comments | 0 | 2020-11-30T08:59:26Z | 2024-06-27T11:07:58Z | https://github.com/MonetDB/MonetDB/issues/797 | 753,289,026 | 797 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-09 01:00:21 +0100
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2005-12-13 12:05:48 +0100
## Comment 4611
Date: 2005-12-09 13:00:21 +0100
From: @sjoerdmullender
Start Mserver --dbinit 'module(sql_server);
sql_server_start();'
In another window start MapiClient -lsql
sql>prepare select ?;
MAPI = monetdb@localhost:45123
ACTION= read_line
QUERY = prepare select ?;
ERROR = Connection terminated
In first window notice the Segmentation Fault.
## Comment 4612
Date: 2005-12-13 00:05:48 +0100
From: @njnes
Logged In: YES
user_id=43556
Fixed, checking the tail_type of an variable statement was
bogus.
## Comment 4613
Date: 2005-12-20 14:24:28 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-12-19, sjoerd: TEST ADDED / SUCCESS
sql/src/test/BugDay_2005-12-19_2.9.3/Tests/bogus_prepare.SF-1377079.sql
## Comment 4614
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1377079 at http://sourceforge.net/support/tracker.php?aid=1377079
| bogus prepare causes crash | https://api.github.com/repos/MonetDB/MonetDB/issues/796/comments | 0 | 2020-11-30T08:59:23Z | 2024-06-27T11:07:57Z | https://github.com/MonetDB/MonetDB/issues/796 | 753,288,990 | 796 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-09 11:30:46 +0100
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-01-22 08:37:17 +0100
## Comment 4607
Date: 2005-12-09 11:30:46 +0100
From: Wouter Alink <<alink>>
I don't know whether the following is a feature or a
bug, but i would expect that the print(bat("a")); would
either always or never fail directly after a destroy("a");
Try for example the following:
START MAPI SESSION:
mil>var a :=
bat(int,int).insert(0,0).persists(true).bbpname("a");
CLOSE SESSION
START NEW SESSION:
mil>print(bat("a"));
-----------------
h t name
int int type
-----------------
[ 0, 0 ]
mil>destroy("a");
mil>print(bat("a"));
MAPI = anonymous@localhost:50000
QUERY = print(bat("a"));
ERROR = !ERROR: interpret_params: print(param 1):
invalid BAT.
START MAPI SESSION:
mil>var a :=
bat(int,int).insert(0,0).persists(true).bbpname("a");
START NEW SESSION:
mil>var a := bat("a");
mil>destroy("a");
mil>print(bat("a"));
-----------------
h t name
int int type
-----------------
[ 0, 0 ]
mil>a := nil;
mil>print(bat("a"));
MAPI = anonymous@localhost:50000
QUERY = print(bat("a"));
ERROR = !ERROR: interpret_params: print(param 1):
invalid BAT.
## Comment 4608
Date: 2005-12-20 14:22:23 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-12-19, sjoerd: TEST ADDED / FAILURE
MonetDB/tests/BugDay_2005-12-19_4.9.3/Tests/print_after_destroy.SF-1377020a.milC
MonetDB/tests/BugDay_2005-12-19_4.9.3/Tests/print_after_destroy.SF-1377020b.milC
## Comment 4609
Date: 2006-01-22 20:37:17 +0100
From: @drstmane
Logged In: YES
user_id=572415
The test confirms that now also the first print right after
the destroy in the second example does result in an error as
(IMHO) expected & correct.
## Comment 4610
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1377020 at http://sourceforge.net/support/tracker.php?aid=1377020
| Mserver: destroy() immediately except if referenced | https://api.github.com/repos/MonetDB/MonetDB/issues/795/comments | 0 | 2020-11-30T08:59:20Z | 2024-06-27T11:07:56Z | https://github.com/MonetDB/MonetDB/issues/795 | 753,288,965 | 795 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-09 11:07:22 +0100
From: Wouter Alink <<alink>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-01-15 11:43:05 +0100
## Comment 4602
Date: 2005-12-09 11:07:22 +0100
From: Wouter Alink <<alink>>
when shredding documents on the fly... Mserver crashes
(this only happens the first time, afterwards all seems
fine)
for example:
create a file "/tmp/newfile.xml" with contents "<x/>"
now run the query: 'doc("/tmp/newfile.xml")/x'
Mserver will crash. after restarting Mserver, and
rerunning the query, it will successfully answer the query.
## Comment 4603
Date: 2005-12-20 14:08:40 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-12-19, sjoerd: TEST ADDED / FAILURE
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/shredding_on_the_fly.SF-1377006.XQUERY.py
## Comment 4604
Date: 2006-01-15 01:10:19 +0100
From: @drstmane
Logged In: YES
user_id=572415
This one seems to be related to (if not identical with)
1405188 "PF: shredding documents on-the-fly via fn:doc() fails"
https://sourceforge.net/tracker/index.php?func=detail&aid=1405188&group_id=56967&atid=482468
## Comment 4605
Date: 2006-01-15 11:43:05 +0100
From: @drstmane
Logged In: YES
user_id=572415
Fixed by back-porting Peter's "tentative" fix for http://sourceforge.net/support/tracker.php?aid=1405188 "PF: shredding documents on-the-fly via fn:doc() fails"
1377006 "XQuery: shredding-on-the-fly"
1204965 "XQuery: Example from W3C fails"
from the XQuery_0-9_update branch to the main trunk.
## Comment 4606
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1377006 at http://sourceforge.net/support/tracker.php?aid=1377006
| XQuery: shredding-on-the-fly | https://api.github.com/repos/MonetDB/MonetDB/issues/794/comments | 0 | 2020-11-30T08:59:17Z | 2024-06-27T11:07:55Z | https://github.com/MonetDB/MonetDB/issues/794 | 753,288,926 | 794 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-09 09:06:22 +0100
From: Wouter Alink <<alink>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2006-01-15 01:03:46 +0100
## Comment 4597
Date: 2005-12-09 09:06:22 +0100
From: Wouter Alink <<alink>>
When shredding a document with only one attribute, a
warning is generated...
test.xml:
<X Y=""/>
mil>shred_doc("/home/alink/test.xml","test.xml");
WARNING: BAT[ATTR_PROP] not dense
Shredded XML doc("test.xml"), total time after
commit=0.013s
mil>
## Comment 4598
Date: 2005-12-20 13:56:11 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-12-19, sjoerd: TEST ADDED / FAILURE
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/shredding_one_attribute.SF-1376942.milC
## Comment 4599
Date: 2006-01-14 13:50:02 +0100
From: @drstmane
Logged In: YES
user_id=572415
Gentle reminder ;-)
## Comment 4600
Date: 2006-01-15 01:03:46 +0100
From: @drstmane
Logged In: YES
user_id=572415
Turned out to be a property issue:
pf_compress() (pathfinder/runtime/shredder.mx) uses
BATins_kunique() (MonetDB/src/gdk/gdk_setop.mx) directly
(iso. via BATkunique()), but only the latter sets the key
property of the resulting head;
without the key property being set, a subsequent BATleftjoin
could not know that it could maintain the denseness of the
left head.
Hence, I decided to fix it myself by having also
BATkunique() set the key property if applicable
(cf. changes in MonetDB/src/gdk/gdk_setop.mx).
## Comment 4601
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1376942 at http://sourceforge.net/support/tracker.php?aid=1376942
| XQuery: shredding 1 attribute | https://api.github.com/repos/MonetDB/MonetDB/issues/793/comments | 0 | 2020-11-30T08:59:14Z | 2024-06-27T11:07:54Z | https://github.com/MonetDB/MonetDB/issues/793 | 753,288,895 | 793 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-06 02:58:05 +0100
From: @grobian
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2005-12-06 04:13:51 +0100
## Comment 4590
Date: 2005-12-06 14:58:05 +0100
From: @grobian
This is a wannabe bug:
conflicts: 17 shift/reduce, 8 reduce/reduce
monet_parse.y:341.22-37: warning: rule never reduced
because of conflicts: @9: /* empty */
## Comment 4591
Date: 2005-12-06 15:12:20 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Hi Fabian,
what is the problem with this warning?
afaik it has always been there..
## Comment 4592
Date: 2005-12-06 15:14:43 +0100
From: @grobian
Logged In: YES
user_id=963970
iirc the warning on the rule that is never reduced because
of conflicts, is new... May be wrong, but I thought it was
caused by the recent parser changes.
## Comment 4593
Date: 2005-12-06 17:05:59 +0100
From: @drstmane
Logged In: YES
user_id=572415
From Peter's cvs check-in message :
"
bugfix 1374485: bison warning
problem was that the rule for forward PROC definitions could not
be resolved by bison (because of the presence of a recently
introduced
C-block in the grammar rule for proc definitions, just before
the point that the LALR parser could distinguish between the
normal proc-def and forward proc-def rules).
small rewrite of the rules resolved it
"
Hence, might this even fix the problem with PROC forward
declaration in test tests/by_Peter/Tests/recursion.milM,
(cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.64.64.d-Fedora4/tests_by_Peter/recursion.out.00.html)
which I noticed only recently, but forgot to report (and
noone else ssems to have noticed it ... ;-)) ... ?
Please check the testweb tomorrow.
If it indeed also fixes this problem, then thanks to Fabian
and Peter for watching-out carefully, and acting instantly!
## Comment 4594
Date: 2005-12-07 09:22:19 +0100
From: @drstmane
Logged In: YES
user_id=572415
Indeed, the forward PROC declaration problem in
tests/by_Peter/Tests/recursion.milM seems to be fixed as well.
Thanks, again!
## Comment 4595
Date: 2005-12-20 13:51:06 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-12-19, sjoerd: NO TEST / COMPILATION
## Comment 4596
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1374485 at http://sourceforge.net/support/tracker.php?aid=1374485
| MonetDB: bison complains on never reduced rule | https://api.github.com/repos/MonetDB/MonetDB/issues/792/comments | 0 | 2020-11-30T08:59:11Z | 2024-06-27T11:07:53Z | https://github.com/MonetDB/MonetDB/issues/792 | 753,288,859 | 792 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-05 10:11:05 +0100
From: Bastiaan de Groot <<bgroot>>
To: @njnes
Version: -- development
Last updated: 2005-12-13 01:33:40 +0100
## Comment 4584
Date: 2005-12-05 10:11:05 +0100
From: Bastiaan de Groot <<bgroot>>
I have found a rather strange bug. When i create two
tables, one consisting of an integer and more than 30
longs and the other consisting of a time and more then
30 longs. I then try to perform a join on all long
values between the two tables. This join is performed
correctly in almost all cases only when the first two
longs are non-zero the third is zero and the fourth is
non-zero two records who should have been joined are
not joined. When i exclude this middle zero from the
join condition everything is performed correct.
I have included a testscript to show the bug.
I am using MonetDb 4.8.2 in windows xp mediacenter on a
P4 2.0 ghz
## Comment 4585
Date: 2005-12-05 11:46:58 +0100
From: @grobian
Logged In: YES
user_id=963970
I created a scriptfile from the Java application. (Dirty
program by the way!) It results for me in:
+------------+-----------+
| urlid | clicktime |
+============+===========+
| <NULL> | 19:42:31 |
+------------+-----------+
1 row
The monster join is a bit too big to easily see what is
happening to me. However, it looks as if this result might
be correct, since you use a LEFT OUTER JOIN which indicates
that everything from clicktest that is not in urltest is
kept in the result as NULL. Since clicktime comes from
clicktest and urlid from urltest, it makes sense that
clicktime is nicely filled, while urlid is set to NULL.
## Comment 4586
Date: 2005-12-05 12:04:33 +0100
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
I use the left outer join to be able to show were it goes
wrong. The result is not correct:
-the longs inserted in both tables are the same for both
tables. The records should therefor match. See the result if
you remove the third long value from the join condition, the
records will match.
-when i use different values in the table, but the same in
both tables, the urlId is coupled to the clicktime.
## Comment 4587
Date: 2005-12-13 13:33:40 +0100
From: @njnes
Logged In: YES
user_id=43556
The hash/xor-ing done for multi column joins had an overflow
resulting in an nil. As nil != nil, some correct results were
gone. A test is added, broken_join.SF-1373391.sql .
## Comment 4588
Date: 2005-12-20 13:50:31 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-12-19, sjoerd: ALREADY IN TESTWEB
sql/src/test/BugTracker/Tests/broken_join.SF-1373391.sql
## Comment 4589
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1373391 at http://sourceforge.net/support/tracker.php?aid=1373391
| Join isn't performed correctly when 4th column is zero | https://api.github.com/repos/MonetDB/MonetDB/issues/791/comments | 0 | 2020-11-30T08:59:08Z | 2024-06-27T11:07:52Z | https://github.com/MonetDB/MonetDB/issues/791 | 753,288,829 | 791 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-12-02 09:23:33 +0100
From: Bastiaan de Groot <<bgroot>>
To: @njnes
Version: -- development
Last updated: 2005-12-13 02:23:02 +0100
## Comment 4572
Date: 2005-12-02 09:23:33 +0100
From: Bastiaan de Groot <<bgroot>>
When I fire the following (incorrect) query:
sql>select urlid,clicktime from
(clicks left outer join urls on
urls.suburl0x0=clicks.suburl0x0 and
urls.suburl0x1=clicks.suburl0x1 and
urls.suburl1x0=clicks.suburl1x0 and
urls.suburl1x1=clicks.suburl1x1 and
urls.suburl2x0=clicks.suburl2x0 and
urls.suburl2x1=clicks.suburl2x1 and
urls.suburl3x0=clicks.suburl3x0 and
urls.suburl3x1=clicks.suburl3x1 and
urls.suburl4x0=clicks.suburl4x0 and
urls.suburl4x1=clicks.suburl4x1 and
urls.suburl5x0=clicks.suburl5x0 and
urls.suburl5x1=clicks.suburl5x1 and
urls.suburl6x0=clicks.suburl6x0 and
urls.suburl6x1=clicks.suburl6x1 and
urls.suburl7x0=clicks.suburl7x0 and
urls.suburl7x1=clicks.suburl7x1 and
urls.suburl8x0=clicks.suburl8x0 and
urls.suburl8x1=clicks.suburl8x1 and
urls.suburl9x0=clicks.suburl9x0 and
urls.suburl9x1=clicks.suburl9x1 and
urls.suburl10x0=clicks.suburl10x0 and
urls.suburl10x1=clicks.suburl10x1 and
urls.suburl11x0=clicks.suburl11x0 and
urls.suburl11x1=clicks.suburl11x1 and
urls.suburl12x0=clicks.suburl12x0 and
urls.suburl12x1=clicks.suburl12x1 and
urls.suburl13x0=clicks.suburl13x0 and
urls.suburl13x1=clicks.suburl13x1 and
urls.suburl14x0=clicks.suburl14x0 and
urls.suburl14x1=clicks.suburl14x1 and
urls.suburl15x0=clicks.suburl15x0 and
urls.suburl15x1=clicks.suburl15x1 and
urls.suburl16x0=clicks.suburl16x0 and
urls.suburl16x1=clicks.suburl16x1) where
clicktime>'00:00:00' and clicktime<'23:59
:59');
I get the following error message:
QUERY = select urlid,clicktime from (clicks left outer
join urls on urls.suburl0
x0=clicks.suburl0x0 and urls.suburl0x1=clicks.suburl0x1
and urls.suburl1x0=click
s.suburl1x0 and urls.suburl1x1=clicks.suburl1x1 and
urls.suburl2x0=clicks.suburl
2x0 and urls.suburl2x1=clicks.suburl2x1 and
urls.suburl3x0=clicks.suburl3x0 and
urls.suburl3x1=clicks.suburl3x1 and
urls.suburl4x0=clicks.suburl4x0 and urls.sub
url4x1=clicks.suburl4x1 and
urls.suburl5x0=clicks.suburl5x0 and urls.suburl5x1=c
licks.suburl5x1 and urls.suburl6x0=clic
ERROR = !parse error, expecting `';'' in: "select
urlid,clicktime from (clicks l
eft outer join urls on urls.suburl0x0=clicks.suburl0x0
and urls.suburl0x1=clicks
.suburl0x1 and urls.suburl1x0=clicks.suburl1x0 and
urls.suburl1x1=clicks.suburl1
x1 and urls.suburl2x0=clicks.suburl2x0 and
urls.suburl2x1=clicks.suburl2x1 and u
rls.suburl3x0=clicks.suburl3x0 and
urls.suburl3x1=clicks.suburl3x1 and urls.subu
rl4x0=clicks.suburl4x0 and
urls.suburl4x1=clicks.suburl4x1 and urls.suburl5x0=cl
icks.suburl5x0 and urls.suburl5x1=clicks.suburl5x1 and
urls.suburl6x0=clicks.sub
url6x0 and urls.suburl6x1=clicks.suburl6x1 and
urls.suburl7x0=clicks.suburl7x0 a
nd urls.suburl7x1=clicks.suburl7x1 and
urls.suburl8x0=clicks.suburl8x0 and urls.
suburl8x1=clicks.suburl8x1 and
urls.suburl9x0=clicks.suburl9x0 and urls.suburl9x
1=clicks.suburl9x1 and
urls.suburl10x0=clicks.suburl10x0 and urls.suburl10x1=cli
cks.suburl10x1 and urls.suburl11x0=clicks.suburl11x0
and urls.suburl11x1=clicks.
suburl11x1 and urls.suburl12x0=clicks.suburl12x0 and
urls.suburl12x1=cliá▀3♣╚☻@♣
☺
Notice the weird symbols on the end of error message.
ps. the query is incorrect due the last closing bracket
which should be left out.
## Comment 4573
Date: 2005-12-02 09:42:47 +0100
From: @drstmane
Logged In: YES
user_id=572415
I've seen similar effects in error messages also with short
queries popping up randomly since the recent yytree and
constant algebra changes. I don't know, whether they are
related, but to me it looks like some non-initialized memory
buffer ...
## Comment 4574
Date: 2005-12-02 10:25:24 +0100
From: @grobian
Logged In: YES
user_id=963970
according to the bugheader this is MonetDB 4.8.0 (stable).
Bastiaan, can you tell what version you use, on which
platform and with howmany spare-bits?
## Comment 4575
Date: 2005-12-02 11:09:43 +0100
From: @grobian
Logged In: YES
user_id=963970
bastiaan, could you please attach a script which contains:
- create statement for your clicks table
- the long select query
kthxplz
## Comment 4576
Date: 2005-12-02 14:27:57 +0100
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
version information:
Monet Database Server V4.8.2
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for i686-pc-win32/32bit with 32bit OIDs;
dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
I use Windows media center edition(which is basicaly windows
xp with sp2) on a p4.
I will try to produce a test script this afternoon but, I
think the problem is in the parser since the query isn't
correct.
## Comment 4577
Date: 2005-12-02 14:32:45 +0100
From: @grobian
Logged In: YES
user_id=963970
might be, but I can't get to your problem, because the
parser bails out at an early stage telling me I don't have a
table named 'clicks', hence I need a simple create statement
of your clicks table.
## Comment 4578
Date: 2005-12-02 15:02:11 +0100
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
I see,
here is the script
## Comment 4579
Date: 2005-12-02 15:05:15 +0100
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
I now see that the statement creating the clicktable is
still outcommented(since it already exist in my db), please
uncomment line 33
## Comment 4580
Date: 2005-12-05 12:07:59 +0100
From: @grobian
Logged In: YES
user_id=963970
It stops at the same location, but without garbage. I find
it a very strange location to stop parsing somehow. I
attached a simple script.
% java -cp MonetDB_JDBCClient.jar:. SymbolBug
Exception in thread "main" java.sql.SQLException: parse
error, expecting `';'' in: "select urlid,clicktime from
(clicks left outer join urls on
urls.suburl0x0=clicks.suburl0x0 and
urls.suburl0x1=clicks.suburl0x1 and
urls.suburl1x0=clicks.suburl1x0 and
urls.suburl1x1=clicks.suburl1x1 and
urls.suburl2x0=clicks.suburl2x0 and
urls.suburl2x1=clicks.suburl2x1 and
urls.suburl3x0=clicks.suburl3x0 and
urls.suburl3x1=clicks.suburl3x1 and
urls.suburl4x0=clicks.suburl4x0 and
urls.suburl4x1=clicks.suburl4x1 and
urls.suburl5x0=clicks.suburl5x0 and
urls.suburl5x1=clicks.suburl5x1 and
urls.suburl6x0=clicks.suburl6x0 and
urls.suburl6x1=clicks.suburl6x1 and
urls.suburl7x0=clicks.suburl7x0 and
urls.suburl7x1=clicks.suburl7x1 and
urls.suburl8x0=clicks.suburl8x0 and
urls.suburl8x1=clicks.suburl8x1 and
urls.suburl9x0=clicks.suburl9x0 and
urls.suburl9x1=clicks.suburl9x1 and
urls.suburl10x0=clicks.suburl10x0 and
urls.suburl10x1=clicks.suburl10x1 and
urls.suburl11x0=clicks.suburl11x0 and
urls.suburl11x1=clicks.suburl11x1 and
urls.suburl12x0=clicks.suburl12x0 and urls.suburl12x1=cl
current transaction is aborted (please ROLLBACK)
at
nl.cwi.monetdb.jdbc.MonetConnection$HeaderList.getNextHeader(MonetConnection.java:2087)
at
nl.cwi.monetdb.jdbc.MonetStatement.getMoreResults(MonetStatement.java:530)
at
nl.cwi.monetdb.jdbc.MonetStatement.getMoreResults(MonetStatement.java:504)
at
nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:374)
at
nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:340)
at
nl.cwi.monetdb.jdbc.MonetStatement.executeQuery(MonetStatement.java:405)
at SymbolBug.main(SymbolBug.java:42)
Monet Database Server V4.9.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for powerpc-apple-darwin8.3.0/64bit with 64bit
OIDs; dynamically linked.
## Comment 4581
Date: 2005-12-13 14:23:00 +0100
From: @njnes
Logged In: YES
user_id=43556
Fixed in two ways. One, increased the buffer for error
messages, 1K was somewhat small. Secondly, the end of the
error string now allows is '0', so we never print beyond the
buffer. Added test inside the broken_join.SF-1373391.sql
test as both use the same schema.
## Comment 4582
Date: 2005-12-20 13:18:48 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: ALREADY IN TESTWEB
Test was added inside the
sql/src/test/BugTracker/Tests/broken_join.SF-1373391.sql as
both use the same schema
## Comment 4583
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1371524 at http://sourceforge.net/support/tracker.php?aid=1371524
| Long query leads to strange symbols in error message | https://api.github.com/repos/MonetDB/MonetDB/issues/790/comments | 0 | 2020-11-30T08:59:04Z | 2024-06-27T11:07:51Z | https://github.com/MonetDB/MonetDB/issues/790 | 753,288,769 | 790 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-30 05:47:12 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-12-23 06:06:37 +0100
## Comment 4567
Date: 2005-11-30 17:47:12 +0100
From: @drstmane
Since recent changes, test
tests/BugsViaSourgeforce/Tests/ID.1244326.XQUERY fails,
basically because the final item is [oid,oid], but
print_results expects and [void,oid].
In fact, item is [oid,oid], since the final leftjoin()
(new) addValues() proc fails to maintain the void head
of the delta input.
(I do not recall right now, how this was done before
the latest changes...)
see also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1244326.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1244326.out.00.html
## Comment 4568
Date: 2005-12-20 13:15:48 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: ALREADY IN TESTWEB
Since this is a report of testweb failure
## Comment 4569
Date: 2005-12-23 17:47:08 +0100
From: @peterboncz
Logged In: YES
user_id=591107
I think I fixed this already; at least in the test web this
does not fail anymore. correct?
it was my [oid](b).access(BAT_WRITE) fix in the udf body.
## Comment 4570
Date: 2005-12-23 18:06:37 +0100
From: @drstmane
Logged In: YES
user_id=572415
test works, hence even I (;-)) consider this one fixed.
## Comment 4571
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1370202 at http://sourceforge.net/support/tracker.php?aid=1370202
| PF: tests/BugsViaSourgeforce/Tests/ID.1244326 fails | https://api.github.com/repos/MonetDB/MonetDB/issues/789/comments | 0 | 2020-11-30T08:59:00Z | 2024-06-27T11:07:50Z | https://github.com/MonetDB/MonetDB/issues/789 | 753,288,725 | 789 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-30 05:05:14 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-12-01 11:56:03 +0100
## Comment 4561
Date: 2005-11-30 17:05:14 +0100
From: @drstmane
Apparently, with some of the latest changes, a 64-bit
OID bug sneaked in that is triggered by XMark query 3:
It seems to work fine on all platforms with 32-bit OIDs
but fails on all platform with 64-bit OIDs.
As usually, see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_XMark/q03.out.00.html
for details.
## Comment 4562
Date: 2005-12-01 16:03:54 +0100
From: @drstmane
Logged In: YES
user_id=572415
A first analysis seems to suggest that
ll_htordered_unique_thetajoin(EQ,...) given different
results with 64- and 32-bit OIDs --- which of course sounds
more than scary --- further investigation is pending ...
## Comment 4563
Date: 2005-12-01 17:18:10 +0100
From: @drstmane
Logged In: YES
user_id=572415
Further analysis reveal, that the problem is related to "in
case of integer equi-join, we shift iter and value together
in a lng and do a single join on that" in proc
ll_htordered_unique_thetajoin, with then tirggers some bug
in leftthetajoin().
See the attached diff of 32- & 64-bit traces for details...
## Comment 4564
Date: 2005-12-01 23:56:03 +0100
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS:
make sure we shift correctly when combining 2 <=32-bit
columns into one 64-bit column
## Comment 4565
Date: 2005-12-20 13:14:27 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: ALREADY IN TEST WEB
Since this is a report of testweb failure
## Comment 4566
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1370172 at http://sourceforge.net/support/tracker.php?aid=1370172
| PF: XMark Q3 triggers 64-bit OID bug | https://api.github.com/repos/MonetDB/MonetDB/issues/788/comments | 0 | 2020-11-30T08:58:57Z | 2024-06-27T11:07:49Z | https://github.com/MonetDB/MonetDB/issues/788 | 753,288,686 | 788 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-27 01:12:05 +0100
From: Alper Çuğun <<alper>>
To: @sjoerdmullender
Version: -- development
Last updated: 2005-11-27 10:09:51 +0100
## Comment 4545
Date: 2005-11-27 01:12:05 +0100
From: Alper Çuğun <<alper>>
Trying to 'make' buildtools fails with all kind of
errors. I have put the output below.
alper@blowfish:~/workspace/monet/buildtools$ make
cd ""/home/alper/workspace/monet/buildtools/."/autogen"
&& python setup.py build
running build
running build_py
running build_scripts
cd _MX && make all
make[1]: Entering directory
`/home/alper/workspace/monet/buildtools/_MX'
make all-am
make[2]: Entering directory
`/home/alper/workspace/monet/buildtools/_MX'
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory
`/home/alper/workspace/monet/buildtools/_MX'
make[1]: Leaving directory
`/home/alper/workspace/monet/buildtools/_MX'
cd _MEL && make all
make[1]: Entering directory
`/home/alper/workspace/monet/buildtools/_MEL'
make all-am
make[2]: Entering directory
`/home/alper/workspace/monet/buildtools/_MEL'
g++ -g -O2 -o mel any_arg.o atom_arg.o atom.o
atomops.o bat_arg.o builtin.o command.o debug.o
depend.o dependency.o epilogue.o FileInfo.o glue.o
html.o iterator.o link.o ListIterator.o mel.o mel.tab.o
mel.yy.o mil.o module.o object.o operator.o ops.o
prelude.o proto.o symbol.o symtable.o type_arg.o use.o
var_arg.o
mel.yy.o: In function `main':
/home/alper/workspace/monet/buildtools/_MEL/mel.yy.cc:2:
multiple definition of `main'
mel.o:/home/alper/workspace/monet/buildtools/./mel/mel.mx:429:
first defined here
/usr/bin/ld: Warning: size of symbol `main' changed
from 898 in mel.o to 16 in mel.yy.o
mel.o: In function `main':
mel.cc:(.text+0x7fd): undefined reference to `yyin'
mel.tab.o: In function `YYLex1()':
/home/alper/workspace/monet/buildtools/_MEL/btyaccpa.ske:743:
undefined reference to `yylex()'
mel.tab.o: In function `semerror()':
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:465:
undefined reference to `yylineno'
mel.tab.o: In function `yyparse':
/home/alper/workspace/monet/buildtools/_MEL/btyaccpa.ske:470:
undefined reference to `mel_yyerror(char
const*)'mel.tab.o: In function `yyparse':
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:299:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:307:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:315:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:75:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:124:
undefined reference to `get_cur_buffer()'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:125:
undefined reference to `yylineno'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:129:
undefined reference to `new_buffer(_IO_FILE*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:53:
undefined reference to `yylineno'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:54:
undefined reference to `yyin'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:61:
undefined reference to `yylineno'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:64:
undefined reference to `close_and_change(void*, _IO_FILE*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:86:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:181:
undefined reference to `get_signature(char*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:182:
undefined reference to `script'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:427:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:323:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:78:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:400:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:240:
undefined reference to `mel_yyerror(char const*)'
mel.tab.o:/home/alper/workspace/monet/buildtools/_MEL/mel.yy:389:
more undefined references to `mel_yyerror(char const*)'
follow
mel.tab.o: In function `YYLex1()':
/home/alper/workspace/monet/buildtools/_MEL/btyaccpa.ske:750:
undefined reference to `yylex()'
collect2: ld returned 1 exit status
make[2]: *** [mel] Error 1
make[2]: Leaving directory
`/home/alper/workspace/monet/buildtools/_MEL'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/alper/workspace/monet/buildtools/_MEL'
make: *** [all] Error 2
alper@blowfish:~/workspace/monet/buildtools$ make clean
cd _MX && make clean
make[1]: Entering directory
`/home/alper/workspace/monet/buildtools/_MX'
test -z "Mx prefixMxFile idxmx epsffit" || rm -f Mx
prefixMxFile idxmx epsffit
rm -f *.o core *.core
make[1]: Leaving directory
`/home/alper/workspace/monet/buildtools/_MX'
cd _MEL && make clean
make[1]: Entering directory
`/home/alper/workspace/monet/buildtools/_MEL'
test -z "mel" || rm -f mel
rm -f *.o core *.core
make[1]: Leaving directory
`/home/alper/workspace/monet/buildtools/_MEL'
cd _BURG && make clean
make[1]: Entering directory
`/home/alper/workspace/monet/buildtools/_BURG'
test -z "burg" || rm -f burg
rm -f *.o core *.core
make[1]: Leaving directory
`/home/alper/workspace/monet/buildtools/_BURG'
alper@blowfish:~/workspace/monet/buildtools$ make
cd ""/home/alper/workspace/monet/buildtools/."/autogen"
&& python setup.py build
running build
running build_py
running build_scripts
cd _MX && make all
make[1]: Entering directory
`/home/alper/workspace/monet/buildtools/_MX'
make all-am
make[2]: Entering directory
`/home/alper/workspace/monet/buildtools/_MX'
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Mx.o -MD -MP -MF ".deps/Mx.Tpo" \
-c -o Mx.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Mx.c' ||
echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Mx.c;
\
then mv -f ".deps/Mx.Tpo" ".deps/Mx.Po"; \
else rm -f ".deps/Mx.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Index.o -MD -MP -MF ".deps/Index.Tpo" \
-c -o Index.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Index.c'
|| echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Index.c;
\
then mv -f ".deps/Index.Tpo" ".deps/Index.Po"; \
else rm -f ".deps/Index.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Def.o -MD -MP -MF ".deps/Def.Tpo" \
-c -o Def.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Def.c' ||
echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Def.c;
\
then mv -f ".deps/Def.Tpo" ".deps/Def.Po"; \
else rm -f ".deps/Def.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Form.o -MD -MP -MF ".deps/Form.Tpo" \
-c -o Form.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Form.c' ||
echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Form.c;
\
then mv -f ".deps/Form.Tpo" ".deps/Form.Po"; \
else rm -f ".deps/Form.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Tok.o -MD -MP -MF ".deps/Tok.Tpo" \
-c -o Tok.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Tok.c' ||
echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Tok.c;
\
then mv -f ".deps/Tok.Tpo" ".deps/Tok.Po"; \
else rm -f ".deps/Tok.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Code.o -MD -MP -MF ".deps/Code.Tpo" \
-c -o Code.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Code.c' ||
echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Code.c;
\
then mv -f ".deps/Code.Tpo" ".deps/Code.Po"; \
else rm -f ".deps/Code.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Display.o -MD -MP -MF ".deps/Display.Tpo" \
-c -o Display.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Display.c'
|| echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Display.c;
\
then mv -f ".deps/Display.Tpo" ".deps/Display.Po"; \
else rm -f ".deps/Display.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Print.o -MD -MP -MF ".deps/Print.Tpo" \
-c -o Print.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Print.c'
|| echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Print.c;
\
then mv -f ".deps/Print.Tpo" ".deps/Print.Po"; \
else rm -f ".deps/Print.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Io.o -MD -MP -MF ".deps/Io.Tpo" \
-c -o Io.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Io.c' ||
echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Io.c;
\
then mv -f ".deps/Io.Tpo" ".deps/Io.Po"; \
else rm -f ".deps/Io.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Sys.o -MD -MP -MF ".deps/Sys.Tpo" \
-c -o Sys.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Sys.c' ||
echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Sys.c;
\
then mv -f ".deps/Sys.Tpo" ".deps/Sys.Po"; \
else rm -f ".deps/Sys.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT disclaimer.o -MD -MP -MF
".deps/disclaimer.Tpo" \
-c -o disclaimer.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/disclaimer.c'
|| echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/disclaimer.c;
\
then mv -f ".deps/disclaimer.Tpo" ".deps/disclaimer.Po"; \
else rm -f ".deps/disclaimer.Tpo"; exit 1; \
fi
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT Tex2Html.o -MD -MP -MF ".deps/Tex2Html.Tpo" \
-c -o Tex2Html.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/Tex2Html.c'
|| echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/Tex2Html.c;
\
then mv -f ".deps/Tex2Html.Tpo" ".deps/Tex2Html.Po"; \
else rm -f ".deps/Tex2Html.Tpo"; exit 1; \
fi
gcc -g -O2 -o Mx Mx.o Index.o Def.o Form.o Tok.o
Code.o Display.o Print.o Io.o Sys.o disclaimer.o Tex2Html.o
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT prefixMxFile.o -MD -MP -MF
".deps/prefixMxFile.Tpo" \
-c -o prefixMxFile.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/prefixMxFile.c'
|| echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/prefixMxFile.c;
\
then mv -f ".deps/prefixMxFile.Tpo"
".deps/prefixMxFile.Po"; \
else rm -f ".deps/prefixMxFile.Tpo"; exit 1; \
fi
gcc -g -O2 -o prefixMxFile prefixMxFile.o disclaimer.o
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT idxmx.o -MD -MP -MF ".deps/idxmx.Tpo" \
-c -o idxmx.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/idxmx.c'
|| echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/idxmx.c;
\
then mv -f ".deps/idxmx.Tpo" ".deps/idxmx.Po"; \
else rm -f ".deps/idxmx.Tpo"; exit 1; \
fi
gcc -g -O2 -o idxmx idxmx.o
if gcc -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./Mx -I.
-g -O2 -MT epsffit.o -MD -MP -MF ".deps/epsffit.Tpo" \
-c -o epsffit.o `test -f
'/home/alper/workspace/monet/buildtools/./Mx/epsffit.c'
|| echo
'/home/alper/workspace/monet/buildtools/./Mx/'`/home/alper/workspace/monet/buildtools/./Mx/epsffit.c;
\
then mv -f ".deps/epsffit.Tpo" ".deps/epsffit.Po"; \
else rm -f ".deps/epsffit.Tpo"; exit 1; \
fi
gcc -g -O2 -o epsffit epsffit.o
make[2]: Leaving directory
`/home/alper/workspace/monet/buildtools/_MX'
make[1]: Leaving directory
`/home/alper/workspace/monet/buildtools/_MX'
cd _MEL && make all
make[1]: Entering directory
`/home/alper/workspace/monet/buildtools/_MEL'
make all-am
make[2]: Entering directory
`/home/alper/workspace/monet/buildtools/_MEL'
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT any_arg.o -MD -MP -MF ".deps/any_arg.Tpo" \
-c -o any_arg.o `test -f 'any_arg.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`any_arg.cc;
\
then mv -f ".deps/any_arg.Tpo" ".deps/any_arg.Po"; \
else rm -f ".deps/any_arg.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT atom_arg.o -MD -MP -MF ".deps/atom_arg.Tpo" \
-c -o atom_arg.o `test -f 'atom_arg.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`atom_arg.cc;
\
then mv -f ".deps/atom_arg.Tpo" ".deps/atom_arg.Po"; \
else rm -f ".deps/atom_arg.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT atom.o -MD -MP -MF ".deps/atom.Tpo" \
-c -o atom.o `test -f 'atom.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`atom.cc; \
then mv -f ".deps/atom.Tpo" ".deps/atom.Po"; \
else rm -f ".deps/atom.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT atomops.o -MD -MP -MF ".deps/atomops.Tpo" \
-c -o atomops.o `test -f 'atomops.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`atomops.cc;
\
then mv -f ".deps/atomops.Tpo" ".deps/atomops.Po"; \
else rm -f ".deps/atomops.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT bat_arg.o -MD -MP -MF ".deps/bat_arg.Tpo" \
-c -o bat_arg.o `test -f 'bat_arg.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`bat_arg.cc;
\
then mv -f ".deps/bat_arg.Tpo" ".deps/bat_arg.Po"; \
else rm -f ".deps/bat_arg.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT builtin.o -MD -MP -MF ".deps/builtin.Tpo" \
-c -o builtin.o `test -f 'builtin.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`builtin.cc;
\
then mv -f ".deps/builtin.Tpo" ".deps/builtin.Po"; \
else rm -f ".deps/builtin.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT command.o -MD -MP -MF ".deps/command.Tpo" \
-c -o command.o `test -f 'command.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`command.cc;
\
then mv -f ".deps/command.Tpo" ".deps/command.Po"; \
else rm -f ".deps/command.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT debug.o -MD -MP -MF ".deps/debug.Tpo" \
-c -o debug.o `test -f 'debug.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`debug.cc; \
then mv -f ".deps/debug.Tpo" ".deps/debug.Po"; \
else rm -f ".deps/debug.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT depend.o -MD -MP -MF ".deps/depend.Tpo" \
-c -o depend.o `test -f 'depend.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`depend.cc;
\
then mv -f ".deps/depend.Tpo" ".deps/depend.Po"; \
else rm -f ".deps/depend.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT dependency.o -MD -MP -MF
".deps/dependency.Tpo" \
-c -o dependency.o `test -f 'dependency.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`dependency.cc;
\
then mv -f ".deps/dependency.Tpo" ".deps/dependency.Po"; \
else rm -f ".deps/dependency.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT epilogue.o -MD -MP -MF ".deps/epilogue.Tpo" \
-c -o epilogue.o `test -f 'epilogue.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`epilogue.cc;
\
then mv -f ".deps/epilogue.Tpo" ".deps/epilogue.Po"; \
else rm -f ".deps/epilogue.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT FileInfo.o -MD -MP -MF ".deps/FileInfo.Tpo" \
-c -o FileInfo.o `test -f 'FileInfo.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`FileInfo.cc;
\
then mv -f ".deps/FileInfo.Tpo" ".deps/FileInfo.Po"; \
else rm -f ".deps/FileInfo.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT glue.o -MD -MP -MF ".deps/glue.Tpo" \
-c -o glue.o `test -f 'glue.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`glue.cc; \
then mv -f ".deps/glue.Tpo" ".deps/glue.Po"; \
else rm -f ".deps/glue.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT html.o -MD -MP -MF ".deps/html.Tpo" \
-c -o html.o `test -f 'html.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`html.cc; \
then mv -f ".deps/html.Tpo" ".deps/html.Po"; \
else rm -f ".deps/html.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT iterator.o -MD -MP -MF ".deps/iterator.Tpo" \
-c -o iterator.o `test -f 'iterator.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`iterator.cc;
\
then mv -f ".deps/iterator.Tpo" ".deps/iterator.Po"; \
else rm -f ".deps/iterator.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT link.o -MD -MP -MF ".deps/link.Tpo" \
-c -o link.o `test -f 'link.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`link.cc; \
then mv -f ".deps/link.Tpo" ".deps/link.Po"; \
else rm -f ".deps/link.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT ListIterator.o -MD -MP -MF
".deps/ListIterator.Tpo" \
-c -o ListIterator.o `test -f 'ListIterator.cc' ||
echo
'/home/alper/workspace/monet/buildtools/./mel/'`ListIterator.cc;
\
then mv -f ".deps/ListIterator.Tpo"
".deps/ListIterator.Po"; \
else rm -f ".deps/ListIterator.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT mel.o -MD -MP -MF ".deps/mel.Tpo" \
-c -o mel.o `test -f 'mel.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`mel.cc; \
then mv -f ".deps/mel.Tpo" ".deps/mel.Po"; \
else rm -f ".deps/mel.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT mel.tab.o -MD -MP -MF ".deps/mel.tab.Tpo" \
-c -o mel.tab.o `test -f 'mel.tab.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`mel.tab.cc;
\
then mv -f ".deps/mel.tab.Tpo" ".deps/mel.tab.Po"; \
else rm -f ".deps/mel.tab.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT mel.yy.o -MD -MP -MF ".deps/mel.yy.Tpo" \
-c -o mel.yy.o `test -f 'mel.yy.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`mel.yy.cc;
\
then mv -f ".deps/mel.yy.Tpo" ".deps/mel.yy.Po"; \
else rm -f ".deps/mel.yy.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT mil.o -MD -MP -MF ".deps/mil.Tpo" \
-c -o mil.o `test -f 'mil.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`mil.cc; \
then mv -f ".deps/mil.Tpo" ".deps/mil.Po"; \
else rm -f ".deps/mil.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT module.o -MD -MP -MF ".deps/module.Tpo" \
-c -o module.o `test -f 'module.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`module.cc;
\
then mv -f ".deps/module.Tpo" ".deps/module.Po"; \
else rm -f ".deps/module.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT object.o -MD -MP -MF ".deps/object.Tpo" \
-c -o object.o `test -f 'object.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`object.cc;
\
then mv -f ".deps/object.Tpo" ".deps/object.Po"; \
else rm -f ".deps/object.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT operator.o -MD -MP -MF ".deps/operator.Tpo" \
-c -o operator.o `test -f 'operator.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`operator.cc;
\
then mv -f ".deps/operator.Tpo" ".deps/operator.Po"; \
else rm -f ".deps/operator.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT ops.o -MD -MP -MF ".deps/ops.Tpo" \
-c -o ops.o `test -f 'ops.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`ops.cc; \
then mv -f ".deps/ops.Tpo" ".deps/ops.Po"; \
else rm -f ".deps/ops.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT prelude.o -MD -MP -MF ".deps/prelude.Tpo" \
-c -o prelude.o `test -f 'prelude.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`prelude.cc;
\
then mv -f ".deps/prelude.Tpo" ".deps/prelude.Po"; \
else rm -f ".deps/prelude.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT proto.o -MD -MP -MF ".deps/proto.Tpo" \
-c -o proto.o `test -f 'proto.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`proto.cc; \
then mv -f ".deps/proto.Tpo" ".deps/proto.Po"; \
else rm -f ".deps/proto.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT symbol.o -MD -MP -MF ".deps/symbol.Tpo" \
-c -o symbol.o `test -f 'symbol.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`symbol.cc;
\
then mv -f ".deps/symbol.Tpo" ".deps/symbol.Po"; \
else rm -f ".deps/symbol.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT symtable.o -MD -MP -MF ".deps/symtable.Tpo" \
-c -o symtable.o `test -f 'symtable.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`symtable.cc;
\
then mv -f ".deps/symtable.Tpo" ".deps/symtable.Po"; \
else rm -f ".deps/symtable.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT type_arg.o -MD -MP -MF ".deps/type_arg.Tpo" \
-c -o type_arg.o `test -f 'type_arg.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`type_arg.cc;
\
then mv -f ".deps/type_arg.Tpo" ".deps/type_arg.Po"; \
else rm -f ".deps/type_arg.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT use.o -MD -MP -MF ".deps/use.Tpo" \
-c -o use.o `test -f 'use.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`use.cc; \
then mv -f ".deps/use.Tpo" ".deps/use.Po"; \
else rm -f ".deps/use.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I.
-I/home/alper/workspace/monet/buildtools/./mel -I.
-g -O2 -MT var_arg.o -MD -MP -MF ".deps/var_arg.Tpo" \
-c -o var_arg.o `test -f 'var_arg.cc' || echo
'/home/alper/workspace/monet/buildtools/./mel/'`var_arg.cc;
\
then mv -f ".deps/var_arg.Tpo" ".deps/var_arg.Po"; \
else rm -f ".deps/var_arg.Tpo"; exit 1; \
fi
g++ -g -O2 -o mel any_arg.o atom_arg.o atom.o
atomops.o bat_arg.o builtin.o command.o debug.o
depend.o dependency.o epilogue.o FileInfo.o glue.o
html.o iterator.o link.o ListIterator.o mel.o mel.tab.o
mel.yy.o mil.o module.o object.o operator.o ops.o
prelude.o proto.o symbol.o symtable.o type_arg.o use.o
var_arg.o
mel.yy.o: In function `main':
/home/alper/workspace/monet/buildtools/_MEL/mel.yy.cc:2:
multiple definition of `main'
mel.o:/home/alper/workspace/monet/buildtools/./mel/mel.mx:429:
first defined here
/usr/bin/ld: Warning: size of symbol `main' changed
from 898 in mel.o to 16 in mel.yy.o
mel.o: In function `main':
mel.cc:(.text+0x7fd): undefined reference to `yyin'
mel.tab.o: In function `YYLex1()':
/home/alper/workspace/monet/buildtools/_MEL/btyaccpa.ske:743:
undefined reference to `yylex()'
mel.tab.o: In function `semerror()':
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:465:
undefined reference to `yylineno'
mel.tab.o: In function `yyparse':
/home/alper/workspace/monet/buildtools/_MEL/btyaccpa.ske:470:
undefined reference to `mel_yyerror(char
const*)'mel.tab.o: In function `yyparse':
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:299:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:307:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:315:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:75:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:124:
undefined reference to `get_cur_buffer()'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:125:
undefined reference to `yylineno'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:129:
undefined reference to `new_buffer(_IO_FILE*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:53:
undefined reference to `yylineno'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:54:
undefined reference to `yyin'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:61:
undefined reference to `yylineno'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:64:
undefined reference to `close_and_change(void*, _IO_FILE*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:86:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:181:
undefined reference to `get_signature(char*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:182:
undefined reference to `script'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:427:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:323:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:78:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:400:
undefined reference to `mel_yyerror(char const*)'
/home/alper/workspace/monet/buildtools/_MEL/mel.yy:240:
undefined reference to `mel_yyerror(char const*)'
mel.tab.o:/home/alper/workspace/monet/buildtools/_MEL/mel.yy:389:
more undefined references to `mel_yyerror(char const*)'
follow
mel.tab.o: In function `YYLex1()':
/home/alper/workspace/monet/buildtools/_MEL/btyaccpa.ske:750:
undefined reference to `yylex()'
collect2: ld returned 1 exit status
make[2]: *** [mel] Error 1
make[2]: Leaving directory
`/home/alper/workspace/monet/buildtools/_MEL'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/alper/workspace/monet/buildtools/_MEL'
make: *** [all] Error 2
## Comment 4546
Date: 2005-11-27 02:20:57 +0100
From: Alper Çuğun <<alper>>
Logged In: YES
user_id=123831
I now tried to build the tools in buildtools separately and
it seems that mel is the culprit (autogen and Mx seem to
work fine).
And I Googled up this reference which is probably related:
http://sourceforge.net/mailarchive/forum.php?thread_id=7428528&forum_id=42505
## Comment 4547
Date: 2005-11-27 09:25:32 +0100
From: @njnes
Logged In: YES
user_id=43556
Thanks for you bug report. We recently moved the buildtools
into there own cvs reposistory (before they were included in
the MonetDB source tree).
Could you attach the configure output of the mel tool, ie
the config.{log,status} and possibly your mel_config.h. Next
to this it maybe important to know your os (version) +
versions of flex and bison.
## Comment 4548
Date: 2005-11-27 18:19:00 +0100
From: Alper Çuğun <<alper>>
Logged In: YES
user_id=123831
I just installed bison, it did not give any errors on it but
now it still does not work.
My respective versions:
Debian GNU/Linux 2.6.12-1-k7
flex version 2.5.4
bison++ Version 1.21.9-1
## Comment 4549
Date: 2005-11-27 18:54:21 +0100
From: @drstmane
Logged In: YES
user_id=572415
If I recall correctly, we require at least bison 1.35 (>=
2.0 is available by now ...); further, we require the plain
C version --- bison++ is the C++ version, right?
I'm afraid our configure(s) do not yet properly check
whether a "proper" version of bison is available --- sorry
for the inconvenience.
Could you please try again with bison >= 1.35; and if there
are still problems, please describe them a bit more specific
than "it still does not work".
## Comment 4550
Date: 2005-11-27 19:29:46 +0100
From: Alper Çuğun <<alper>>
Logged In: YES
user_id=123831
Ok, nice to know. I installed plain bison 1.35 and I tried
bootstrap, configure and make again. I did 'make clean' and
then 'make'. It gives me the following error:
alper@blowfish:~/workspace/monet/buildtools/mel$ make
make all-am
make[1]: Entering directory
`/home/alper/workspace/monet/buildtools/mel'
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT any_arg.o
-MD -MP -MF ".deps/any_arg.Tpo" \
-c -o any_arg.o `test -f 'any_arg.cc' || echo
'./'`any_arg.cc; \
then mv -f ".deps/any_arg.Tpo" ".deps/any_arg.Po"; \
else rm -f ".deps/any_arg.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT atom_arg.o
-MD -MP -MF ".deps/atom_arg.Tpo" \
-c -o atom_arg.o `test -f 'atom_arg.cc' || echo
'./'`atom_arg.cc; \
then mv -f ".deps/atom_arg.Tpo" ".deps/atom_arg.Po"; \
else rm -f ".deps/atom_arg.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT atom.o -MD
-MP -MF ".deps/atom.Tpo" \
-c -o atom.o `test -f 'atom.cc' || echo './'`atom.cc; \
then mv -f ".deps/atom.Tpo" ".deps/atom.Po"; \
else rm -f ".deps/atom.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT atomops.o
-MD -MP -MF ".deps/atomops.Tpo" \
-c -o atomops.o `test -f 'atomops.cc' || echo
'./'`atomops.cc; \
then mv -f ".deps/atomops.Tpo" ".deps/atomops.Po"; \
else rm -f ".deps/atomops.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT bat_arg.o
-MD -MP -MF ".deps/bat_arg.Tpo" \
-c -o bat_arg.o `test -f 'bat_arg.cc' || echo
'./'`bat_arg.cc; \
then mv -f ".deps/bat_arg.Tpo" ".deps/bat_arg.Po"; \
else rm -f ".deps/bat_arg.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT builtin.o
-MD -MP -MF ".deps/builtin.Tpo" \
-c -o builtin.o `test -f 'builtin.cc' || echo
'./'`builtin.cc; \
then mv -f ".deps/builtin.Tpo" ".deps/builtin.Po"; \
else rm -f ".deps/builtin.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT command.o
-MD -MP -MF ".deps/command.Tpo" \
-c -o command.o `test -f 'command.cc' || echo
'./'`command.cc; \
then mv -f ".deps/command.Tpo" ".deps/command.Po"; \
else rm -f ".deps/command.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT debug.o
-MD -MP -MF ".deps/debug.Tpo" \
-c -o debug.o `test -f 'debug.cc' || echo './'`debug.cc; \
then mv -f ".deps/debug.Tpo" ".deps/debug.Po"; \
else rm -f ".deps/debug.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT depend.o
-MD -MP -MF ".deps/depend.Tpo" \
-c -o depend.o `test -f 'depend.cc' || echo './'`depend.cc; \
then mv -f ".deps/depend.Tpo" ".deps/depend.Po"; \
else rm -f ".deps/depend.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT
dependency.o -MD -MP -MF ".deps/dependency.Tpo" \ -c -o
dependency.o `test -f 'dependency.cc' || echo
'./'`dependency.cc; \
then mv -f ".deps/dependency.Tpo" ".deps/dependency.Po"; \
else rm -f ".deps/dependency.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT epilogue.o
-MD -MP -MF ".deps/epilogue.Tpo" \
-c -o epilogue.o `test -f 'epilogue.cc' || echo
'./'`epilogue.cc; \
then mv -f ".deps/epilogue.Tpo" ".deps/epilogue.Po"; \
else rm -f ".deps/epilogue.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT FileInfo.o
-MD -MP -MF ".deps/FileInfo.Tpo" \
-c -o FileInfo.o `test -f 'FileInfo.cc' || echo
'./'`FileInfo.cc; \
then mv -f ".deps/FileInfo.Tpo" ".deps/FileInfo.Po"; \
else rm -f ".deps/FileInfo.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT glue.o -MD
-MP -MF ".deps/glue.Tpo" \
-c -o glue.o `test -f 'glue.cc' || echo './'`glue.cc; \
then mv -f ".deps/glue.Tpo" ".deps/glue.Po"; \
else rm -f ".deps/glue.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT html.o -MD
-MP -MF ".deps/html.Tpo" \
-c -o html.o `test -f 'html.cc' || echo './'`html.cc; \
then mv -f ".deps/html.Tpo" ".deps/html.Po"; \
else rm -f ".deps/html.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT iterator.o
-MD -MP -MF ".deps/iterator.Tpo" \
-c -o iterator.o `test -f 'iterator.cc' || echo
'./'`iterator.cc; \
then mv -f ".deps/iterator.Tpo" ".deps/iterator.Po"; \
else rm -f ".deps/iterator.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT link.o -MD
-MP -MF ".deps/link.Tpo" \
-c -o link.o `test -f 'link.cc' || echo './'`link.cc; \
then mv -f ".deps/link.Tpo" ".deps/link.Po"; \
else rm -f ".deps/link.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT
ListIterator.o -MD -MP -MF ".deps/ListIterator.Tpo" \
-c -o ListIterator.o `test -f 'ListIterator.cc' || echo
'./'`ListIterator.cc; \
then mv -f ".deps/ListIterator.Tpo" ".deps/ListIterator.Po"; \
else rm -f ".deps/ListIterator.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT mel.o -MD
-MP -MF ".deps/mel.Tpo" \
-c -o mel.o `test -f 'mel.cc' || echo './'`mel.cc; \
then mv -f ".deps/mel.Tpo" ".deps/mel.Po"; \
else rm -f ".deps/mel.Tpo"; exit 1; \
fi
if g++ -DHAVE_CONFIG_H -I. -I. -I. -g -O2 -MT mel.tab.o
-MD -MP -MF ".deps/mel.tab.Tpo" \
-c -o mel.tab.o `test -f 'mel.tab.cc' || echo
'./'`mel.tab.cc; \
then mv -f ".deps/mel.tab.Tpo" ".deps/mel.tab.Po"; \
else rm -f ".deps/mel.tab.Tpo"; exit 1; \
fi
mel.tab.cc:17: error: previous declaration of ‘int
yyparse()’ with ‘C++’ linkage
mel.h:37: error: conflicts with new declaration with ‘C’ linkage
make[1]: *** [mel.tab.o] Error 1
make[1]: Leaving directory
`/home/alper/workspace/monet/buildtools/mel'
make: *** [all] Error 2
## Comment 4551
Date: 2005-11-27 19:36:30 +0100
From: @njnes
Logged In: YES
user_id=43556
I just tested with byacc (1.9) instead of bison which also
works.
## Comment 4552
Date: 2005-11-27 19:43:33 +0100
From: @njnes
Logged In: YES
user_id=43556
could you try
make distclean; configure ; make
## Comment 4553
Date: 2005-11-27 19:58:51 +0100
From: Alper Çuğun <<alper>>
Logged In: YES
user_id=123831
I already had byacc installed all the time.
And make distclean... gives the same error.
## Comment 4554
Date: 2005-11-27 20:30:31 +0100
From: @njnes
Logged In: YES
user_id=43556
First of all thanks for still trying. This is something we
haven't seen in a will and definitely want to fix.
It seems the mel.h header file is included after the first
definition of yyparse(). Could you therefor, attach the
mel.tab.cc file, so we could verify this and possibly find a
solution.
## Comment 4555
Date: 2005-11-27 21:02:15 +0100
From: Alper Çuğun <<alper>>
Logged In: YES
user_id=123831
Sure, here it is.
## Comment 4556
Date: 2005-11-27 21:18:44 +0100
From: @njnes
Logged In: YES
user_id=43556
Could you try the following patch?
cvs diff: Diffing .
Index: mel.mx
===================================================================
RCS file: /cvsroot/monetdb/buildtools/mel/mel.mx,v
retrieving revision 1.4
diff -u -r1.4 mel.mx
--- mel.mx 5 Jul 2005 08:50:45 -0000 1.4
+++ mel.mx 27 Nov 2005 20:17:48 -0000
@@ -175,7 +175,7 @@
int yylex();
-extern "C" int yyparse();
+extern int yyparse();
extern void mel_yyerror(const char *);
## Comment 4557
Date: 2005-11-27 22:00:56 +0100
From: Alper Çuğun <<alper>>
Logged In: YES
user_id=123831
That seemed to do the trick. Thanks.
## Comment 4558
Date: 2005-11-27 22:09:51 +0100
From: @njnes
Logged In: YES
user_id=43556
patch applied.
## Comment 4559
Date: 2005-12-20 13:13:41 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: NO TEST / COMPILATION
## Comment 4560
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1367230 at http://sourceforge.net/support/tracker.php?aid=1367230
| buildtools make fails | https://api.github.com/repos/MonetDB/MonetDB/issues/787/comments | 0 | 2020-11-30T08:58:53Z | 2024-06-27T11:07:48Z | https://github.com/MonetDB/MonetDB/issues/787 | 753,288,630 | 787 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-27 01:07:40 +0100
From: Alper Çuğun <<alper>>
To: @sjoerdmullender
Version: -- development
Last updated: 2006-02-24 02:53:09 +0100
## Comment 4541
Date: 2005-11-27 01:07:40 +0100
From: Alper Çuğun <<alper>>
The source installation instruction neglects to mention
the necessity of checking out and building (?) the
buildtools project in order to build MonetDB.
http://monetdb.cwi.nl/GetGoing/Setup/MonetDB/index.html
I found this out because bootstrap complains about a
missing autogen.py. This file seems to be located in
buildtools.
(Not that I can manage to get buildtools to build
properly, but that's for another bug report.)
## Comment 4542
Date: 2005-12-20 13:13:20 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: NO TEST /
WEBSITE/COMPILATION/DOCUMENTATION
## Comment 4543
Date: 2006-02-24 14:53:09 +0100
From: @drstmane
Logged In: YES
user_id=572415
buildtools are now mentioned in MonetDB's HowToStart in the
CVS source and on the website:
http://monetdb.cwi.nl/GetGoing/Setup/MonetDB/Unix/index.html
## Comment 4544
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1367228 at http://sourceforge.net/support/tracker.php?aid=1367228
| buildtools omitted | https://api.github.com/repos/MonetDB/MonetDB/issues/786/comments | 0 | 2020-11-30T08:58:49Z | 2024-06-27T11:07:47Z | https://github.com/MonetDB/MonetDB/issues/786 | 753,288,594 | 786 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-26 08:02:39 +0100
From: Markos <<markos_adam>>
To: @njnes
Version: -- development
Last updated: 2006-01-03 03:11:04 +0100
## Comment 4532
Date: 2005-11-26 20:02:39 +0100
From: Markos <<markos_adam>>
When applying a limit clause to a simple count(*) or
max(*) statement over a table (not grouped), you get an
error message. These kind of statements have no
practical meaning but still should be handled with no
error messages.
Tested on
Both Windows XP and MacOs 10.4
MonetDB Version: 4.8.2
Sample sql (uses system table "tables"):
select count(*) from tables limit 1;
Error Message:
MAPI = monetdb@localhost:45123
QUERY = select count(*) from tables limit 1;
ERROR = !ERROR: interpret: no matching MIL operator to
'slice(int, int, int)'.
!MAYBE YOU MEAN:
! slice(BAT[any::1,any::2], int, int) :
BAT[any::1,any::2]
The following SQL generates no errors:
select type, count(*) from pcolumns group by type limit 1;
## Comment 4533
Date: 2005-11-27 09:28:56 +0100
From: @njnes
Logged In: YES
user_id=43556
Cannot reproduce the bug on the cvs current, ie. could you try
a development version?
## Comment 4534
Date: 2005-11-30 22:39:56 +0100
From: Markos <<markos_adam>>
Logged In: YES
user_id=1389708
If you cannot reproduce it in the latest dev version then
probably you have fixed it between 4.8.2 and current. I will
try to build/install current version if I have some free
time and if there are any news I will post them here.
## Comment 4535
Date: 2005-12-13 00:17:24 +0100
From: @njnes
Logged In: YES
user_id=43556
okay closing it.
## Comment 4536
Date: 2005-12-20 13:11:55 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: TEST ADDED / SUCCESS
sql/src/test/BugDay_2005-12-19_2.9.3/Tests/aggregate_functions_with_limit.SF-1367127.sql
## Comment 4537
Date: 2005-12-20 23:55:18 +0100
From: @drstmane
Logged In: YES
user_id=572415
re-opend as the respective test fails; cf. e.g.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d-Fedora4/src_test_BugDay_2005-12-19_2.9.3/aggregate_functions_with_limit.SF-1367127.out.00.html
(as of tomorrow...)
## Comment 4538
Date: 2005-12-21 12:35:11 +0100
From: @yzchang
Logged In: YES
user_id=341633
The failure is caused by the test script. It used system
tables (tables, pcolumns) as its data. Since the contents
of the system tables change from time to time, the output of
the test script can also be different.
I have committed a new version of the test script, which
uses statically created table as its data. So if the test
does not fail during today's nightly test, I think we can
re-close this bug.
Jennie
## Comment 4539
Date: 2006-01-03 15:11:04 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Closed on behalf of Jennie.
## Comment 4540
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1367127 at http://sourceforge.net/support/tracker.php?aid=1367127
| Aggregate functions with limit | https://api.github.com/repos/MonetDB/MonetDB/issues/785/comments | 0 | 2020-11-30T08:58:46Z | 2024-06-27T11:07:46Z | https://github.com/MonetDB/MonetDB/issues/785 | 753,288,545 | 785 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-24 09:49:19 +0100
From: Jens Teubner <<teubner>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2010-05-04 11:10:03 +0200
## Comment 4523
Date: 2005-11-24 09:49:19 +0100
From: Jens Teubner <<teubner>>
XQuery allows the specify "stable" along with the
"order by" clause in FLWOR expressions. In case two
tuples are identical with respect to the order by
clause, "stable" requests them to be arranged according
to the original input stream, e.g.
for $i in (1 to 10)
stable order by ($i mod 2)
return $i
should return all even numbers *in ascending order*,
then all odd numbers, again in *ascending order*.
The information about the "stable" keyword is currently
available in the parse tree, but not propagated to the
Core tree. So this needs work on that side first.
## Comment 4524
Date: 2005-12-20 12:48:47 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: TEST ADDED / SUCCESS
/ufs/zhang/src/pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/stable_order_by.SF-1265379.xq
## Comment 4525
Date: 2005-12-20 12:55:16 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: TEST ADDED / SUCCESS
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/stable_order_by.SF-1265379.xq
Note: although the status of this bug is "open" and its
resolution is "none", the test script returns (correct)
values as described in the bug report.
## Comment 4526
Date: 2005-12-20 13:13:19 +0100
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
You are right, Jennie. The problem here is that the correct
order returned by Pathfinder is a mere coincidence. The
current code does not actually enforce the "stable"
requirement if the order by criterion does not imply a
unique ordering.
But thanks a lot for the test in the TestWeb.
## Comment 4527
Date: 2006-01-22 20:48:54 +0100
From: @drstmane
Logged In: YES
user_id=572415
Won't be fixed for this release.
## Comment 4528
Date: 2006-06-06 21:12:20 +0200
From: @grobian
Logged In: YES
user_id=963970
Jens, Jennie, Stefan? Can any of you evaluate this bug
briefly once again, and at least assign it to someone?
## Comment 4529
Date: 2006-07-29 13:58:57 +0200
From: @drstmane
Logged In: YES
user_id=572415
Just for the records:
Thanks to Sjoerd, MonetDB 4.13.1 (CVS HEAD) now has a stable
sort (ssort()).
Maybe, that could be of use when implementing the stable
order by in MonetDB/XQuery.
## Comment 4530
Date: 2006-08-02 18:39:07 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Information about the "stable" option is now propagated
into the XQuery Core tree.
Both back-ends (milprint_summer and algebra) currently
*always* implement stable order by. This is semantically
correct, but we might miss optimization opportunities. So
we rather have a non-exploited optimization hook than a
real bug.
(To go into the details: both implementations refine the
specified order by the `pos' information, which is
unnecessary if "stable" was not given in the input query.)
## Comment 4531
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1365379 at http://sourceforge.net/support/tracker.php?aid=1365379
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: "stable order by" | https://api.github.com/repos/MonetDB/MonetDB/issues/784/comments | 0 | 2020-11-30T08:58:42Z | 2024-06-28T07:36:44Z | https://github.com/MonetDB/MonetDB/issues/784 | 753,288,503 | 784 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-23 11:49:41 +0100
From: @yzchang
To: MonetDB4 devs <<bugs-monetdb4>>
Version: -- development
Last updated: 2005-11-25 11:55:13 +0100
## Comment 4518
Date: 2005-11-23 23:49:41 +0100
From: @yzchang
Start mapi listener with:
$Mserver --dbinit="module(mapi); mapi_start();"
Results in Mserver crash:
$Mserver --dbinit="module(mapi); mapi_start();"
Monet Database Server V4.9.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
Mserver: ../../../src/monet/yytree.mx:237: Myyexpand:
Assertion `n->extendable' failed.
MonetDB>Aborted
While it is no problem to start mapi listener after
Mserver has been started:
$Mserver
Monet Database Server V4.9.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>module(mapi);
MonetDB>mapi_start();
MonetDB>
## Comment 4519
Date: 2005-11-24 09:23:21 +0100
From: @drstmane
Logged In: YES
user_id=572415
Jennie,
according to out TestWeb, all MAPI tests (starting Mserver
with --dbinit="module(mapi); mapi_start();") seem to work
fine (cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/index_short.html),
hence:
- When did you last `cvs update -dP` your MonetDB?
- Which flags did you use with configure?
- Did you re-build from scratch (i.e., `rm -rf
$MONETDB_BUILD && de-bootstrap && bootstrap && configure &&
make && make install` ) after the last `cvs update -dP`, or
did you just call `make && make install`?
## Comment 4520
Date: 2005-11-25 11:54:28 +0100
From: @yzchang
Logged In: YES
user_id=341633
Stefan,
Sorry for the extra work I created for you. I might have
submitted this bug too enthusiatically, since I'm not
completely sure that "cvs update -dP" has been doen before I
rebuild the system (I do always do 'cvs update', but I did
not check if it was succeeded...).
After 'cvs update' and rebuild the system again, this
problem is gone now. So I close this bug and mark it as
'invalid'.
## Comment 4521
Date: 2005-12-20 12:37:04 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: No TEST / COMPILATION/INVALID
## Comment 4522
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1365089 at http://sourceforge.net/support/tracker.php?aid=1365089
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-monetdb4@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| --dbinit="module(mapi); mapi_start()" crashes Mserver | https://api.github.com/repos/MonetDB/MonetDB/issues/783/comments | 0 | 2020-11-30T08:58:39Z | 2024-06-28T07:36:44Z | https://github.com/MonetDB/MonetDB/issues/783 | 753,288,463 | 783 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-23 12:39:35 +0100
From: Dave van Soest <<dsoest>>
To: @njnes
Version: -- development
Last updated: 2005-11-23 02:44:07 +0100
## Comment 4514
Date: 2005-11-23 12:39:35 +0100
From: Dave van Soest <<dsoest>>
It seems not possible to concurrently insert tuples
into a table that has a foreign key.
An example:
CREATE TABLE urls (urlid INT NOT NULL, url
VARCHAR(1024), PRIMARY KEY (urlid));
CREATE TABLE clickstream (urlid INT NOT NULL, clicktime
TIME NOT NULL, FOREIGN KEY (urlid) REFERENCES urls
(urlid));
INSERT INTO urls VALUES(1, 'something');
INSERT INTO urls VALUES(2, 'dummy');
Now start two (Mapi)clients and execute the following
commands in this order:
Client 1: INSERT INTO clickstream VALUES(1, '00:01:02');
Client 2: INSERT INTO clickstream VALUES(2, '01:02:03');
Client 1: COMMIT;
Client 2: COMMIT;
The last commit will produce a concurrency error.
Note that these commands will work when the declaration
of the foreign key is omitted when the
clickstream-table is created.
Dave van Soest,
Mark de Greef
## Comment 4515
Date: 2005-11-23 14:44:06 +0100
From: @grobian
Logged In: YES
user_id=963970
Thanks for your bug report. However, this is expected
behaviour on the "FULLY SERIALIZABLE" isolation level in SQL99.
## Comment 4516
Date: 2005-12-20 12:37:55 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: NO TEST / INVALID
## Comment 4517
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1364563 at http://sourceforge.net/support/tracker.php?aid=1364563
| Concurrent insert not possible with foreign key | https://api.github.com/repos/MonetDB/MonetDB/issues/782/comments | 0 | 2020-11-30T08:58:36Z | 2024-06-28T07:36:44Z | https://github.com/MonetDB/MonetDB/issues/782 | 753,288,412 | 782 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-22 01:58:12 +0100
From: Bastiaan de Groot <<bgroot>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2005-11-22 02:15:26 +0100
## Comment 4510
Date: 2005-11-22 13:58:12 +0100
From: Bastiaan de Groot <<bgroot>>
When I use a preparedStatement I get the following error:
java.sql.SQLException: wrong number of arguments for
prepared statement
at
nl.cwi.monetdb.jdbc.MonetConnection$HeaderList.getNextHeader(MonetConnection.java:2165)
at
nl.cwi.monetdb.jdbc.MonetStatement.getMoreResults(MonetStatement.java:485)
at
nl.cwi.monetdb.jdbc.MonetStatement.getMoreResults(MonetStatement.java:459)
at
nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:329)
at
nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:290)
at
nl.cwi.monetdb.jdbc.MonetPreparedStatement.execute(MonetPreparedStatement.java:166)
at getPreparedBug.main(getPreparedBug.java:40)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.intellij.rt.execution.application.AppMain.main(AppMain.java:86)
At first look it seems like i forgot to fill in an
argument or filled in one to many but when, i increase
or decrease the amount of arguments i fill in. I get a
clear message that a certain argument number doesn't
exsist or that one is missing.
When in my connection I set the following option:
?native_prepared_statemen1970-01-01 01:00:00 +0100false
The code is executing without any errors and gives the
wanted result.
I have included a java file who generates the error.
## Comment 4511
Date: 2005-11-22 14:15:26 +0100
From: @grobian
Logged In: YES
user_id=963970
duplicate of http://sourceforge.net/support/tracker.php?aid=1363729
## Comment 4512
Date: 2005-12-20 11:47:38 +0100
From: @yzchang
Logged In: YES
user_id=341633
BugDay_2005-12-19, Jennie: NO TEST / DUPLICATE (1363729)
## Comment 4513
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1363733 at http://sourceforge.net/support/tracker.php?aid=1363733
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| SQL: wrong number of arguments for prepared statement | https://api.github.com/repos/MonetDB/MonetDB/issues/781/comments | 0 | 2020-11-30T08:58:33Z | 2024-06-28T07:36:43Z | https://github.com/MonetDB/MonetDB/issues/781 | 753,288,380 | 781 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-22 01:51:23 +0100
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-11-23 12:31:31 +0100
## Comment 4506
Date: 2005-11-22 13:51:23 +0100
From: @grobian
The attached file contains an example script which
confuses the server. It creates a table with 35
columns, then prepares a statement to insert 35 columns
and finally executes the prepared statement. At this
final execution the server dies claiming that the
number of supplied values doesn't match the number of
the prepared statement.
This bug was pointed out by Bastiaan de Groot.
## Comment 4507
Date: 2005-11-23 00:31:31 +0100
From: @njnes
Logged In: YES
user_id=43556
Fixed, well as the underlying engine (MonetDB4) doesn't
support more than 32 arguments to procs, we need to limit
the use by the sql frontend. So now we give a proper error
message on large prepares.
A test script was added.
## Comment 4508
Date: 2005-12-20 11:45:29 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
sql/src/test/BugTracker/Tests/large_prepare.SF-1363729.sql
## Comment 4509
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1363729 at http://sourceforge.net/support/tracker.php?aid=1363729
| SQL: Many columns in prepared statement confuse server | https://api.github.com/repos/MonetDB/MonetDB/issues/780/comments | 0 | 2020-11-30T08:58:29Z | 2024-06-27T11:07:41Z | https://github.com/MonetDB/MonetDB/issues/780 | 753,288,346 | 780 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-22 10:15:13 +0100
From: Bastiaan de Groot <<bgroot>>
To: @njnes
Version: -- development
Last updated: 2005-11-26 12:49:48 +0100
## Comment 4502
Date: 2005-11-22 10:15:13 +0100
From: Bastiaan de Groot <<bgroot>>
When I try to insert an illigal value in a timestamp
field this leads to an null value being inserted
instead of an error being raised, see the following
example:
sql>create table foo (bar timestamp);
6 querytype
sql>insert into foo values('12:12:12:99');
4 querytype
[ 1 ]
sql>select * from foo;
3 querytype
foo table_name
bar name
timestamp type
19 length
1 tuplecount
2 id
[ NULL ]
Fabian found out that the following code gives out the
correct error:
monetdb-> create table foo (bar timestamp);
Operation successful
monetdb-> insert into foo values('12:12:12:99');
1 affected row
monetdb-> insert into foo values(timestamp '12:12:12:99');
Error: incorrect timestamp value (12:12:12:99) in:
"insert into foo
values(timestamp '12:12:12:99')"
So apperantly the checking isn't performed correctly
## Comment 4503
Date: 2005-11-26 00:49:46 +0100
From: @njnes
Logged In: YES
user_id=43556
test script added which runs fine now
The internal cast functions (from string) return nil on
invalid strings. we now wrap these and chek for nil.
## Comment 4504
Date: 2005-12-20 11:45:01 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
sql/src/test/BugTracker/Tests/inserting_invalid_timestamp.SF-1363557.sql
## Comment 4505
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1363557 at http://sourceforge.net/support/tracker.php?aid=1363557
| SQL: inserting an invalid timestamp leads to a null value | https://api.github.com/repos/MonetDB/MonetDB/issues/779/comments | 0 | 2020-11-30T08:58:26Z | 2024-06-27T11:07:40Z | https://github.com/MonetDB/MonetDB/issues/779 | 753,288,316 | 779 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-21 08:42:46 +0100
From: @grobian
To: @sjoerdmullender
Version: -- development
Last updated: 2005-11-22 12:45:28 +0100
## Comment 4496
Date: 2005-11-21 20:42:46 +0100
From: @grobian
I updated compiled and installed from scratch:
- buildtools
- monetdb current
- sql current
Compiling SQL fails with a lot of complaints. A small
excerpt follows:
odbc.py.c:13290: error: initializer element is not constant
odbc.py.c:13290: warning: data definition has no type
or storage class
odbc.py.c:13291: error: syntax error before 'if'
odbc.py.c: In function 'init_odbc':
odbc.py.c:13330: error: syntax error before '*' token
odbc.py.c:13332: error: 'PyObject' undeclared (first
use in this function)
odbc.py.c:13332: error: 'm' undeclared (first use in
this function)
odbc.py.c:13332: error: invalid operands to binary *
odbc.py.c:13332: error: 'd' undeclared (first use in
this function)
odbc.py.c:13332: warning: left-hand operand of comma
expression has no effect
odbc.py.c:13332: warning: statement with no effect
odbc.py.c:13334: error: 'SWIG_globals' undeclared
(first use in this function)
odbc.py.c:13334: warning: statement with no effect
odbc.py.c:13339: warning: statement with no effect
odbc.py.c:13340: warning: statement with no effect
odbc.py.c:13407: error: 'odbc' undeclared (first use in
this function)
odbc.py.c:13407: error: invalid operands to binary *
odbc.py.c:13407: warning: statement with no effect
odbc.py.c:13410: warning: implicit declaration of
function 'PyErr_NewException'
odbc.py.c:13410: warning: assignment makes pointer from
integer without a cast
odbc.py.c:13415: warning: implicit declaration of
function 'PyImport_ImportModule'
odbc.py.c:13415: warning: statement with no effect
odbc.py.c:13417: warning: implicit declaration of
function 'Py_FatalError'
odbc.py.c:13420: warning: implicit declaration of
function 'PyObject_GetAttrString'
make[5]: *** [odbc.py.lo] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
## Comment 4497
Date: 2005-11-22 10:01:05 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Please provide the *first* part of the errors. The last
part is pretty useless for debugging purposes.
But one hint: make sure autogen is up-to-date.
## Comment 4498
Date: 2005-11-22 11:07:53 +0100
From: @grobian
Logged In: YES
user_id=963970
how do I check for the freshness of autogen? As stated, I
updated this yesterday (and today). How can I check all the
voodoo went fine? I removed all build and installation dirs
to make sure no junk was around to cause trouble...
% env
PYTHONPATH=$BUILDTOOLS_DIR/program-x86_64/lib/python2.4/site-packages
$BUILDTOOLS_DIR/program-x86_64/bin/autogen.py --version
Traceback (most recent call last):
File
"/ufs/fabian/scratch/monetdb/buildtools/program-x86_64/bin/autogen.py",
line 163, in ?
(InstallList, DocList, OutList) = main(topdir, topdir,
automake, [])
File
"/ufs/fabian/scratch/monetdb/buildtools/program-x86_64/bin/autogen.py",
line 131, in main
read_makefile(p, cwd)
File
"/ufs/fabian/scratch/monetdb/buildtools/program-x86_64/bin/autogen.py",
line 92, in read_makefile
for line in fileinput.input(os.path.join(cwd,
'Makefile.ag')):
File "/usr/lib64/python2.4/fileinput.py", line 231, in next
line = self.readline()
File "/usr/lib64/python2.4/fileinput.py", line 320, in
readline
self._file = open(self._filename, "r")
IOError: [Errno 2] No such file or directory:
'--version/Makefile.ag'
As for the build errors:
% wc -l build.err
6473 build.err
% head -n20 build.err
Making MonetDB/SQL
odbc.py.c:22:20: error: Python.h: No such file or directory
odbc.py.c:622: error: syntax error before 'PyObject_HEAD'
odbc.py.c:622: warning: no semicolon at end of struct or union
odbc.py.c:625: error: syntax error before '}' token
odbc.py.c:625: warning: type defaults to 'int' in
declaration of 'PySwigObject'
odbc.py.c:625: warning: data definition has no type or
storage class
odbc.py.c:630: error: syntax error before '*' token
odbc.py.c: In function 'PySwigObject_print':
odbc.py.c:633: error: 'v' undeclared (first use in this
function)
odbc.py.c:633: error: (Each undeclared identifier is
reported only once
odbc.py.c:633: error: for each function it appears in.)
odbc.py.c:634: warning: implicit declaration of function 'fputs'
odbc.py.c:634: error: 'fp' undeclared (first use in this
function)
odbc.py.c:639: warning: control reaches end of non-void function
odbc.py.c: At top level:
odbc.py.c:641: error: syntax error before '*' token
odbc.py.c:642: error: syntax error before '*' token
odbc.py.c:643: warning: return type defaults to 'int'
odbc.py.c: In function 'PySwigObject_repr':
## Comment 4499
Date: 2005-11-22 12:45:28 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
There was indeed a problem in the odbc/python Makefile.
This is now fixed in CVS.
## Comment 4500
Date: 2005-12-20 11:44:33 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / COMPILATION
## Comment 4501
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1363051 at http://sourceforge.net/support/tracker.php?aid=1363051
| Compilation of odbc.py.lo fails | https://api.github.com/repos/MonetDB/MonetDB/issues/778/comments | 0 | 2020-11-30T08:58:23Z | 2024-06-27T11:07:39Z | https://github.com/MonetDB/MonetDB/issues/778 | 753,288,282 | 778 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-21 02:21:43 +0100
From: monaree <<monica_areej>>
To: @njnes
Version: -- development
Last updated: 2005-11-26 12:54:13 +0100
## Comment 4488
Date: 2005-11-21 14:21:43 +0100
From: monaree <<monica_areej>>
Run the attached SQL script on MonetDB 4.8.3. It will
crash the server with a Segmentation Fault. The problem
lies in the last statement with the sum (SET .. = ... +
SELECT ...).
## Comment 4489
Date: 2005-11-21 15:08:03 +0100
From: @yzchang
Logged In: YES
user_id=341633
I think your attachment wasn't attached successfully. You
need to select the checkbox next to "Check to Upload and
Attach a File:"
So please try attach your script again. Thank you!
## Comment 4490
Date: 2005-11-21 15:20:05 +0100
From: @grobian
Logged In: YES
user_id=963970
When executing the script I get this error:
!CONSTRAINT FOREIGN KEY: no such table table 'url'
I think the create statement for the table "url" is missing.
Could you please add it so we can exactly reproduce your
situation?
## Comment 4491
Date: 2005-11-21 20:33:03 +0100
From: @grobian
Logged In: YES
user_id=963970
please drop a small message that you uploaded a file next
time, because we (at least I) don't get notified if you only
upload a file.
## Comment 4492
Date: 2005-11-21 20:51:52 +0100
From: @grobian
Logged In: YES
user_id=963970
I corrected your script myself this time. (See attach)
Now I indeed get a nice crash:
MonetDB>Mserver:
/ufs/fabian/scratch/monetdb/current/sql/src/server/sql_select.mx:865:
sql_binop: Assertion `list_length(rs->op1.lval) == 1' failed.
Abort
## Comment 4493
Date: 2005-11-26 00:54:12 +0100
From: @njnes
Logged In: YES
user_id=43556
this update uses outer references. This case wasn't properly
handled.
Test added
src/test/BugTracker/Tests/update_with_subselect.SF-1362771.sql
## Comment 4494
Date: 2005-12-20 11:44:16 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
sql/src/test/BugTracker/Tests/update_with_subselect.SF-1362771.sql
## Comment 4495
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1362771 at http://sourceforge.net/support/tracker.php?aid=1362771
| SQL: Seg fault on UPDATE statement with subselect | https://api.github.com/repos/MonetDB/MonetDB/issues/777/comments | 0 | 2020-11-30T08:58:20Z | 2024-06-27T11:07:37Z | https://github.com/MonetDB/MonetDB/issues/777 | 753,288,251 | 777 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-18 11:44:43 +0100
From: Jens Teubner <<teubner>>
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2005-11-18 12:50:13 +0100
## Comment 4484
Date: 2005-11-18 11:44:43 +0100
From: Jens Teubner <<teubner>>
I'm a bit frightened by the fact that I will have to
touch our parser again, and hope I can fix this one
with more collateral damage than Peter's latest changes
to the MonetDB parser ;-).
The query
for $i in (1,2)
order by ($i) ascending
return $i
fails with
syntax error, unexpected ") as", expecting ")"
on line 2 (next token is `) as')
parse error: XQuery parsing failed
But I think that should be easy to fix. I'm currently
looking into this.
## Comment 4485
Date: 2005-11-18 12:50:13 +0100
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Fix is now in CVS (stable).
Added a trailing whitespace to the lexer pattern
`) as' (now `) as '). This prevents it from being
matched in the given example.
(And for the next bugday: A test is already there.)
## Comment 4486
Date: 2005-12-20 11:47:50 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
pathfinder/compiler/parser/Tests/good-112.xq
## Comment 4487
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1359816 at http://sourceforge.net/support/tracker.php?aid=1359816
| PF: parser problem: `) as' vs. `)' `ascending' | https://api.github.com/repos/MonetDB/MonetDB/issues/776/comments | 0 | 2020-11-30T08:58:17Z | 2024-06-27T11:07:36Z | https://github.com/MonetDB/MonetDB/issues/776 | 753,288,209 | 776 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-17 08:28:30 +0100
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2005-11-25 12:01:18 +0100
## Comment 4477
Date: 2005-11-17 20:28:30 +0100
From: @drstmane
Since yesterday's "yytree" optimization (and related
changes/checkins), 468 out of the 946 pathfinder tests
fail, maily as Mserver crashes with a segfault as soon
as module pathfinder is loaded:
$ gdb Mserver
GNU gdb Red Hat Linux (6.3.0.0-1.84rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it
under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as
"x86_64-redhat-linux-gnu"...Using host libthread_db
library "/lib64/libthread_db.so.1".
(gdb) r
Starting program:
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.GNU.64.64.d.--enable-debug.PREFIX./bin/Mserver
[Thread debugging using libthread_db enabled]
[New Thread 46912516843424 (LWP 12821)]
[New Thread 1082132832 (LWP 12857)]
Monet Database Server V4.9.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>module(pathfinder);
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912516843424 (LWP 12821)]
0x0000003fea46aea8 in _int_malloc () from /lib64/libc.so.6
(gdb) up
1 0x0000003fea46cb3b in malloc () from /lib64/libc.so.6
(gdb)
2 0x00002aaaab8ec10f in GDKmallocmax (size=256,
maxsize=0x7ffffef8d0e8, emergency=1)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/gdk/gdk_utils.mx:1055
1055 GDKmalloc_prefixsize(s, size);
(gdb) li
1050 s[-1] = -((ssize_t) size);
1051 *maxsize = newmax -
(sizeof(size_t) + sizeof(size_t));
1052 return (void *) s;
1053 }
1054 CHKMEM(size, 0);
1055 GDKmalloc_prefixsize(s, size);
1056 if (s == NULL) {
1057 GDKmemfail("GDKmalloc", size,
BBPTRIM_ALL, 0);
1058 GDKmalloc_prefixsize(s, size);
1059 if (s == NULL) {
(gdb) print s
$1 = (ssize_t *) 0x0
(gdb) print size
$2 = 256
(gdb)
## Comment 4478
Date: 2005-11-17 21:37:52 +0100
From: @mlkersten
Logged In: YES
user_id=490798
The impact of these changes in essence make
nightly built not to be trusted. This affects
all developers in their daily work and should
be resolved with the highest priority, such that
the web is clean the next nightly run.
## Comment 4479
Date: 2005-11-18 13:38:00 +0100
From: @drstmane
Logged In: YES
user_id=572415
The problem seem to be an endless recusion in yycopy that
causes stack overflow and (hence?) a failing malloc() (see
trace below).
Unfortunately, I haven't found the trigger for the endless
recursion, yet ...
$ gdb Mserver
GNU gdb Red Hat Linux (6.3.0.0-1.84rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...Using
host libthread_db library "/lib64/libthread_db.so.1".
(gdb) r
Starting program:
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.GNU.64.64.d.--enable-debug.PREFIX./bin/Mserver
[Thread debugging using libthread_db enabled]
[New Thread 46912516843424 (LWP 31239)]
[New Thread 1082132832 (LWP 31276)]
Monet Database Server V4.9.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>module(pathfinder);
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912516843424 (LWP 31239)]
0x0000003fea46aea8 in _int_malloc () from /lib64/libc.so.6
(gdb) up
1 0x0000003fea46cb3b in malloc () from /lib64/libc.so.6
(gdb)
2 0x00002aaaab8ec10f in GDKmallocmax (size=256,
maxsize=0x7ffffef270e8, emergency=1)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/gdk/gdk_utils.mx:1055
1055 GDKmalloc_prefixsize(s, size);
(gdb) li
1050 s[-1] = -((ssize_t) size);
1051 *maxsize = newmax - (sizeof(size_t)
+ sizeof(size_t));
1052 return (void *) s;
1053 }
1054 CHKMEM(size, 0);
1055 GDKmalloc_prefixsize(s, size);
1056 if (s == NULL) {
1057 GDKmemfail("GDKmalloc", size,
BBPTRIM_ALL, 0);
1058 GDKmalloc_prefixsize(s, size);
1059 if (s == NULL) {
(gdb) bt
0 0x0000003fea46aea8 in _int_malloc () from /lib64/libc.so.6
1 0x0000003fea46cb3b in malloc () from /lib64/libc.so.6
2 0x00002aaaab8ec10f in GDKmallocmax (size=256,
maxsize=0x7ffffef270e8, emergency=1)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/gdk/gdk_utils.mx:1055
3 0x00002aaaab8ec29a in GDKmalloc (size=256) at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/gdk/gdk_utils.mx:1076
4 0x00002aaaaaade418 in yychunkalloc (tok=268, cap=0,
extendable=0, noyyval=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:166
5 0x00002aaaaaade64a in yycopy (t=0x2aaab5c48e80,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:193
6 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
7 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
8 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
9 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
10 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
11 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
12 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
13 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
14 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
15 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
16 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
17 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
18 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
19 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
20 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
21 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
22 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
23 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
24 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
25 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
26 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
27 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:216
28 0x00002aaaaaade7bb in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:214
29 0x00002aaaaaade852 in yycopy (t=0x2aaab5c48d00,
kill_orig=1, func_parent=0, next=0x7fffffb23408,
end=0x7fffffb23400)
---Type <return> to continue, or q <return> to quit---
## Comment 4480
Date: 2005-11-20 18:32:34 +0100
From: @drstmane
Logged In: YES
user_id=572415
According to the TestWeb, this looks fixed to me.
Peter,
could you please check/confirm, and in case it's indeed
fixed, mark this report "fixed" and close it?
Thanks in advance.
Stefan
## Comment 4481
Date: 2005-11-25 00:01:18 +0100
From: @peterboncz
Logged In: YES
user_id=591107
all fixed
## Comment 4482
Date: 2005-12-20 11:43:40 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB
## Comment 4483
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1359227 at http://sourceforge.net/support/tracker.php?aid=1359227
| PF: 468 out of 946 test fail after "yytree" changes | https://api.github.com/repos/MonetDB/MonetDB/issues/775/comments | 0 | 2020-11-30T08:58:13Z | 2024-06-27T11:07:35Z | https://github.com/MonetDB/MonetDB/issues/775 | 753,288,160 | 775 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-17 08:17:06 +0100
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2005-11-18 10:45:37 +0100
## Comment 4470
Date: 2005-11-17 20:17:06 +0100
From: @drstmane
Since yesterday's "yytree" optimization (and related
changes/checkins), 333 of the 338 SQL tests fail,
mainly because Mserver crashes with an assertion as
soon as MapiClient -lsql tries to connect:
Mserver:
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/monet_interpreter.mx:1099:
interpret: Assertion `(int) (argc*sizeof(ValRecord)) <=
opcache->yyval.val.ival' failed.
## Comment 4471
Date: 2005-11-17 21:39:00 +0100
From: @mlkersten
Logged In: YES
user_id=490798
The impact of these changes in essence make
nightly built not to be trusted. This affects
all developers in their daily work and should
be resolved with the highest priority, such that
the web is clean the next nightly run.
## Comment 4472
Date: 2005-11-18 00:59:55 +0100
From: @drstmane
Logged In: YES
user_id=572415
Niels, latest fixes seem to bring us back to only 3 failing
test. Thank you very much, Niels!
Once this is confirmed by tomorrows testweb, this bug report
can be closed.
## Comment 4473
Date: 2005-11-18 10:45:37 +0100
From: @drstmane
Logged In: YES
user_id=572415
Indeed, Niels fix has solved the MapiClient connection
problem. Hence, I close this bug report.
For the bookkeeping:
However, there are still more tests failing now than before
the "yytree" optimization in MonetDB:
16.11. 17.11. 19.11.
C1.5.12 G32/32s 30 54 30
D8.2.0 G32/32d 8 332 9
D3.0 G64/64d 3 332 40
F3 G64/64d 3 332 20
F3 n64/64d 3 332 24
F4 G32/32d 5 332 9
F4 G64/32d 4 333 6
F4 G64/64d 3 332 5
F4 n64/32d 4 333 5
F4 n64/64d 3 332 5
G1.6.13 G32/32d 9 332 15
I646.5 G64/64d 15 321 16
R4 G64/64d 7 332 26
R4 n64/64d 7 332 63
S9.3 G32/32d 22 332 32
S9.3 G64/64d 4 332 30
S9.3 n64/64d 4 86 29
S5.8 G64/64d 15 332 23
S5.8 n64/64d 17 332 23
see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/index_short.html
for details.
(Sorry, I don't have time right now to properly file more
bug reports...)
## Comment 4474
Date: 2005-11-18 10:46:37 +0100
From: @drstmane
Logged In: YES
user_id=572415
oops, forgot to tell who took care of this bug...
## Comment 4475
Date: 2005-12-20 11:43:22 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB
## Comment 4476
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1359220 at http://sourceforge.net/support/tracker.php?aid=1359220
| SQL: 333 out of 338 tests fail after "yytree" changes | https://api.github.com/repos/MonetDB/MonetDB/issues/774/comments | 0 | 2020-11-30T08:58:09Z | 2024-06-27T11:07:34Z | https://github.com/MonetDB/MonetDB/issues/774 | 753,288,116 | 774 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-17 05:45:17 +0100
From: Jens Teubner <<teubner>>
To: @sjoerdmullender
Version: -- development
Last updated: 2005-11-18 11:33:16 +0100
## Comment 4463
Date: 2005-11-17 17:45:17 +0100
From: Jens Teubner <<teubner>>
The configure script for the buildtools does not
complain if Python cannot be found on the system. It
runs perfectly fine, but as soon as I invoke make, I
get
bash$ make
cd ""/path/to/buildtools/."/autogen" && python setup.py
build
/bin/sh: line 1: python: command not found
make: *** [all] Error 127
(Btw. there's no "Group" for the buildtools repository
on the Bug submission page.)
## Comment 4464
Date: 2005-11-17 18:26:59 +0100
From: @drstmane
Logged In: YES
user_id=572415
This is indeed inconvenient.
The reason is that (1) there actually is no configure for
autogen, yet, and (2) the top-level configure is just a
wrapper that calls the individual configure's (for Mx, mel,
& burg).
We will check, whether we can (i) add a proper configure
also for autogen, (ii) check for python in the top-level
configure-wrapper (or top-level make-wrapper), (iii) or at
least mention in the README's that python is required.
(I added "buildtools" to the "Group".)
## Comment 4465
Date: 2005-11-18 11:05:48 +0100
From: @drstmane
Logged In: YES
user_id=572415
Jens,
the top-level configure(-wrapper) no checks whether python
(required for autogen) is available in $PATH, and aborts if not.
Please close this bug repost, in case you agree with this
fix, or set the resolution back to "none", otherwise.
Thanks,
Stefan
## Comment 4466
Date: 2005-11-18 11:33:16 +0100
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Great, this is quite exactly what I had in mind. Thanks.
(Of course I still cannot compile MonetDB on our new
machine, but I already asked the respective person to
install Python there.)
## Comment 4467
Date: 2005-11-18 12:20:52 +0100
From: @drstmane
Logged In: YES
user_id=572415
Yep, python is indeed required to compile MonetDB et al. ---
at least from the CVS sources.
From the source tarball/source rpm, it might (haven't
checked, sorry) be possible without python, since bootstrap
and thus autogen is not required; the (other) buildtools
(Mx, mel, burg) are (still) required, though (it's on out
todo list (1) to produce both binary and source packages for
buildtools, and (2) to make the source distributions compile
without the buildtools --- however, since this is not
highest priority right now, there is no schedule/deadline
for these tasks...).
If you have python installed on your new machine, be sure
that also the respective development packages are installed.
## Comment 4468
Date: 2005-12-20 11:43:03 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / COMPILATION
## Comment 4469
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1359102 at http://sourceforge.net/support/tracker.php?aid=1359102
| buildtools: configure doesn't complain if python isn't avail | https://api.github.com/repos/MonetDB/MonetDB/issues/773/comments | 0 | 2020-11-30T08:58:06Z | 2024-06-27T11:07:33Z | https://github.com/MonetDB/MonetDB/issues/773 | 753,288,075 | 773 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-17 05:26:26 +0100
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2005-11-25 12:00:43 +0100
## Comment 4455
Date: 2005-11-17 17:26:26 +0100
From: @drstmane
Since yesterday's "yytree" optimization (and related
changes/checkins), the following tests
segfaul in join(), sort_ht(), and/or print();
all on the same set of platforms:
F4 G32/32d: Fedora Core4, GNU, 32bit, 32bit OIDs
G1.6.13 G32/32d: Gentoo 1.6.13, GNU, 32bit, 32bit OIDs
I646.5 G64/64d: IRIX64 6.5, GNU, 64bit, 64bit OIDs
R4 G64/64d: RedHat 4WS, GNU, 64bit, 64bit OIDs
S5.8 G64/64d: SunOS 5.8, GNU, 64bit, 64bit OIDs
S5.8 n64/64d: SunOS 5.8, ntv, 64bit, 64bit OIDs
S9.3 G32/32d: SuSE 9.3, GNU, 32bit, 32bit OIDs
as usual, see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/index_short.html
for details:
src/modules/plain/Tests/algebra_PROCs.*
src/modules/plain/Tests/decimal.*
src/monet/Tests/setaggr_exist.*
tests/Availability/Tests/02_Modules_contrib.*
tests/Availability/Tests/02_Modules_plain.*
tests/Availability/Tests/09_Modules_UNKNOWN.*
tests/BugDay_2005-11-09_4.9.3/Tests/tcpip_hangs_on_close.SF-1070569.*
tests/BugReports/Tests/no.171.*
tests/by_Peter/Tests/GNATS-2736.*
tests/sigs/Tests/none.*
tests/suite_00/Tests/test_10.*
## Comment 4456
Date: 2005-11-17 18:43:06 +0100
From: @drstmane
Logged In: YES
user_id=572415
all these segfaults occur in
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208964192 (LWP 29319)]
0x00a10f0a in yycopy (t=0x9970714, kill_orig=0,
func_parent=0, next=0xbff27b44, end=0xbff27b40)
at
/ufs/manegold/_/scratch0/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:200
200 assert(ATOMextern(t->yyval.vtype) == 0);
(gdb) li
195 /* function exec nodes (opcache) may be
extended later; usually are 1 wide */
196 func_parent = (t->token == TOK_FUNCTION ||
t->token == TOK_SETOP || t->token == TOK_SETAGGR);
197
198 tn->cnt = t->cnt;
199 if (t->noyyval) {
200 assert(ATOMextern(t->yyval.vtype) == 0);
201 } else {
202 tn->yyval = t->yyval;
203 if (kill_orig) {
204 /* steal the memory from the
copied node */
(gdb) print t->yyval.vtype
$1 = 160965380
(gdb)
vtype=160965380 looks indeed suspicious to me ...
## Comment 4457
Date: 2005-11-17 19:15:18 +0100
From: @drstmane
Logged In: YES
user_id=572415
Docu says:
src/monet/monet.mx:162:
noyyval:1, /* yyval part is not
allocated => BEWARE: first 16 bytes bogus */
and
src/monet/yytree.mx:89-93:
So, one may get a YSSTREE pointer t, but iff (t->noyyval ==
1) then the
t->yyval field is not there and it actually contains the end
part of
the previous node in the chunk (the first node from a chunk
always
allocates a t->yyval to avoid some memory debugging tools
detecting
use of illegal pointers).
but code says
src/monet/yytree.mx:199-201:
if (t->noyyval) {
assert(ATOMextern(t->yyval.vtype) == 0);
} else {
i.e., t->yyval is accessed also t->noyyval indicates that
t->yyval is not set !???
However, changing
if (t->noyyval) {
to
if (!t->noyyval) {
yields
$ Mserver
Monet Database Server V4.9.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for i686-redhat-linux-gnu/32bit with 32bit OIDs;
dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
Mserver:
/ufs/manegold/_/scratch0/Monet/Testing/Current/MonetDB/src/monet/yytree.mx:200:
yycopy: Assertion `(BATatoms[t->yyval.vtype].storage >= 11)
== 0' failed.
Aborted
|-(
... giving up, maybe Peter knows what's wrong ...
## Comment 4458
Date: 2005-11-17 21:45:20 +0100
From: @mlkersten
Logged In: YES
user_id=490798
No need to say more.
## Comment 4459
Date: 2005-11-20 18:36:08 +0100
From: @drstmane
Logged In: YES
user_id=572415
According to the TestWeb, this looks fixed to me.
Peter,
could you please check/confirm, and in case it's indeed
fixed, mark this report "fixed" and close it?
Thanks in advance.
Stefan
## Comment 4460
Date: 2005-11-25 00:00:43 +0100
From: @peterboncz
Logged In: YES
user_id=591107
all fixed
## Comment 4461
Date: 2005-12-20 11:42:45 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB
## Comment 4462
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1359087 at http://sourceforge.net/support/tracker.php?aid=1359087
| tests segfault on some platforms after "yytree" changes | https://api.github.com/repos/MonetDB/MonetDB/issues/772/comments | 0 | 2020-11-30T08:58:02Z | 2024-06-27T11:07:33Z | https://github.com/MonetDB/MonetDB/issues/772 | 753,288,021 | 772 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-17 05:13:35 +0100
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2005-11-25 12:00:05 +0100
## Comment 4450
Date: 2005-11-17 17:13:35 +0100
From: @drstmane
Since yesterday's "yytree" optimization (and related
changes/checkins), the following tests fail on all
platforms; as usual, see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/index_short.html
for details:
src/modules/plain/Tests/aggrX3.*:
several "!ERROR: BBPreclaim: 29 refs > 1 (2)"
tests/BugsViaSourgeforce/Tests/ID.1023816.*:
table(x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x,x);
yields
!Mtimeout: Segmentation fault (11): Mserver
--config=/export/scratch0/monet/monet.GNU.64.64.d.9068/MonetDB/Fedora4/conf/MonetDB.conf
--debug=10 --set
monet_mod_path=/export/scratch0/monet/monet.GNU.64.64.d.9068/MonetDB/Fedora4/src/modules/plain/.libs:/export/scratch0/monet/monet.GNU.64.64.d.9068/MonetDB/Fedora4/src/modules/contrib/.libs:/export/scratch0/monet/monet.GNU.64.64.d.9068/MonetDB/Fedora4/src/modules/calibrator/.libs:/export/scratch0/monet/monet.GNU.64.64.d.9068/MonetDB/Fedora4/src/modules/mnetcdf/.libs:/export/scratch0/monet/monet.GNU.64.64.d.9068/MonetDB/Fedora4/src/mapi/.libs
--set
gdk_dbfarm=/export/scratch0/monet/monet.GNU.64.64.d.9068/MonetDB/Fedora4/dbfarm
--set
sql_logdir=/export/scratch0/monet/monet.GNU.64.64.d.9068/MonetDB/Fedora4/log
--set mapi_port=36329 --set sql_port=48959 --set
xquery_port=54072 --set monet_prompt= --trace
--dbname=mTests_tests_BugsViaSourgeforce
tests/by_Peter/Tests/evenheight.*:
test output end prematurly without error message;
"silent" server crash/exit?
tests/by_Peter/Tests/table_orderby.*:
*** glibc detected ***
/export/scratch0/monet/monet.GNU.64.64.d.9068/MonetDB/Fedora4/src/tools/.libs/lt-Mserver:
free(): invalid pointer: 0x00002aaab4bfaff8 ***
(see Backtrace in attaced file
## Comment 4451
Date: 2005-11-20 18:33:37 +0100
From: @drstmane
Logged In: YES
user_id=572415
According to the TestWeb, this looks fixed to me.
Peter,
could you please check/confirm, and in case it's indeed
fixed, mark this report "fixed" and close it?
Thanks in advance.
Stefan
## Comment 4452
Date: 2005-11-25 00:00:04 +0100
From: @peterboncz
Logged In: YES
user_id=591107
fixed
## Comment 4453
Date: 2005-12-20 11:42:33 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB
## Comment 4454
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1359071 at http://sourceforge.net/support/tracker.php?aid=1359071
| various tests fail on all platforms after "yytree" changes | https://api.github.com/repos/MonetDB/MonetDB/issues/771/comments | 0 | 2020-11-30T08:57:59Z | 2024-06-27T11:07:32Z | https://github.com/MonetDB/MonetDB/issues/771 | 753,287,985 | 771 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-16 05:23:29 +0100
From: @yzchang
To: @sjoerdmullender
Version: -- development
Last updated: 2005-11-22 12:41:16 +0100
## Comment 4446
Date: 2005-11-16 17:23:29 +0100
From: @yzchang
We need some adjusting in SQL as well:
../../../../src/backends/monet4/sql_server.mx: In
function 'reset_arg_tree':
../../../../src/backends/monet4/sql_server.mx:299:
error: 'struct YYS' has no member named 'overflow'
make[5]: *** [lib_sql_server_la-sql_server.lo] Error 1
make[5]: Leaving directory
`/ufs/zhang/src/sql/build/src/backends/monet4'
make[4]: *** [all] Error 2
make[4]: Leaving directory
`/ufs/zhang/src/sql/build/src/backends/monet4'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/ufs/zhang/src/sql/build/src/backends'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/ufs/zhang/src/sql/build/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/ufs/zhang/src/sql/build'
make: *** [all] Error 2
## Comment 4447
Date: 2005-11-22 12:41:16 +0100
From: @drstmane
Logged In: YES
user_id=572415
This one has long been fixed by Niels.
## Comment 4448
Date: 2005-12-20 08:18:22 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / COMPILATION
## Comment 4449
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1358222 at http://sourceforge.net/support/tracker.php?aid=1358222
| Failed to compile SQL | https://api.github.com/repos/MonetDB/MonetDB/issues/770/comments | 0 | 2020-11-30T08:57:56Z | 2024-06-27T11:07:31Z | https://github.com/MonetDB/MonetDB/issues/770 | 753,287,949 | 770 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-15 02:00:36 +0100
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-11-26 12:57:20 +0100
## Comment 4440
Date: 2005-11-15 14:00:36 +0100
From: @grobian
Regardless what moment and when the function now() is
being called, it never returns fractional seconds:
sql>select now();
3 querytype
table_name
current_timestamp name
timestamptz type
19 length
1 tuplecount
0 id
[ 2005-11-15 12:59:16.000+00:00 ]
sql>select now();
3 querytype
table_name
current_timestamp name
timestamptz type
19 length
1 tuplecount
0 id
[ 2005-11-15 12:59:19.000+00:00 ]
Also note that by default now() should return 6
fractional seconds instead of 3.
## Comment 4441
Date: 2005-11-26 00:57:18 +0100
From: @njnes
Logged In: YES
user_id=43556
some test for this bug exist.
The now (current_timestamp) function had precision of
seconds only now its milliseconds. We need a large type for
microseconds....
## Comment 4442
Date: 2005-12-20 08:17:23 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
## Comment 4443
Date: 2005-12-20 11:25:20 +0100
From: @drstmane
Logged In: YES
user_id=572415
"stupid" question: which existing test covers this bug?
## Comment 4444
Date: 2005-12-20 20:58:49 +0100
From: @njnes
Logged In: YES
user_id=43556
included in test
timestamp_fraction.SF-1357342.sql
## Comment 4445
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1357347 at http://sourceforge.net/support/tracker.php?aid=1357347
| SQL: now() doesn't contain fractional seconds values | https://api.github.com/repos/MonetDB/MonetDB/issues/769/comments | 0 | 2020-11-30T08:57:53Z | 2024-06-27T11:07:30Z | https://github.com/MonetDB/MonetDB/issues/769 | 753,287,915 | 769 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-15 01:57:19 +0100
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-01-15 12:34:39 +0100
## Comment 4430
Date: 2005-11-15 13:57:19 +0100
From: @grobian
Consider the following scenario:
sql>create table t (t1 timestamp, t2 timestamp(0), t3
timestamp(3));
6 querytype
sql>insert into t values (now(), now(), now());
4 querytype
[ 1 ]
sql>select * from t;
3 querytype
t, t, t table_name
t1, t2, t3 name
timestamp, timestamp, timestamp type
19, 19, 26 length
1, , tuplecount
0, , id
[ 2005-11-15 12:50:58.000, 2005-11-15
12:50:58.000, 2005-11-15 12:50:58.000 ]
According to me (and the Big Book is with me on that)
the result should have been:
[ 2005-11-15 12:50:58.000000, 2005-11-15 12:50:58,
2005-11-15 12:50:58.000 ]
## Comment 4431
Date: 2005-11-26 00:46:48 +0100
From: @njnes
Logged In: YES
user_id=43556
Test file is added, and correctly runs
The internal cast functions return nil if the input isn't
parsable. So we now wrap these functions and test for nil.
## Comment 4432
Date: 2005-12-20 08:19:13 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
## Comment 4433
Date: 2005-12-20 11:24:25 +0100
From: @drstmane
Logged In: YES
user_id=572415
"stupid" question: which existing test covers this bug?
## Comment 4434
Date: 2005-12-20 20:54:39 +0100
From: @njnes
Logged In: YES
user_id=43556
Added new test Tests/timestamp_fraction.SF-1357342.sql
Seems my remark on 2005-11-25 was before the test was added.
## Comment 4435
Date: 2005-12-20 23:53:29 +0100
From: @drstmane
Logged In: YES
user_id=572415
re-opened as the respective test fails, cf. e.g.:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d-Fedora4/src_test_BugDay_2005-12-19_2.9.3/timestamp_fraction.SF-1357342.out.00.html
(as of tomorrow...)
## Comment 4436
Date: 2005-12-23 23:42:49 +0100
From: @grobian
Logged In: YES
user_id=963970
increasing priority as it is a rather crucial bug.
## Comment 4437
Date: 2005-12-25 10:45:01 +0100
From: @njnes
Logged In: YES
user_id=43556
This is a bug in the cast/convert implementation. A proper
implementation for cast from temporal values to strings is
missing. Such a cast function requires alot of information
such a timezone of the client, temporal type (with or without
time zone), number of fractional seconds and maximum length
of the result string. This doesn't match the current simple
convert interface, ie. its another special case (like the
current interval implementation now).
## Comment 4438
Date: 2006-01-15 12:34:39 +0100
From: @grobian
Logged In: YES
user_id=963970
bug is fixed, closing.
## Comment 4439
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1357342 at http://sourceforge.net/support/tracker.php?aid=1357342
| SQL: timestamp doesn't obey fractional seconds precision | https://api.github.com/repos/MonetDB/MonetDB/issues/768/comments | 0 | 2020-11-30T08:57:50Z | 2024-06-27T11:07:29Z | https://github.com/MonetDB/MonetDB/issues/768 | 753,287,880 | 768 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-15 01:48:10 +0100
From: @grobian
To: @njnes
Version: -- development
Last updated: 2011-01-31 14:49:12 +0100
## Comment 4424
Date: 2005-11-15 13:48:10 +0100
From: @grobian
Consider the following example from the big book (p.205):
monetdb-> select extract (second from interval
'-05:01:22.01' hour to second);
+---------------------+
| second_single_value |
+=====================+
| -22 |
+---------------------+
1 row
monetdb->
MonetDB should have returned instead:
-22.01
For any datetime_field other than SECOND, EXTRACT
returns an integer. For a datatime_field of SECOND,
EXTRACT returns a decimal number. (for the milli- and
microseconds)
## Comment 4425
Date: 2005-11-26 00:59:29 +0100
From: @njnes
Logged In: YES
user_id=43556
This will require some more work. The current seconds are in
reall seconds, ie not in milli or even micro seconds.
## Comment 4426
Date: 2005-12-20 08:12:54 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: TEST ADDED / FAILURE
interval_milliseconds.SF-1357338.sql
## Comment 4427
Date: 2006-01-15 12:36:02 +0100
From: @grobian
Logged In: YES
user_id=963970
this is more of a feature request
## Comment 4428
Date: 2006-06-06 21:10:40 +0200
From: @grobian
Logged In: YES
user_id=963970
WONTFIX/CANTFIX
## Comment 4429
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1357338 at http://sourceforge.net/support/tracker.php?aid=1357338
## Comment 15446
Date: 2011-01-31 14:49:12 +0100
From: @grobian
Created attachment 51
seconds double patch
for the record, the incomplete patch I once created
> Attached file: [seconds_double.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_767_seconds_double.patch_51) (text/plain, 4491 bytes)
> Description: seconds double patch
| SQL: EXTRACT returns wrong answer for SECOND | https://api.github.com/repos/MonetDB/MonetDB/issues/767/comments | 0 | 2020-11-30T08:57:46Z | 2024-06-28T07:36:43Z | https://github.com/MonetDB/MonetDB/issues/767 | 753,287,845 | 767 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-15 12:37:10 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2007-01-20 11:48:02 +0100
## Comment 4414
Date: 2005-11-15 12:37:10 +0100
From: @grobian
When the client is in a session with the server, and
the server hits a GDKmalloc failure, this message is
sent to the server as is (i.e. without error prefix (!).
Example message:
GDKmalloc(4194304) fail => BBPtrim(enter) usage
[mem=634350178,vm=67108864]
## Comment 4415
Date: 2005-12-20 08:08:09 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST /
Protocol is checked by any mapi/jdbc client
## Comment 4416
Date: 2006-01-21 00:06:46 +0100
From: @njnes
Logged In: YES
user_id=43556
Currently there is no warning/debugging header, such as the
errors '!'. We first need to introduce such a character and
change/check all THRprint calls. Lowering the priority.
Assigning to fabian for defining this change to mapi.
## Comment 4417
Date: 2006-06-06 21:09:10 +0200
From: @grobian
Logged In: YES
user_id=963970
should be on our todo's again...
## Comment 4418
Date: 2006-06-06 23:35:48 +0200
From: @mlkersten
Logged In: YES
user_id=490798
The specific errors are easily trapped in gdk_utils.mx.
The real problem is that THRprintf is called in many places
subject to a debugging flag being set. This may cause
'garbage' to be sent over the line.
A total of around 300 THRprintfs should be checked.
It takes a few hours to inject '!' in all places.
## Comment 4419
Date: 2006-06-11 18:40:01 +0200
From: @mlkersten
Logged In: YES
user_id=490798
Checked gdk_utils.mx for direct THRprintf that should have
included a ! to designate an error.
Check results in testweb tomorrow.
## Comment 4420
Date: 2006-11-05 20:37:13 +0100
From: @mlkersten
Logged In: YES
user_id=490798
It seems the 200 cases in GDK can be handled, provided we have
a clear policy. Now, debugging/error messages are sent both to
GDKout and GDKerr.
I propose to sent output intended for GDKout with a ''
and all for GDKerr with a '!'
This way trace information also goes to MapiClient, rather
then the server console.
It is up to the MapiClient implementation(or front-end) to
filter the relevant data.
## Comment 4421
Date: 2006-11-05 22:00:33 +0100
From: @grobian
Logged In: YES
user_id=963970
That's fine with me, and should work nicely with the latest
changes to the protocol.
## Comment 4422
Date: 2007-01-20 23:48:02 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
NO TEST NEEDED
There have been no reported errors and further code developments
should continuously be aware of proper marking errors.
## Comment 4423
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1357294 at http://sourceforge.net/support/tracker.php?aid=1357294
| MAPI: protocol violation on GDKmalloc failure | https://api.github.com/repos/MonetDB/MonetDB/issues/766/comments | 0 | 2020-11-30T08:57:43Z | 2024-06-27T11:07:26Z | https://github.com/MonetDB/MonetDB/issues/766 | 753,287,808 | 766 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-15 12:04:06 +0100
From: Steffen Goeldner <<sgoeldner>>
To: @njnes
Version: -- development
Last updated: 2005-11-26 01:06:28 +0100
## Comment 4410
Date: 2005-11-15 12:04:06 +0100
From: Steffen Goeldner <<sgoeldner>>
OS: Windows 2000
Compiler: MS VC++ Toolkit 2003
Parser tools: UnxUtils
sql>select cast( 1 as varchar(10));
MAPI = monetdb@localhost:45123
ACTION= read_line
QUERY = select cast( 1 as varchar(10));
ERROR = Connection terminated
## Comment 4411
Date: 2005-11-26 01:06:28 +0100
From: @njnes
Logged In: YES
user_id=43556
Test src/test/BugTracker/Tests/crash_on_cast.SF-1357271.sql
added, which now runs successfully
The truncate function lookup failed in the cast
implementation. This is now checked correctly.
## Comment 4412
Date: 2005-12-20 08:05:35 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
src/test/BugTracker/Tests/crash_on_cast.SF-1357271.sql
## Comment 4413
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1357271 at http://sourceforge.net/support/tracker.php?aid=1357271
| SQL: crash: select cast( 1 as varchar(10)) | https://api.github.com/repos/MonetDB/MonetDB/issues/765/comments | 0 | 2020-11-30T08:57:40Z | 2024-06-27T11:07:25Z | https://github.com/MonetDB/MonetDB/issues/765 | 753,287,779 | 765 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-14 02:50:51 +0100
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-02-07 11:54:22 +0100
## Comment 4406
Date: 2005-11-14 14:50:51 +0100
From: @grobian
When the server has no client slots available any more
it puts the client in a slot somewhere and never serves
it, causing the client to lock and wait indefenitely
for the server to start talking.
A better solution would be for the server to reject
such connections on TCP level, or protocol connection,
e.g. by sending an error and closing the connection.
(!Maximum clients reached)
## Comment 4407
Date: 2005-12-20 08:04:20 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / POSTPONED
needs some thinking about a proper test script
## Comment 4408
Date: 2006-02-07 23:54:22 +0100
From: @njnes
Logged In: YES
user_id=43556
A new connection gets a new client/thread (if none is
cached) now. If we run out of client slots the connection is
directly closed.
## Comment 4409
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1356568 at http://sourceforge.net/support/tracker.php?aid=1356568
| MAPI: New connections get stuck instead of rejected | https://api.github.com/repos/MonetDB/MonetDB/issues/764/comments | 0 | 2020-11-30T08:57:37Z | 2024-06-27T11:07:24Z | https://github.com/MonetDB/MonetDB/issues/764 | 753,287,745 | 764 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-14 02:31:53 +0100
From: @grobian
To: @njnes
Version: -- development
Last updated: 2006-01-24 08:50:41 +0100
## Comment 4400
Date: 2005-11-14 14:31:53 +0100
From: @grobian
(pegasus:current/sql/src) fabian% run_monet_sql --set
mapi_clien1970-01-01 01:01:02 +0100
Monet Database Server V4.9.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>!FATAL: THRnew: too many threads
It is impossible to allow more than 61 concurrent
connections to the database. This might be possible to
communicate to the user without terminating the server,
for instance using a warning.
## Comment 4401
Date: 2005-12-20 08:03:09 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / POSTPONED
This requires bash/bat scripts or changes to mtest
## Comment 4402
Date: 2006-01-15 14:45:40 +0100
From: @grobian
Logged In: YES
user_id=963970
this problem still persists on todays version. Any decision
on how to solve it? Server termination still feels a bit
too aggressive to me.
This bug is also related to MAPI: New connections get stuck
instead of rejected
http://sourceforge.net/tracker/index.php?func=detail&aid=1356568&group_id=56967&atid=482468
## Comment 4403
Date: 2006-01-24 08:50:41 +0100
From: @njnes
Logged In: YES
user_id=43556
Instead of exiting with a fatal error, we now adjust
mapi_clients to the maximum of available threads and give a
warning.
## Comment 4404
Date: 2006-01-25 10:50:25 +0100
From: @grobian
Logged In: YES
user_id=963970
great. In monet_daemon=yes mode, you even can't get higher
than 12 threads!!!
## Comment 4405
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1356552 at http://sourceforge.net/support/tracker.php?aid=1356552
| MAPI: setting mapi_clients property too high terminates serv | https://api.github.com/repos/MonetDB/MonetDB/issues/763/comments | 0 | 2020-11-30T08:57:33Z | 2024-06-27T11:07:23Z | https://github.com/MonetDB/MonetDB/issues/763 | 753,287,696 | 763 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-13 10:10:41 +0100
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-11-26 06:24:45 +0100
## Comment 4395
Date: 2005-11-13 22:10:41 +0100
From: @grobian
While trying to sign up with the DVDstore application,
I found out that I didn't enter my Age the hard way.
monetdb-> start transaction;
auto commit mode: off
monetdb-> create table test (age smallint);
Operation successful
monetdb-> insert into test values ('');
Error: ERROR: str_2_sht: operation failed.
monetdb-> rollback;
auto commit mode: on
monetdb->
The error message is a bit vague, although correct.
PostgreSQL does:
forum=> start transaction;
START TRANSACTION
forum=> create table test (age smallint);
CREATE TABLE
forum=> insert into test values ('');
ERROR: invalid input syntax for integer: ""
forum=> rollback;
ROLLBACK
forum=>
Maybe the error message can be made a bit more clear?
Would be great to have the column name included also.
## Comment 4396
Date: 2005-11-26 01:12:48 +0100
From: @njnes
Logged In: YES
user_id=43556
Test script added. Error message may still need some work.
Problem is these are dynamic (mil level) messages, which are
hard to make specific/clear on the sql level.
## Comment 4397
Date: 2005-11-26 18:24:45 +0100
From: @njnes
Logged In: YES
user_id=43556
Improved the error message of the str_2_* functions.
## Comment 4398
Date: 2005-12-20 07:57:48 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
/src/test/BugTracker/Tests/string2int_conversion.SF-1356068
## Comment 4399
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1356068 at http://sourceforge.net/support/tracker.php?aid=1356068
| SQL: String to Int conversion | https://api.github.com/repos/MonetDB/MonetDB/issues/762/comments | 0 | 2020-11-30T08:57:30Z | 2024-06-27T11:07:22Z | https://github.com/MonetDB/MonetDB/issues/762 | 753,287,666 | 762 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-11 08:07:38 +0100
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2005-11-12 09:57:10 +0100
## Comment 4391
Date: 2005-11-11 20:07:38 +0100
From: @mlkersten
The LIMIT clause is improperly parsed.
Consider the VOC database example:
select * from soldiers limit5;
so concatenate the limit and the number!
then you don't get a parser error and all tuples
are returned to the user.
## Comment 4392
Date: 2005-11-12 09:57:09 +0100
From: @grobian
Logged In: YES
user_id=963970
this is an invalid bug.
What you actually do, is make use of the SQL99 'feature' to
alias a table without using "AS". You just alias soldiers
as limit5 in this example.
## Comment 4393
Date: 2005-12-20 07:55:50 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / INVALID BUG
## Comment 4394
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1354321 at http://sourceforge.net/support/tracker.php?aid=1354321
| SQL: parse error in LIMIT | https://api.github.com/repos/MonetDB/MonetDB/issues/761/comments | 0 | 2020-11-30T08:57:27Z | 2024-06-28T07:36:43Z | https://github.com/MonetDB/MonetDB/issues/761 | 753,287,638 | 761 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-11 01:12:20 +0100
From: Jan Rittinger <<jan.rittinger>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-11-14 09:30:54 +0100
## Comment 4385
Date: 2005-11-11 13:12:20 +0100
From: Jan Rittinger <<jan.rittinger>>
Stefan,
with your commit of version 1.106 of milprint_summer.c
you overwrote the changes introduced by 1.105
(distinct-doc-order coping with attributes).
## Comment 4386
Date: 2005-11-11 18:22:13 +0100
From: @drstmane
Logged In: YES
user_id=572415
Jan,
thanks for noticing, and sorry for the inconvenience.
I didn't notice this "accident", and actually have no idea,
how it could happen
(so far, I trusted cvs ...).
Anyway, I'll fix it as soon as I find some time and SF
grants me access to the cvs repository...
Stefan
## Comment 4387
Date: 2005-11-12 13:29:50 +0100
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS.
Jan,
could you please double-check, and close the bug if
everything's fine, again?
Thanks,
Stefan
## Comment 4388
Date: 2005-11-14 09:30:54 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
thx -- seems fine :)
## Comment 4389
Date: 2005-12-19 23:34:54 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / CODE
## Comment 4390
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1353883 at http://sourceforge.net/support/tracker.php?aid=1353883
| cvs checkin accidently overwrote changes | https://api.github.com/repos/MonetDB/MonetDB/issues/760/comments | 0 | 2020-11-30T08:57:24Z | 2024-06-27T11:07:20Z | https://github.com/MonetDB/MonetDB/issues/760 | 753,287,601 | 760 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-10 10:53:44 +0100
From: Jan Rittinger <<jan.rittinger>>
To: @njnes
Version: -- development
Last updated: 2006-01-20 12:44:05 +0100
## Comment 4375
Date: 2005-11-10 10:53:44 +0100
From: Jan Rittinger <<jan.rittinger>>
sorry, couldn't reproduce bug on a smaller query.
Attached script where crash occurs in line 1539
(Requirements are Monet and pf CVS head).
## Comment 4376
Date: 2005-11-10 16:47:56 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
sorry -- probably the same as http://sourceforge.net/support/tracker.php?aid=1340615
## Comment 4377
Date: 2005-11-20 20:23:41 +0100
From: @drstmane
Logged In: YES
user_id=572415
same problem as
1340615 "setting the access property on void|void bats does
not work"
cf.
http://sourceforge.net/tracker/index.php?func=detail&aid=1340615&group_id=56967&atid=482468
## Comment 4378
Date: 2005-11-25 00:59:05 +0100
From: @peterboncz
Logged In: YES
user_id=591107
the script does not work anymore as it depends on the fake
stuff so I can't check.
## Comment 4379
Date: 2005-11-25 13:46:26 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
same query is now evaluated without crash :)
## Comment 4380
Date: 2005-12-19 23:34:15 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
pathfinder/tests/BugsViaSourgeforce/Tests/making_void-void_BAT_writable.SF-1353017.milS
## Comment 4381
Date: 2005-12-21 00:24:27 +0100
From: @drstmane
Logged In: YES
user_id=572415
re-opened as the respective test fails:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/making_void-void_BAT_writable.SF-1353017.out.00.html
this is most probably releated to the other void|void
insert/append bugs
## Comment 4382
Date: 2006-01-18 09:54:38 +0100
From: @drstmane
Logged In: YES
user_id=572415
While the void issues are fixed, this one no results in
Mserver:
/export/scratch0/monet/monet.GNU.64.64.d.1432/pathfinder/runtime/pf_support.mx:1446:
CMDappendConvert: Assertion `t' failed.
somewhere in
a0000 := doc_tbl (ws, a0001);
or more precisely in
add_doc()
I saw the same error elsewhere earlier, but is was fixed bug
Peter's fixed of the on-the-fly shredding; I looked at the
test scrip, but didn't see any place to apply Peter's fixes
there (they did not include any changes to milprint_summer.c).
What did I miss?
Is it a different bug?
## Comment 4383
Date: 2006-01-20 00:44:05 +0100
From: @drstmane
Logged In: YES
user_id=572415
Lengthy debugging finally revealed that this test script
actually works.
The assertion is the result of the fact that the same
document ("tests/XMark/Tests/auctionG.xml") gets shredded
via "shred_doc()" in three tests in this directory. The
first one ("ID.1292727.col_name-segfault.shred") simply
shreds it. The second
("making_void-void_BAT_appendable.SF-1340615") and third
("making_void-void_BAT_writable.SF-1353017") one first
delete all documents from the database
("delete_all_docs(false); delete_all_docs(true);") before
shredding "tests/XMark/Tests/auctionG.xml".
While the first two tests run fine, the third one creates
the assertion. The same happens if the second or third test
are run twice after another on the same database.
To avoid problems with Pathfinder'\''s apparently completely
unstable "document managent", we now shred document
tests/XMark/Tests/auctionG.xml once in the first test
("auctionG_xml") in this directory and then simply re-use it
in the tests that required it.
The (heavily??) broken document management will be
documented in a new bug report --- but not tonight ---
already wasted^wspent too much time on this ...
## Comment 4384
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1353017 at http://sourceforge.net/support/tracker.php?aid=1353017
| access(BAT_WRITE) on a void|void bat crashes Mserver | https://api.github.com/repos/MonetDB/MonetDB/issues/759/comments | 0 | 2020-11-30T08:57:21Z | 2024-06-27T11:07:19Z | https://github.com/MonetDB/MonetDB/issues/759 | 753,287,552 | 759 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-09 09:19:59 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-11-20 06:01:27 +0100
## Comment 4370
Date: 2005-11-09 21:19:59 +0100
From: @drstmane
Since recent changes, the MIL command
xquery(str,str):str does not only return the expected
query results, but it also returns (or prints?) the
generated MIL code.
See (e.g.)
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/runtime/text1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1204965-c.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1205565-b.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1207029.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-11-09_0.8/boolean_dm.SF-1204097.out.00.html
## Comment 4371
Date: 2005-11-20 17:16:05 +0100
From: @drstmane
Logged In: YES
user_id=572415
Apparently, the problem only occurs if Mserver is started
with "--trace" to echo MIL commands that Mserver receives
via stdin on the console (this is quite handly for locating
bugs in long MIL scripts, that's why Mtest uses "--trace" by
default).
Apparently, this tracing/echoing/listing of the received MIL
code is now also triggered xquery(str,str):str since
xquery(str,str):str became a BUILTIN (was a COMMAND before).
Unfortunately, I failed to find out, where the echoing gets
triggered, and whether it could be switched off (again) for
xquery(str,str):str --- maybe someone could help??
Of course, we could simply approve also the echoed MIL, but
since this might change (often), this is IMHO no
(convenient) solution.
Neither is running Mtest without "--trace" and option, since
this would make Mtest less useful...
Any help is highly appreciated, since the current situation
makes the Mtest and the TestWeb more than tricky to use...
## Comment 4372
Date: 2005-11-20 18:01:27 +0100
From: @drstmane
Logged In: YES
user_id=572415
I "saw the light" and fixed (hacked?) is myself:
Index: runtime/pathfinder.mx
===================================================================
RCS file: /cvsroot/monetdb/pathfinder/runtime/pathfinder.mx,v
retrieving revision 1.124
diff -u -9 -r1.124 pathfinder.mx
--- runtime/pathfinder.mx 6 Nov 2005 22:02:35 -0000
1.124
+++ runtime/pathfinder.mx 20 Nov 2005 16:58:20 -0000
@@ -1025,24 +1025,27 @@
/*
* parse MIL buffer into a tree
*/
static YYSTREE
xquery_mil2tree(xquery_client *ctx, char* buf)
{
Client c = monet_clients + ctx->stk;
YYSTREE ret = NULL, treebak = c->tree;
char* bufbak = c->input;
+ int listing_bak = c->listing;
+ c->listing = 0;
c->input = buf;
c->tree = NULL;
if (parseClient(c, FALSE))
ret = c->tree;
c->tree = treebak;
c->input = bufbak;
+ c->listing = listing_bak;
return ret;
}
according to Mtest, this solves this bug, but does not cause
any harm to any other test.
## Comment 4373
Date: 2005-12-19 23:33:32 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB
## Comment 4374
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1352526 at http://sourceforge.net/support/tracker.php?aid=1352526
| PF: xquery(str,str):str returns/prints generated MIL code | https://api.github.com/repos/MonetDB/MonetDB/issues/758/comments | 0 | 2020-11-30T08:57:18Z | 2024-06-27T11:07:18Z | https://github.com/MonetDB/MonetDB/issues/758 | 753,287,522 | 758 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-08 06:10:45 +0100
From: @Teggy
To: Jens Teubner <<teubner>>
Version: -- development
CC: @sjoerdmullender, @drstmane
Last updated: 2011-05-03 10:37:14 +0200
## Comment 4356
Date: 2005-11-08 18:10:45 +0100
From: @Teggy
The query
<a>b{attribute c {"d"}}</a>
should yield XQTY0024 (an attribute node cannot be
created after the children of the containing element)
but constructs the element
<a c="d">b</a>
in Pathfinder.
(This is a type checking issue.)
Greetings,
--Teggy
## Comment 4357
Date: 2005-11-10 15:55:38 +0100
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
I have looked into this, and I've actually prepared
a fix for this in my working copy.
However, committing it would actually break more
than it fixes. Our current implementation of static
typing rules for XPath location steps apparently are
too simplistic.
We basically use the node test in the step as the
step's return type (.../child::text() leads to `text*',
.../child::foo leads to `element foo {...}*', etc.). This,
however, means that .../child::node() will have the
return type `node*', which no longer would be
accepted as the content in an element construction
operator. With my fix, any query of the form
element { ... } { .../node() }
is doomed to fail with a static type error.
What we need before actually implementing the
constraint is a more elaborated typing of XPath
location steps. We should definitely do that
anyway, but it is more than an afternoon's hack :(
## Comment 4358
Date: 2005-12-19 23:32:48 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / FAILURE:
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/attribute_after_non-attribute_content.SF-1351516.*
## Comment 4359
Date: 2006-01-19 23:51:52 +0100
From: @drstmane
Logged In: YES
user_id=572415
Jens,
just for the bookkeeping:
I guess, this won't be fixed/fixable for this release (i.e.,
before Sunday)?
## Comment 4360
Date: 2006-01-20 10:01:12 +0100
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
I'm afraid not.
It requires fixing the static type inference for XPath
location steps first, which is quite some work to do. We
were hoping to get a student here to work on this typing
stuff. One day I will have to do this myself...
## Comment 4361
Date: 2006-01-20 10:09:58 +0100
From: @drstmane
Logged In: YES
user_id=572415
Thanks, Jens.
I'll temorary reduce the "Priority" until the release is out...
## Comment 4362
Date: 2006-06-06 21:08:10 +0200
From: @grobian
Logged In: YES
user_id=963970
Jens, did you ( by chance 0:-) ) do this yourself already?
Feel free to reset flags if not :)
## Comment 4363
Date: 2006-06-11 12:25:19 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Sorry, Fabian, I did not.
Our static type inference does indeed need some overhaul.
This bug is one instance of our problems only. It is
definitely not a show-stopper, though, and I marked this as
"Later".
(We do have a student here who claimed interest. But he does
not want to start before the end of the semester. We'll see
...)
## Comment 4364
Date: 2007-02-19 18:12:00 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Is this going to be a "Won't Fix" or what?
## Comment 4365
Date: 2007-11-10 23:36:36 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
Please, confirm status
## Comment 4366
Date: 2008-01-22 14:39:54 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
This one is still an issue:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugDay_2005-12-19_0.9.3/attribute_after_non-attribute_content.SF-1351516.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugDay_2005-12-19_0.9.3/attribute_after_non-attribute_content.SF-1351516.err.00.html
## Comment 4367
Date: 2009-02-16 00:35:38 +0100
From: @drstmane
updated TestWeb URLs:
ALG:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugDay_2005-12-19_0.9.3/attribute_after_non-attribute_content.SF-1351516.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugDay_2005-12-19_0.9.3/attribute_after_non-attribute_content.SF-1351516.err.00.html
MPS:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugDay_2005-12-19_0.9.3/attribute_after_non-attribute_content.SF-1351516.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugDay_2005-12-19_0.9.3/attribute_after_non-attribute_content.SF-1351516.err.00.html
## Comment 4368
Date: 2009-11-11 19:48:33 +0100
From: @drstmane
===================================================================
2009/11/11 - stmane:
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/All,1.13.36.1
Disabled test that is bound to fail.
Please re-enable once bug is fixed.
cf.
ID: 1351516 "PF: attribute after non-attribute content"
https://sourceforge.net/tracker/index.php?func=detail&aid=1351516&group_id=56967&atid=482468
===================================================================
## Comment 4369
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1351516 at http://sourceforge.net/support/tracker.php?aid=1351516
## Comment 15779
Date: 2011-05-03 10:37:14 +0200
From: @drstmane
Development on MonetDB4 and MonetDB/XQuery has ceased. It is unlikely that
this bug will be fixed.
The last release of MonetDB/XQuery and MonetDB4 is Mar2011.
| PF: attribute after non-attribute content | https://api.github.com/repos/MonetDB/MonetDB/issues/757/comments | 0 | 2020-11-30T08:57:14Z | 2024-06-28T07:36:42Z | https://github.com/MonetDB/MonetDB/issues/757 | 753,287,488 | 757 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-07 04:36:18 +0100
From: @Teggy
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-06-08 06:54:19 +0200
## Comment 4343
Date: 2005-11-07 16:36:18 +0100
From: @Teggy
Dear friends,
the expression
<a>{text {()}}</a>/text()
yields text {""} while it should yield (): no text node
is constructed if its constructor's content sequence is
empty.
Also see 3.7.3.4 Text Node Constructors in the current
W3C XQuery CR.
Regards,
--Teggy
## Comment 4344
Date: 2005-11-07 17:05:31 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
This bug is already known (see KnownIssues) and won't be
fixed in the near future. The reason is that in June 2005
the working draft introduced new versions of
item-sequence-to-untypedAtomic that ask for special
treatment in case of constructors.
## Comment 4345
Date: 2005-12-19 23:23:48 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / FAILURE:
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/text_nodes_with_empty_content_seq.SF-1350418.*
the bug still occurs.
## Comment 4346
Date: 2006-11-08 04:20:01 +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 365 days (the time period specified by
the administrator of this Tracker).
## Comment 4347
Date: 2006-11-08 09:17:53 +0100
From: @Teggy
Logged In: YES
user_id=642632
This is still an issue. Keep your fingers off of it, filthy
SF robot.
;-)
--Teggy
## Comment 4348
Date: 2007-11-10 23:35:56 +0100
From: @mlkersten
Logged In: YES
user_id=490798
Originator: NO
That's over a year ago. It is still an issue?
## Comment 4349
Date: 2008-01-22 14:37:57 +0100
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
This one is still an issue:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora6/tests_BugDay_2005-12-19_0.9.3/text_nodes_with_empty_content_seq.SF-1350418.out.00.html
## Comment 4350
Date: 2008-06-02 12:56:39 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
problem occurs in
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQ_XMP/Q06.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQ_R/Q02.out.00.html
## Comment 4351
Date: 2008-06-02 21:16:09 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
problem also occurs in
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugDay_2005-12-19_0.9.3/non-existent_attribute.SF-1324219.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugTracker/interpret_while-bit_nil.SF-1567021.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_BugsViaSourgeforce/ID.1766173.out.00.html
## Comment 4352
Date: 2008-06-07 10:25:28 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
After more than 2,5 years this bug is finally fixed.
Pruning empty textnodes on the MIL level and respecting the optional semantics of the textnode constructor during the optimizations did the job.
text{"42"}/<a/> --> <a/>
text{""}/<a/> --> ()
<a>{text{"foo"}}</a> --> <a>foo</a>
<a>{text{""}}</a> --> <a/>
for $a in ("foo","","bar") return <a>{text{$a}}</a> --> <a>foo</a><a/><a>bar</a>
## Comment 4353
Date: 2008-06-08 16:16:35 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Re-opening as
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsG103/GNU.64.64.d-Fedora8/tests_W3C_use_cases_XQ_XMP/Q06.out.00.html
still seems to fail with ALG.
Jan, could you please have a quick look and comment?
With MPS, the originally reported bug still seems to exist:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora8/tests_BugDay_2005-12-19_0.9.3/text_nodes_with_empty_content_seq.SF-1350418.out.00.html
(extended version available as of tomorrow).
It is very likely, though, that MPS will no be fixed anymore.
## Comment 4354
Date: 2008-06-08 18:54:19 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Originator: NO
The failing tests_W3C_use_cases_XQ_XMP/Q06 query is unrelated to this bug... The cause for its incorrect output has been fixed in CVS though.
## Comment 4355
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1350418 at http://sourceforge.net/support/tracker.php?aid=1350418
| PF: text nodes with empty content sequence | https://api.github.com/repos/MonetDB/MonetDB/issues/756/comments | 0 | 2020-11-30T08:57:11Z | 2024-06-27T11:07:17Z | https://github.com/MonetDB/MonetDB/issues/756 | 753,287,445 | 756 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-05 03:13:22 +0100
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2005-11-18 09:43:49 +0100
## Comment 4337
Date: 2005-11-05 15:13:22 +0100
From: @drstmane
runtime/shredder.mx now uses macro
"XML_PARSE_NOXINCNODE" and hence fail to compile if the
respective libxml2-dev[el] package (and hence
libxml2/libxml/parser.h) is not installed/available, or
if it is available but from and libxml2 < v2.6.12.
"XML_PARSE_NOXINCNODE" is defined in
libxml2/libxml/parser.h only since libxml2 v2.6.12.
Instead of failing during compilation, configure should
properly check whether "XML_PARSE_NOXINCNODE" is
available, and otherwise abort compilation immediately
with a proper error message
(or compile runtime/shredder.mx without
"XML_PARSE_NOXINCNODE", in case this is an option).
Assigned to Peter, since he added
"XML_PARSE_NOXINCNODE" to runtime/shredder.mx, but of
course everybody else is just as welcome to fix this.
## Comment 4338
Date: 2005-11-05 15:15:47 +0100
From: @drstmane
Logged In: YES
user_id=572415
ps: in case you're curious, details can be found at
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.64.d-Debian3.0/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.64.d-SuSE9.3/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.64.d-SuSE9.3/make-k.out
## Comment 4339
Date: 2005-11-18 09:43:49 +0100
From: @peterboncz
Logged In: YES
user_id=591107
a simple check whether XML_PARSE_NOXINCNODE is defined was
added before passing it to the libxml2 call.
I don't think it it worthwhile to add configure logic for
this.
## Comment 4340
Date: 2005-11-18 10:22:30 +0100
From: @drstmane
Logged In: YES
user_id=572415
I agree with your solution, Peter, but when closing a bug
report, could you *please* also set the "Resolution:"
information?
I set it to "Fixed" for this bug report, hoping that this is
OK with you ...
Stefan
## Comment 4341
Date: 2005-12-19 23:18:27 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / COMPILATION
## Comment 4342
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1349031 at http://sourceforge.net/support/tracker.php?aid=1349031
| PF: runtime/shredder.mx fails to compile with libxml2<2.6.12 | https://api.github.com/repos/MonetDB/MonetDB/issues/755/comments | 0 | 2020-11-30T08:57:07Z | 2024-06-27T11:07:16Z | https://github.com/MonetDB/MonetDB/issues/755 | 753,287,413 | 755 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-04 10:59:05 +0100
From: Gustavo Hispagnol <<gmhispagnol>>
To: @njnes
Version: -- development
Last updated: 2005-11-09 08:58:29 +0100
## Comment 4331
Date: 2005-11-04 22:59:05 +0100
From: Gustavo Hispagnol <<gmhispagnol>>
Hi,
The SQL Group By does not work by position number,
this can be very limiting because expressions can not
be used to group either:
Example:
select a+b,sum(c) from d
group by 1
Note that the group by is refers to the position 1. To
overcome this limit I have to use a subquery:
select a_b,c from
(select a+b as a_b,sum(c) as c from d ) e
group by a_b
Any chances to get it fixed?
Best regards and thanks for your great job!
Gustavo
## Comment 4332
Date: 2005-11-04 23:05:17 +0100
From: @grobian
Logged In: YES
user_id=963970
maybe I just don't get it, but why can't you do:
select a + b as a_plus_b, sum(c) as sum_c from d
group by a_plus_b
Or am I missing something here?
## Comment 4333
Date: 2005-11-09 14:50:47 +0100
From: Gustavo Hispagnol <<gmhispagnol>>
Logged In: YES
user_id=818683
Ok, I didn´t notice the capability of grouping by a column
alias before. There are some DBs that does not support this
capability. Anyway, I guess grouping by a column position is
consistant with the order by syntax
## Comment 4334
Date: 2005-11-09 20:58:28 +0100
From: @njnes
Logged In: YES
user_id=43556
Grouping (or any other operation) by column position has
been depricated since sql'99. We therefor descided not too
implement this and instead support the alias. The group by
alias is also the prefered to solution by the sql standards.
BugDay_2005-11-09, Niels Nes: NO TEST / INVALID
## Comment 4335
Date: 2005-12-19 23:18:08 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / INVALID
## Comment 4336
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1348664 at http://sourceforge.net/support/tracker.php?aid=1348664
| SQL Group By does not work by position | https://api.github.com/repos/MonetDB/MonetDB/issues/754/comments | 0 | 2020-11-30T08:57:04Z | 2024-06-28T07:36:42Z | https://github.com/MonetDB/MonetDB/issues/754 | 753,287,361 | 754 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-04 02:15:27 +0100
From: @sjoerdmullender
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2007-12-21 04:20:04 +0100
## Comment 4324
Date: 2005-11-04 14:15:27 +0100
From: @sjoerdmullender
Executing test compiler/core/tests/fs/Tests/good-048.xq
results in the error:
!ERROR: XML Generation: idxTV, BAT[tmp/tmp_450]: 5 not
within [0,4]
ERROR: xquery_print_result_main: operation failed.
when run on the following document (also attached):
<bar xmlns="http://www.foo.bar/">
<baz/>
</bar>
When the interior element <baz/> is removed, there is
no error.
## Comment 4325
Date: 2005-11-04 22:39:30 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
In my version that doesn't include Peters latest changes the
query works fine. I added my MIL script - could you perhaps
compare it with your output?
## Comment 4326
Date: 2005-11-25 14:04:06 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
as their was no reaction and never occured in my setting -
this bug becomes invalid...
## Comment 4327
Date: 2005-12-19 23:36:25 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / POSTPONED:
maybe, we should eventually consider executing all "good"
tests in compiler// ...
## Comment 4328
Date: 2006-12-20 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 4329
Date: 2007-12-21 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 4330
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1348256 at http://sourceforge.net/support/tracker.php?aid=1348256
| PF: bug executing core test good-048.xq | https://api.github.com/repos/MonetDB/MonetDB/issues/753/comments | 0 | 2020-11-30T08:57:01Z | 2024-06-28T07:36:42Z | https://github.com/MonetDB/MonetDB/issues/753 | 753,287,320 | 753 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-04 02:07:51 +0100
From: @drstmane
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2005-11-18 06:49:27 +0100
## Comment 4319
Date: 2005-11-04 14:07:51 +0100
From: @drstmane
Triggered by some of the changes checked in on Friday,
Oct 28 2005,
test tests/XQuery/Tests/concat.xq fails.
See (e.g.)
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora3/tests_XQuery/concat.out.00.html
for details.
## Comment 4320
Date: 2005-11-04 22:49:50 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Sorry this is my bug. In my last checkin I forgot to test the
kind in the concat simplification rule of compiler/core/coreopt.
brg. If you want to have a fast fix replace case 48 by the fixed
code (quoted below). Otherwise you'll have to wait a little bit
longer until I cleaned up my code :)
fix:
/* CoreExpr: apply (arg (Atom, arg (Atom, nil))) */
case 48:
/*
* fn:concat does not need to append an empty string
*/
if (! PFqname_eq (p->sem.fun->qname,
PFqname (PFns_fn, "concat"))) {
if (LRL(p)->kind == c_lit_str && !strcmp (LRL(p)-
>sem.str,"")) {
*p = *LL(p);
rewritten = true;
break;
}
}
## Comment 4321
Date: 2005-11-18 18:49:27 +0100
From: @drstmane
Logged In: YES
user_id=572415
Bug appears to be fixed.
## Comment 4322
Date: 2005-12-19 23:16:41 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB
## Comment 4323
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1348252 at http://sourceforge.net/support/tracker.php?aid=1348252
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQuery: test tests/XQuery/Tests/concat.xq fails since 29.10. | https://api.github.com/repos/MonetDB/MonetDB/issues/752/comments | 0 | 2020-11-30T08:56:58Z | 2024-06-27T11:07:12Z | https://github.com/MonetDB/MonetDB/issues/752 | 753,287,297 | 752 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-03 11:38:37 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-11-04 01:27:37 +0100
## Comment 4315
Date: 2005-11-03 23:38:37 +0100
From: @drstmane
After yesterday's changes, pathfinder fails to compile
with various
compilers on various platforms:
icc 8.1:
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.ntv.64.64.d.24635/pathfinder/compiler
-I..
-I/var/tmp/monet.ntv.64.64.d.24635/pathfinder/compiler
-Iinclude
-I/var/tmp/monet.ntv.64.64.d.24635/pathfinder/compiler/include
-I/var/tmp/monet.ntv.64.64.d.24635/MonetDB/.ntv.64.64.d-RedHat4WS/include/MonetDB
-I/var/tmp/monet.ntv.64.64.d.24635/MonetDB/.ntv.64.64.d-RedHat4WS/include/MonetDB/common
-I/var/tmp/monet.ntv.64.64.d.24635/MonetDB/.ntv.64.64.d-RedHat4WS/include/MonetDB/gdk
-I/var/tmp/monet.ntv.64.64.d.24635/MonetDB/.ntv.64.64.d-RedHat4WS/include/MonetDB/monet
-I/var/tmp/monet.ntv.64.64.d.24635/MonetDB/.ntv.64.64.d-RedHat4WS/include/MonetDB/plain
-I/var/tmp/monet.ntv.64.64.d.24635/MonetDB/.ntv.64.64.d-RedHat4WS/include/MonetDB/contrib
-I/var/tmp/monet.ntv.64.64.d.24635/MonetDB/.ntv.64.64.d-RedHat4WS/include/MonetDB/mapi
-I/var/tmp/monet.ntv.64.64.d.24635/MonetDB/.ntv.64.64.d-RedHat4WS/include/MonetDB/C
-I/usr/include/libxml2 -DLIBCOMPILER1 -we140 -wd1418
-c99 -Wall -w2 -mp1 -O2 -restrict -unroll -tpp2
-mcpu=itanium2 -DHWCOUNTERS -DHW_Linux -DHW_ia64 -we266
-Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-c
/var/tmp/monet.ntv.64.64.d.24635/pathfinder/compiler/compile.c
-KPIC -DPIC -o .libs/libcompiler1_la-compile.o
/var/tmp/monet.ntv.64.64.d.24635/pathfinder/compiler/compile.c(159):
error 120: return value type does not match the
function type
return cache->buf->buffer->content;
^
/var/tmp/monet.ntv.64.64.d.24635/pathfinder/compiler/compile.c(187):
error 120: return value type does not match the
function type
return cache->buf->buffer->content;
^
compilation aborted for
/var/tmp/monet.ntv.64.64.d.24635/pathfinder/compiler/compile.c
(code 2)
make[3]: *** [libcompiler1_la-compile.lo] Error 1
gcc 4.0.1 on Fedora Core 4:
---------------------------
gcc -m64 -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/compiler
-I..
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/compiler
-Iinclude
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/compiler/include
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -DLIBCOMPILER1 -O2 -std=c99
-Wall -W -O6 -fomit-frame-pointer -finline-functions
-falign-loops=4 -falign-jumps=4 -falign-functions=4
-fexpensive-optimizations -funroll-loops
-frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -c
/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/compiler/compile.c
-fPIC -DPIC -o .libs/libcompiler1_la-compile.o
cc1: warnings being treated as errors
/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/compiler/compile.c:
In function ‘PFurlcache’:
/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/compiler/compile.c:159:
warning: pointer targets in return differ in signedness
/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/compiler/compile.c:187:
warning: pointer targets in return differ in signedness
make[3]: *** [libcompiler1_la-compile.lo] Error 1
gcc -m64 -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/runtime
-I..
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/runtime
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/common
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/gdk
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/monet
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/plain
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/contrib
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/mapi
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-Fedora4/include/MonetDB/C
-I/usr/include/libxml2 -I../compiler/include
-I/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/runtime/../compiler/include
-DLIBPATHFINDER -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer -finline-functions -falign-loops=4
-falign-jumps=4 -falign-functions=4
-fexpensive-optimizations -funroll-loops
-frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -c pathfinder.c
-fPIC -DPIC -o .libs/lib_pathfinder_la-pathfinder.o
cc1: warnings being treated as errors
/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/runtime/pathfinder.mx:
In function ‘xquery_prepare’:
/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/runtime/pathfinder.mx:2801:
warning: pointer targets in passing argument 1 of
‘xquery_parse_ident’ differ in signedness
/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/runtime/pathfinder.mx:2840:
warning: pointer targets in passing argument 1 of
‘xquery_parse_ident’ differ in signedness
/export/scratch0/monet/monet.GNU.64.64.d.24635/pathfinder/runtime/pathfinder.mx:2845:
warning: pointer targets in passing argument 1 of
‘xquery_parse_ident’ differ in signedness
make[3]: *** [lib_pathfinder_la-pathfinder.lo] Error 1
gcc 3.3 on SuSE 9.3 & Debian 3.0 (64bit):
-----------------------------------------
gcc -m64 -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.64.64.d.24635/pathfinder/runtime
-I..
-I/var/tmp/monet.GNU.64.64.d.24635/pathfinder/runtime
-I/var/tmp/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-SuSE9.3/include/MonetDB
-I/var/tmp/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-SuSE9.3/include/MonetDB/common
-I/var/tmp/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-SuSE9.3/include/MonetDB/gdk
-I/var/tmp/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-SuSE9.3/include/MonetDB/monet
-I/var/tmp/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-SuSE9.3/include/MonetDB/plain
-I/var/tmp/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-SuSE9.3/include/MonetDB/contrib
-I/var/tmp/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-SuSE9.3/include/MonetDB/mapi
-I/var/tmp/monet.GNU.64.64.d.24635/MonetDB/.GNU.64.64.d-SuSE9.3/include/MonetDB/C
-I/soft/64/libxml2-2.6.10/include/libxml2
-I../compiler/include
-I/var/tmp/monet.GNU.64.64.d.24635/pathfinder/runtime/../compiler/include
-DLIBPF_SUPPORT -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer -finline-functions -falign-loops=4
-falign-jumps=4 -falign-functions=4
-fexpensive-optimizations -funroll-loops
-frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-strict-aliasing -c shredder.c -fPIC -DPIC -o
.libs/lib_pf_support_la-shredder.o
/var/tmp/monet.GNU.64.64.d.24635/pathfinder/runtime/shredder.mx:
In function `MainSHREDDER':
/var/tmp/monet.GNU.64.64.d.24635/pathfinder/runtime/shredder.mx:1606:
error: `XML_PARSE_NOXINCNODE' undeclared (first use in
this function)
/var/tmp/monet.GNU.64.64.d.24635/pathfinder/runtime/shredder.mx:1606:
error: (Each undeclared identifier is reported only once
/var/tmp/monet.GNU.64.64.d.24635/pathfinder/runtime/shredder.mx:1606:
error: for each function it appears in.)
make[3]: *** [lib_pf_support_la-shredder.lo] Error 1
see also:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.Makes3/index_short.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.64.d-Fedora4/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.64.d-Fedora4/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.64.d-Debian3.0/make-k.out
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.64.d-SuSE9.3/make-k.out
## Comment 4316
Date: 2005-11-04 13:27:37 +0100
From: @drstmane
Logged In: YES
user_id=572415
after adding some more casts (see my latest checkins), the
new code finally compiles.
## Comment 4317
Date: 2005-12-19 23:16:18 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / COMPILATION
## Comment 4318
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1347758 at http://sourceforge.net/support/tracker.php?aid=1347758
| PF: latest pathfinder fails to compile | https://api.github.com/repos/MonetDB/MonetDB/issues/751/comments | 0 | 2020-11-30T08:56:54Z | 2024-06-27T11:07:11Z | https://github.com/MonetDB/MonetDB/issues/751 | 753,287,261 | 751 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-03 05:45:28 +0100
From: @BitGrit
To: @sjoerdmullender
Version: -- development
Last updated: 2005-11-04 12:33:42 +0100
## Comment 4310
Date: 2005-11-03 17:45:28 +0100
From: @BitGrit
Handling of empty lines in MapiClient seems to be broken.
Enter the following on the MapiClient command line:
mil>
mil>printf("foo\n");
mil>
foo
(with the two empty mil> lines being simple Enter
keystrokes)
Clearly, the output should have been printed right
after the printf
statement, not after a second Enter event.
The amount of leading newlines seems to be related to
the amount
of enters needed to get output printed:
mil>
mil>
mil>printf("foo\n");
mil>
mil>
foo
In a more complicated example, this seems to result in
an assertion
failure. put the following into file.mil:
<ENTER>
<ENTER>
<ENTER>
if (bit(0)) {
printf("Foo\n");
} else {
printf("Bar\n") ;
}<EOF>
If ran through 'MapiClient < file.mil' we get an
assertion failure,
while with copy/paste we can see that MapiClient is
waiting for
more input:
mil>
mil>
mil>
mil>if (bit(0)) {
mil> printf("Foo\n");
mil>} else {
mil> printf("Bar\n") ;
more>}
more>
If the file is passed in as an argument: 'MapiClient
file.mil'
this example works fine.
## Comment 4311
Date: 2005-11-03 17:49:41 +0100
From: @BitGrit
Logged In: YES
user_id=1292024
Forgot to add assertion failure output:
Monet Database Server V4.9.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MapiClient:
/ufs/heman/devel/MonetDB/src/mapi/clients/C/MapiClient.mx:1057:
doFileByLines: Assertion `hdl == ((void *)0)' failed.
Aborted
## Comment 4312
Date: 2005-11-04 12:33:42 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed in revision 1.118 of stream.mx.
## Comment 4313
Date: 2005-12-19 22:49:23 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: TEST ADDED / SUCCESS
tests/BugDay_2005-12-19_4.9.3/Tests/empty_line.SF-1347331
## Comment 4314
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1347331 at http://sourceforge.net/support/tracker.php?aid=1347331
| MapiClient fails to handle empty lines correctly | https://api.github.com/repos/MonetDB/MonetDB/issues/750/comments | 0 | 2020-11-30T08:52:14Z | 2024-06-27T11:07:10Z | https://github.com/MonetDB/MonetDB/issues/750 | 753,284,082 | 750 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-03 04:23:14 +0100
From: Bastiaan de Groot <<bgroot>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2005-12-13 02:53:59 +0100
## Comment 4292
Date: 2005-11-03 16:23:14 +0100
From: Bastiaan de Groot <<bgroot>>
When I use a setMaxRows on a PreparedStatement, I get
an arrayOutOfBoundsException when my selection has more
records then I give as a max in setMaxRows.
The exception seems to be catched cause the application
terminates as normal. But the error is still displayed.
I have included a sample java code which generates the
error
## Comment 4293
Date: 2005-11-04 13:41:58 +0100
From: @grobian
Logged In: YES
user_id=963970
hmmm... works for me...
Can you attach a stack trace and reopen the bug?
## Comment 4294
Date: 2005-11-04 13:49:50 +0100
From: @grobian
Logged In: YES
user_id=963970
cleaning up my ~/Desktop:
slightly modified getBug.java to create the table and
disable auto_commit to make sure we don't leave some mess
when it would fail in the middle.
## Comment 4295
Date: 2005-11-17 12:30:02 +0100
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
This is the stak trace:
"C:\Program Files\Java\jdk1.5.0_03\bin\java"
-Didea.launcher.port=7532
"-Didea.launcher.bin.path=C:\Program Files\IntelliJ IDEA
5.0\bin" -Dfile.encoding=windows-1252 -classpath "C:\Program
Files\Java\jdk1.5.0_03\jre\lib\charsets.jar;C:\Program
Files\Java\jdk1.5.0_03\jre\lib\deploy.jar;C:\Program
Files\Java\jdk1.5.0_03\jre\lib\javaws.jar;C:\Program
Files\Java\jdk1.5.0_03\jre\lib\jce.jar;C:\Program
Files\Java\jdk1.5.0_03\jre\lib\jsse.jar;C:\Program
Files\Java\jdk1.5.0_03\jre\lib\plugin.jar;C:\Program
Files\Java\jdk1.5.0_03\jre\lib\rt.jar;C:\Program
Files\Java\jdk1.5.0_03\jre\lib\ext\dnsns.jar;C:\Program
Files\Java\jdk1.5.0_03\jre\lib\ext\localedata.jar;C:\Program
Files\Java\jdk1.5.0_03\jre\lib\ext\sunjce_provider.jar;C:\Program
Files\Java\jdk1.5.0_03\jre\lib\ext\sunpkcs11.jar;C:\Documents
and Settings\Bastiaan\IdeaProjects\adt\classes;C:\Documents
and
Settings\Bastiaan\IdeaProjects\adt\classes\MonetDB_JDBC-2.2-Blunt-SR1.jar;C:\Program
Files\IntelliJ IDEA 5.0\lib\idea_rt.jar"
com.intellij.rt.execution.application.AppMain getBug
java.lang.ArrayIndexOutOfBoundsException: 10
at
nl.cwi.monetdb.jdbc.MonetConnection$RawResults.addRow(Unknown
Source)
at nl.cwi.monetdb.jdbc.MonetConnection.processQuery(Unknown
Source)
at nl.cwi.monetdb.jdbc.MonetConnection.run(Unknown Source)
Exception in thread "main" java.lang.IllegalStateException:
CacheThread shutting down or not running
at nl.cwi.monetdb.jdbc.MonetConnection.addQuery(Unknown Source)
at
nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(Unknown
Source)
at nl.cwi.monetdb.jdbc.MonetStatement.execute(Unknown Source)
at nl.cwi.monetdb.jdbc.MonetStatement.executeUpdate(Unknown
Source)
at getBug.main(getBug.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.intellij.rt.execution.application.AppMain.main(AppMain.java:86)
10
Process finished with exit code
## Comment 4296
Date: 2005-11-21 10:19:46 +0100
From: @grobian
Logged In: YES
user_id=963970
Please upload a source version that runs out of the box.
Your source doesn't create the table (foo) it tries to
insert in. Without it, I can't exactly reproduce your problem.
## Comment 4297
Date: 2005-11-22 10:47:16 +0100
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
i'am sorry but the last getBug.java works out of the box on
my pc. I have deleted everything under
/applicationdata/monetdb and ran the the file in it's own
directory without any other classes on the classpath and it
just works.
## Comment 4298
Date: 2005-11-22 11:14:30 +0100
From: @grobian
Logged In: YES
user_id=963970
Please take a look again.
Make sure you check out your own file, not my modification
to get it running. The diff is below, and it clearly
indicates that table foo isn't created, which causes your
example to fail. It works flawlessly for me with these
changes, that's why I ask you to generate a working example
that indicates the incorrect behaviour.
--- getBug.java.groot 2005-11-22 11:10:27.000000000 +0100
+++ getBug.java 2005-11-22 11:11:14.000000000 +0100
@@ -18,8 +18,9 @@
try {
connection =
DriverManager.getConnection("jdbc:monetdb://localhost/database?debug=false"
, "monetdb", "monetdb");
+ connection.setAutoCommit(false);
Statement st =connection.createStatement();
- //st.executeUpdate("create table foo(bar
integer);");
+ st.executeUpdate("create table foo(bar integer);");
for(int i=0;i<20;i++)
st.executeUpdate("insert into foo
values("+i+");");
PreparedStatement
p=connection.prepareStatement("select * from foo where bar<?");
@@ -37,8 +38,5 @@
System.out.println("table foo may not have been
removed, please take care yourself");
e.printStackTrace(); //To change body of catch
statement use File | Settings | File Templates.
}
-
-
-
}
}
What version of Java do you use?
## Comment 4299
Date: 2005-11-22 11:22:50 +0100
From: @grobian
Logged In: YES
user_id=963970
can you also try using this JDBC driver?
http://www.cwi.nl/~fabian/monetdb/MonetDB_JDBC.jar
I think it has debugging enabled, which gives me a better
clue what goes wrong for you if you post the stack trace
from it.
## Comment 4300
Date: 2005-11-22 12:17:21 +0100
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
I did indeed run your modification of the file but that also
causes the bug. I tryed running it with your jdbc driver and
this is the output it gives but I think it's the same:
java.lang.ArrayIndexOutOfBoundsException: 10
at
nl.cwi.monetdb.jdbc.MonetConnection$RawResults.addRow(MonetConnection.java:1329)
at
nl.cwi.monetdb.jdbc.MonetConnection.processQuery(MonetConnection.java:1196)
at
nl.cwi.monetdb.jdbc.MonetConnection.run(MonetConnection.java:965)
Exception in thread "main" java.lang.IllegalStateException:
CacheThread shutting down or not running
10 at
nl.cwi.monetdb.jdbc.MonetConnection.addQuery(MonetConnection.java:1010)
at
nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:318)
at
nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:290)
at
nl.cwi.monetdb.jdbc.MonetStatement.executeUpdate(MonetStatement.java:384)
at getBug.main(getBug.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.intellij.rt.execution.application.AppMain.main(AppMain.java:86)
I'am using:
java: 1.5.0_03
## Comment 4301
Date: 2005-11-22 12:58:21 +0100
From: @grobian
Logged In: YES
user_id=963970
Ok, it seems you have very strange things going on. Maybe
the IDEA thing influences the order in which the threads are
being executed. Could you please attach a debug log
(?debug=false) to this bug?
## Comment 4302
Date: 2005-11-22 13:34:18 +0100
From: @grobian
Logged In: YES
user_id=963970
sorry, that should read: "debug=true"
## Comment 4303
Date: 2005-11-22 13:46:50 +0100
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
I got that myselft ;)
I tryed running the file outside intellij but then I still
get the error. I have included the log file created when the
file was excecuted from within intellij.
## Comment 4304
Date: 2005-11-22 15:17:17 +0100
From: @grobian
Logged In: YES
user_id=963970
ah... you stumbled upon a very tricky bug. In your case the
server ignores the request from the driver to limit the
amount of tuples it gets, hence the buffer in the driver
'overflows'. In my case, it doesn't ignore the driver. If
I execute the same using MapiClient I get the same
(incorrect) behaviour.
I expect that it has to do with the way in which SET
reply_size = 10 is being sent. In the failing cases it is
sent with a S prefix, in the non-failing case with s prefix.
Added test script as:
sql/src/test/BugTracker/Tests/SF-1347183.reply-size_prepare
## Comment 4305
Date: 2005-11-26 01:15:50 +0100
From: @njnes
Logged In: YES
user_id=43556
The reply size isn't the problem (your reply size test script
runs correctly). Reassigned to fabian. Possible jdbc problem?
## Comment 4306
Date: 2005-12-13 14:43:10 +0100
From: @njnes
Logged In: YES
user_id=43556
Is this bug still valid?
## Comment 4307
Date: 2005-12-13 14:53:59 +0100
From: @grobian
Logged In: YES
user_id=963970
I don't think so. And if it is, then I believe the latests
protocol changes will eliminate it, as it allows JDBC to be
more or less stateless.
## Comment 4308
Date: 2005-12-19 22:42:15 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
The max rows in prepared is tested using test
SF-1347183.reply-size_prepare
The rest of the bug is probably fixed by the protocol
changes and is hence tested by any jdbc/mapi client
## Comment 4309
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1347183 at http://sourceforge.net/support/tracker.php?aid=1347183
| SQL: SET reply_size ignored when sent as S command | https://api.github.com/repos/MonetDB/MonetDB/issues/749/comments | 0 | 2020-11-30T08:52:11Z | 2024-06-27T11:07:09Z | https://github.com/MonetDB/MonetDB/issues/749 | 753,284,031 | 749 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-02 01:23:11 +0100
From: martijn <<mliem>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2005-11-02 01:38:12 +0100
## Comment 4288
Date: 2005-11-02 13:23:11 +0100
From: martijn <<mliem>>
I've got a problem of an error occuring when I try to
use the SQL CREATE VIEW statement. I tried to execute
the following SQL query, using java 1.5 on a Windows XP
system and MonetDB 4.8.2.
CREATE view resultUrl as
SELECT s2_kwm.urlid FROM s2_keywords
INNER JOIN s2_kwm ON s2_keywords.kwId = s2_kwm.kwId
WHERE s2_keywords.kw ='msn'
INTERSECT
SELECT s2_kwm.urlid FROM s2_keywords
INNER JOIN s2_kwm ON s2_keywords.kwId = s2_kwm.kwId
WHERE s2_keywords.kw ='spbasic';
This results in the following error:
java.sql.SQLException: Limit not supported for views
As far as I can see, no Limit is used in the query
above. I also checked the MonetDB log file, which shows
the query exactly as above (log file is included).
The problem is that this means I am unable to create a
view which would enable me to use a much less
complicated query then I am forced to use now.
## Comment 4289
Date: 2005-11-02 13:38:11 +0100
From: @grobian
Logged In: YES
user_id=963970
do not hit 'refresh' on SF pages, use browsing links
instead, otherwise you keep on double posting.
## Comment 4290
Date: 2005-12-19 22:38:55 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / REDUNDANT
## Comment 4291
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1345915 at http://sourceforge.net/support/tracker.php?aid=1345915
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| Limit error using VIEWS | https://api.github.com/repos/MonetDB/MonetDB/issues/748/comments | 0 | 2020-11-30T08:52:08Z | 2024-06-28T07:36:41Z | https://github.com/MonetDB/MonetDB/issues/748 | 753,283,993 | 748 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-11-02 12:26:07 +0100
From: martijn <<mliem>>
To: @njnes
Version: -- development
Last updated: 2005-11-10 10:41:15 +0100
## Comment 4282
Date: 2005-11-02 12:26:07 +0100
From: martijn <<mliem>>
I've got a problem of an error occuring when I try to
use the SQL CREATE VIEW statement. I tried to execute
the following SQL query, using java 1.5 on a Windows XP
system and MonetDB 4.8.2.
CREATE view resultUrl as
SELECT s2_kwm.urlid FROM s2_keywords
INNER JOIN s2_kwm ON s2_keywords.kwId = s2_kwm.kwId
WHERE s2_keywords.kw ='msn'
INTERSECT
SELECT s2_kwm.urlid FROM s2_keywords
INNER JOIN s2_kwm ON s2_keywords.kwId = s2_kwm.kwId
WHERE s2_keywords.kw ='spbasic';
This results in the following error:
java.sql.SQLException: Limit not supported for views
As far as I can see, no Limit is used in the query
above. I also checked the MonetDB log file, which shows
the query exactly as above (log file is included).
The problem is that this means I am unable to create a
view which would enable me to use a much less
complicated query then I am forced to use now.
## Comment 4283
Date: 2005-11-02 12:48:02 +0100
From: @grobian
Logged In: YES
user_id=963970
confirmed on the current branch
## Comment 4284
Date: 2005-11-09 21:05:14 +0100
From: @njnes
Logged In: YES
user_id=43556
Fixed in cvs head
BugDay_2005-11-09, Niels Nes: TEST ADDED / SUCCESS
src/test/bugs/Tests/view_limit.SF-1345861.sql
Please verify it also works for you
## Comment 4285
Date: 2005-11-10 10:41:15 +0100
From: @grobian
Logged In: YES
user_id=963970
meltdown: TEST ADDED / SUCCESS
/sql/src/test/bugs/Tests/view_error_limit.SF-1345861.s*
## Comment 4286
Date: 2005-12-19 22:37:06 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
## Comment 4287
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1345861 at http://sourceforge.net/support/tracker.php?aid=1345861
| Limit error using VIEWS | https://api.github.com/repos/MonetDB/MonetDB/issues/747/comments | 0 | 2020-11-30T08:52:05Z | 2024-06-27T11:07:07Z | https://github.com/MonetDB/MonetDB/issues/747 | 753,283,963 | 747 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-31 04:06:45 +0100
From: Jens Teubner <<teubner>>
To: @sjoerdmullender
Version: -- development
Last updated: 2005-11-28 09:13:57 +0100
## Comment 4278
Date: 2005-10-31 16:06:45 +0100
From: Jens Teubner <<teubner>>
Playing around with MonetDB on SunOS, I've tried compiling
MonetDB with `--without-pthread'. ./configure happily accepts this
option; subsequent compilation, however, fails. Same happens on
my Linux box (Gentoo i386).
## Comment 4279
Date: 2005-11-28 21:13:57 +0100
From: @njnes
Logged In: YES
user_id=43556
At the end of the autoconf macro AM_MONETDB_LIBS we now
check 'have_pthread' and exit configure on failures. Similar
code is probably needed for other critical libraries/programs.
BugDay ;-), just configure ie no test needed.
## Comment 4280
Date: 2005-12-19 22:36:00 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / COMPILATION
## Comment 4281
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1343978 at http://sourceforge.net/support/tracker.php?aid=1343978
| ./configure accepts --without-pthread | https://api.github.com/repos/MonetDB/MonetDB/issues/746/comments | 0 | 2020-11-30T08:52:02Z | 2024-06-27T11:07:06Z | https://github.com/MonetDB/MonetDB/issues/746 | 753,283,931 | 746 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-28 02:15:01 +0200
From: Jan Rittinger <<jan.rittinger>>
To: @njnes
Version: -- development
Last updated: 2006-01-18 09:44:04 +0100
## Comment 4270
Date: 2005-10-28 14:15:01 +0200
From: Jan Rittinger <<jan.rittinger>>
Mserver quits with an segmentation fault because of an
'a0040.access(BAT_APPEND)' command. The bat a0040 is
void|void.
Example see appended file (requires cvs update of pf).
Sorry - but I couldn't produce a smaller example :(
## Comment 4271
Date: 2005-11-20 20:10:47 +0100
From: @drstmane
Logged In: YES
user_id=572415
While my simple test script
MonetDB/tests/BugsViaSourgeforce/Tests/making_void-void_BAT_appendable.SF-1340615.*
seems to work fine,
Jan's original test script
pathfinder/tests/BugsViaSourgeforce/Tests/making_void-void_BAT_appendable.SF-1340615.*
indeed causes a segfault.
Apparently, a tail heap is assumed/expected where there is none.
Here's a debugging trace:
$ gdb --args Mserver
making_void-void_BAT_appendable.SF-1340615.milS
GNU gdb Red Hat Linux (6.3.0.0-1.84rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are
welcome to change it and/or distribute copies of it under
certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show
warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...Using
host libthread_db library "/lib64/libthread_db.so.1".
(gdb) r
Starting program:
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.GNU.64.64.d.--enable-debug.PREFIX./bin/Mserver
making_void-void_BAT_appendable.SF-1340615.milS
[Thread debugging using libthread_db enabled]
[New Thread 46912516843424 (LWP 18461)]
[New Thread 1082132832 (LWP 18497)]
Monet Database Server V4.9.3
Copyright (c) 1993-2005, CWI. All rights reserved.
Compiled for x86_64-redhat-linux-gnu/64bit with 64bit
OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
Shredded XML doc("auctionG.xml"), total time after
commit=0.070s
-----------------
h t name
void void type
-----------------
[ 0@0, nil ]
[ 1@0, nil ]
[ 2@0, nil ]
[ 3@0, nil ]
[ 4@0, nil ]
[ 5@0, nil ]
[ 6@0, nil ]
[ 7@0, nil ]
[ 8@0, nil ]
[ 9@0, nil ]
[ 10@0, nil ]
[ 11@0, nil ]
[ 12@0, nil ]
[ 13@0, nil ]
[ 14@0, nil ]
[ 15@0, nil ]
[ 16@0, nil ]
[ 17@0, nil ]
[ 18@0, nil ]
[ 19@0, nil ]
[ 20@0, nil ]
[ 21@0, nil ]
[ 22@0, nil ]
[ 23@0, nil ]
[ 24@0, nil ]
[ 25@0, nil ]
[ 26@0, nil ]
[ 27@0, nil ]
[ 28@0, nil ]
[ 29@0, nil ]
[ 30@0, nil ]
[ 31@0, nil ]
[ 32@0, nil ]
[ 33@0, nil ]
[ 34@0, nil ]
[ 35@0, nil ]
[ 36@0, nil ]
[ 37@0, nil ]
[ 38@0, nil ]
[ 39@0, nil ]
[ 40@0, nil ]
[ 41@0, nil ]
[ 42@0, nil ]
[ 43@0, nil ]
[ 44@0, nil ]
[ 45@0, nil ]
[ 46@0, nil ]
[ 47@0, nil ]
[ 48@0, nil ]
[ 49@0, nil ]
[ 50@0, nil ]
[ 51@0, nil ]
[ 52@0, nil ]
[ 53@0, nil ]
[ 54@0, nil ]
[ 55@0, nil ]
[ 56@0, nil ]
[ 57@0, nil ]
[ 58@0, nil ]
[ 59@0, nil ]
[ 60@0, nil ]
[ 61@0, nil ]
[ 62@0, nil ]
[ 63@0, nil ]
[ 64@0, nil ]
[ 65@0, nil ]
[ 66@0, nil ]
[ 67@0, nil ]
[ 68@0, nil ]
[ 69@0, nil ]
[ 70@0, nil ]
[ 71@0, nil ]
[ 72@0, nil ]
[ 73@0, nil ]
[ 74@0, nil ]
[ 75@0, nil ]
[ 76@0, nil ]
[ 77@0, nil ]
[ 78@0, nil ]
[ 79@0, nil ]
[ 80@0, nil ]
[ 81@0, nil ]
[ 82@0, nil ]
[ 83@0, nil ]
[ 84@0, nil ]
[ 85@0, nil ]
[ 86@0, nil ]
[ 87@0, nil ]
[ 88@0, nil ]
[ 89@0, nil ]
[ 90@0, nil ]
[ 91@0, nil ]
[ 92@0, nil ]
[ 93@0, nil ]
[ 94@0, nil ]
[ 95@0, nil ]
[ 96@0, nil ]
[ 97@0, nil ]
[ 98@0, nil ]
[ 99@0, nil ]
[ 100@0, nil ]
[ 101@0, nil ]
[ 102@0, nil ]
[ 103@0, nil ]
[ 104@0, nil ]
[ 105@0, nil ]
[ 106@0, nil ]
[ 107@0, nil ]
[ 108@0, nil ]
[ 109@0, nil ]
[ 110@0, nil ]
[ 111@0, nil ]
[ 112@0, nil ]
[ 113@0, nil ]
[ 114@0, nil ]
[ 115@0, nil ]
[ 116@0, nil ]
[ 117@0, nil ]
[ 118@0, nil ]
[ 119@0, nil ]
[ 120@0, nil ]
[ 121@0, nil ]
[ 122@0, nil ]
[ 123@0, nil ]
[ 124@0, nil ]
[ 125@0, nil ]
[ 126@0, nil ]
[ "does not work" ]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912516843424 (LWP 18461)]
0x00002aaaab953b07 in HEAPsetpriv (hp=0x0, committed=0,
remap=0x7fffff889fbc, reload=0x7fffff889fc0)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/gdk/gdk_bat.mx:1728
warning: Source file is more recent than executable.
1728 if (hp->base == NULL || hp->storage ==
STORE_MEM || hp->filename == NULL || !committed) {
(gdb) bt
0 0x00002aaaab953b07 in HEAPsetpriv (hp=0x0, committed=0,
remap=0x7fffff889fbc, reload=0x7fffff889fc0)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/gdk/gdk_bat.mx:1728
1 0x00002aaaab9543c8 in BATsetaccess (b=0x1330118, mode=2)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/gdk/gdk_bat.mx:1817
2 0x00002aaaaaef70da in CMDsetaccess (r=0x7fffff88a240,
input=0x1330118, param=0x7fffff88a260)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/modules/plain/bat.mx:1174
3 0x00002aaaaaef2abb in CMDsetaccess_unpack833334089
(argc=3, argv=0x7fffff88a240) at bat.glue.c:1649
4 0x00002aaaaaabfd95 in interpret (stk=1, lt=0xd8d078,
res=0x7fffff88b3c0)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/monet_interpreter.mx:1169
5 0x00002aaaaaac8b9f in interpret_seqblock (stk=1,
lt=0xd8c5a8, res=0x7fffff88b3c0, scope=0)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/monet_interpreter.mx:1817
6 0x00002aaaaaabda3d in interpret (stk=1, lt=0xd18468,
res=0x7fffff88b3c0)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/monet_interpreter.mx:766
7 0x00002aaaaaabc023 in interpret_str (stk=0,
buf=0x60ccc8
"module(\"pathfinder\");\n\ndelete_all_docs(false);\ndelete_all_docs(true);\ncommit();\n\nmodule(\"unix\");\nvar
TSTSRCDIR := getenv(\"TSTSRCBASE\") +
\"/tests/XMark/Tests\";\nshred_doc(TSTSRCDIR + \"/\" +
\"auctionG.xml"..., res=0x7fffff88b3c0)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/monet_interpreter.mx:245
8 0x00002aaaaaabc4d5 in interpret_file (stk=0,
lt=0x5aabb8, res=0x7fffff88b3c0)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/monet_interpreter.mx:290
9 0x00002aaaaaabe568 in interpret (stk=0, lt=0x5aabb8,
res=0x7fffff88b3c0)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/monet_interpreter.mx:856
10 0x00002aaaaaadd422 in handleRequest (t=0x2aaaabc26e00,
q=0x5e2fa8, res=0x7fffff88b3c0)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/monet_queue.mx:533
11 0x00002aaaaaadd8b0 in doRequest (t=0x2aaaabc26e00,
preference=0x0)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/monet_queue.mx:559
12 0x00002aaaaab33750 in monetInterpreter
(status=0x7fffff88b444)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/monet/monet_process.mx:111
13 0x0000000000402679 in main (argc=2, av=0x7fffff88b568)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/tools/Mserver.mx:450
(gdb) li
1723 static int
1724 HEAPsetpriv(Heap *hp, int committed, int *remap, int
*reload)
1725 {
1726 str p;
1727
1728 if (hp->base == NULL || hp->storage ==
STORE_MEM || hp->filename == NULL || !committed) {
1729 return hp->storage;
1730 }
1731 /* STORE_PRIV would indicate an illegal heap
state */
1732 assert(hp->storage != STORE_PRIV);
(gdb) print hp
$1 = (Heap *) 0x0
(gdb) up
1 0x00002aaaab9543c8 in BATsetaccess (b=0x1330118, mode=2)
at
/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/MonetDB/src/gdk/gdk_bat.mx:1817
1817 m3 =
HEAPsetpriv(b->theap, committed, &remap, &reload);
(gdb) li
1812 m2 =
HEAPsetmmap(b->hheap, committed, &remap);
1813 }
1814 }
1815 if (bak3 >= 0) {
1816 if (mode ==
BAT_WRITE || (mode == BAT_APPEND && ATOMappendpriv(b->ttype,
b->theap))) {
1817 m3 =
HEAPsetpriv(b->theap, committed, &remap, &reload);
1818 } else if (bak ==
BAT_WRITE || (bak == BAT_APPEND && ATOMappendpriv(b->ttype,
b->theap))) {
1819 m3 =
HEAPsetmmap(b->theap, committed, &remap);
1820 }
1821 }
(gdb) print b
$2 = (BAT *) 0x1330118
(gdb) print *b
$3 = {GDKversion = 20749, batCacheid = 243, dims = {headtype
= 6 '\006', tailtype = 0 '\0', headloc = 0, tailloc = 0,
headkey = 1 '\001', tailkey = 0 '\0',
headvarsized = 0 '\0', tailvarsized = 1 '\001', bunshift
= 3 '\003', bunwidth = 8, hseq = 0, tseq =
9223372036854775808}, batBuns = 0x1330250,
hhash = 0x0, thash = 0x0, H = 0x1330190, T = 0x13301e0, P
= 0x1330230, U = 0x1330250, void_tid = 1, void_cnt = 1,
void_seq1 = 126,
void_seq2 = 9223372036854775808}
(gdb) print b->dims.tailtype
$4 = 0 '\0'
(gdb) print b->T->vheap
$5 = (Heap *) 0x0
(gdb) li 1506
1501 file pages. For string-heaps append-bats may mmap
the heap if doubles are not being eliminated
1502 anymore (i.e. when the contents of the builtin hash
table at the start of the string heap
1503 are not crucial anymore).
1504 @{
1505 @c
1506 define ATOMappendpriv(t,h)
((BATatoms[t].atomHeapCheck != HEAP_check ||
!HEAP_mmappable(h)) && \
1507 (ATOMstorage(t) !=
TYPE_str || GDK_ELIMDOUBLES(h)))
1508
1509 @}
1510 @- BATmmap
(gdb) print BATatoms[b->dims.tailtype].atomHeapCheck
$6 = (int (*)(Heap *, HeapRepair *)) 0
(gdb) print HEAP_check
$7 = {int (Heap *, HeapRepair *)} 0x2aaaab86774f <HEAP_check>
(gdb)
## Comment 4272
Date: 2005-11-25 01:01:06 +0100
From: @peterboncz
Logged In: YES
user_id=591107
I think this is fixed. At least it does not crash anymore.
the output of the test web is not as expected though.
Jan, could you please confirm that this problem has gone?
## Comment 4273
Date: 2005-11-25 13:52:52 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
patched file works without crash (output is still wrong
because of http://sourceforge.net/support/tracker.php?aid=1334536)
## Comment 4274
Date: 2005-12-19 22:35:07 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
## Comment 4275
Date: 2005-12-21 00:22:47 +0100
From: @drstmane
Logged In: YES
user_id=572415
re-opened as the respective test fails:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/making_void-void_BAT_appendable.SF-1340615.out.00.html
## Comment 4276
Date: 2006-01-18 09:44:04 +0100
From: @drstmane
Logged In: YES
user_id=572415
Fixed by Niels void semantic fixes in CVS.
## Comment 4277
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1340615 at http://sourceforge.net/support/tracker.php?aid=1340615
| setting the access property on void|void bats does not work | https://api.github.com/repos/MonetDB/MonetDB/issues/745/comments | 0 | 2020-11-30T08:51:58Z | 2024-06-27T11:07:05Z | https://github.com/MonetDB/MonetDB/issues/745 | 753,283,891 | 745 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-27 09:13:50 +0200
From: @Teggy
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2006-06-19 11:14:11 +0200
## Comment 4257
Date: 2005-10-27 21:13:50 +0200
From: @Teggy
Dear friends,
I found the query
<a/>/..
or, equivalently,
<a/>/parent::node()
to fail with
ERROR: XML Generation: idxTV, BAT[tmp]: 4294967295 not
within [0,0].
It should return the empty sequence, though. Since
4294967295 is 2^32 - 1 (or -1 in two's complement),
this smells like an off-by-one error...
Note that
<a/>/parent::*
correctly returns the empty sequence.
Greetings,
--Teggy
## Comment 4258
Date: 2005-10-28 15:04:39 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
You are right -- this is a really ancient off-by-one error
hidden in levelsteps.mx in line 348.
It can be also triggered by the following command:
lev_parent(bat(void,chr).seqbase(0@0).insert(nil,chr(0)),bat(void,oid).seqbase(nil).insert(nil,0@0).reverse(),1,1).print();
The problem is that the step consumes the first context node
(it is only one) and then decreases its counter. Because the
comparison 'while (search_level != -2)' matches
(search_level is -1) a result is generated in line 348.
As I don't understand the idea of levelsteps from the code
it is perhaps most easy for Henning to solve this bug :)
## Comment 4259
Date: 2005-10-28 15:14:56 +0200
From: @drstmane
Logged In: YES
user_id=572415
On behalf of Jan assigned to Henning.
## Comment 4260
Date: 2005-12-19 22:51:33 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: TEST ADDED / FAILURE
Added test parent_step_bug.SF-1339844.xq
output not approved as the script fails
## Comment 4261
Date: 2006-01-14 13:50:20 +0100
From: @drstmane
Logged In: YES
user_id=572415
Gentle reminder ;-)
## Comment 4262
Date: 2006-01-19 23:49:58 +0100
From: @drstmane
Logged In: YES
user_id=572415
Henning,
did you already have a chance to have a look at this one?
If not, could you perhaps give me a hint where to look/how
to fix it?
Thanks in advance,
Stefan
## Comment 4263
Date: 2006-06-06 21:05:54 +0200
From: @grobian
Logged In: YES
user_id=963970
Pingaling! :)
## Comment 4264
Date: 2006-06-08 13:43:50 +0200
From: @Teggy
Logged In: YES
user_id=642632
Hi,
Henning will spend his summer at Yahoo, Inc. (Spain).
Enjoy, Henning.
Most probably, this means that we should not expect Henning
to fix the bug in the weeks/months to come. (Deleting the
assignment to Henning.)
Cheers,
--Torsten
## Comment 4265
Date: 2006-06-18 03:33:46 +0200
From: @peterboncz
Logged In: YES
user_id=591107
As nobody seems to feel responsible for the old code by
Henning, I decided to solve this issue by moving to a loop-
lifted variant, that uses the size column rather than level
(and took ancestor with it on the go).
## Comment 4266
Date: 2006-06-18 13:52:54 +0200
From: @peterboncz
Logged In: YES
user_id=591107
As nobody seems to feel responsible for the old code by
Henning, I decided to solve this issue by moving to a loop-
lifted variant, that uses the size column rather than level
(and took ancestor with it on the go).
## Comment 4267
Date: 2006-06-19 09:29:56 +0200
From: @drstmane
Logged In: YES
user_id=572415
Re-opened as the respective test fails with the new
loop-lifted parent implementation:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/parent_step_bug.SF-1339844.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-12-19_0.9.3/parent_step_bug.SF-1339844.err.00.html
Possibly, the new output is correct and only needs to be
approved, but since I don't know what is supposed to be
correct, I re-open the bug report and assign it to Peter.
## Comment 4268
Date: 2006-06-19 11:14:09 +0200
From: @peterboncz
Logged In: YES
user_id=591107
the transient document container with its multiple roots
caused some trouble here. now the code is resistent against
bats that have multiple roots.
(actually, the code was supposed to be resilient against
corrupt data.. and should have produced a run-time error
instead of a crash)
NOTE: in our future multi-document storage we have an
artificial root node that should nmever be returned.
In order to make the upwards steps now work well with such
multi-document bats, it will suffice to give it a view
pre_size.slice(1@0, BATcount(pre_size))
that thus excludes the overall root.
## Comment 4269
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1339844 at http://sourceforge.net/support/tracker.php?aid=1339844
| PF: A parent step into the void | https://api.github.com/repos/MonetDB/MonetDB/issues/744/comments | 0 | 2020-11-30T08:51:55Z | 2024-06-28T07:36:41Z | https://github.com/MonetDB/MonetDB/issues/744 | 753,283,865 | 744 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-27 01:50:04 +0200
From: Bastiaan de Groot <<bgroot>>
To: @njnes
Version: -- development
Last updated: 2005-11-27 06:07:05 +0100
## Comment 4247
Date: 2005-10-27 13:50:04 +0200
From: Bastiaan de Groot <<bgroot>>
The following sql query gives an error in the sql client:
sql>select * from urls where urlid in
((select urlid from keys where a < 100 and b <200)
intersect
(select urlid from keys where a < 100 and b <300));
returns the following error:
ERROR = !parse error, expecting `','' or `')'' in:
"select * from urls
where urlid in
((select urlid from keys where a < 100 and b <200)
intersect"
while the following statements are working correctly:
((select urlid from keys where a < 100 and b <200)
intersect
(select urlid from keys where a < 100 and b <300));
and:
select * from urls where urlid in (select urlid from
keys where urlid<10);
It seems like the parser is having trouble when
intersect is used in a subquery.
## Comment 4248
Date: 2005-10-27 20:30:52 +0200
From: @njnes
Logged In: YES
user_id=43556
could you add the schema creation queries, without it its
not easy to rerun your queries.
## Comment 4249
Date: 2005-10-27 20:55:02 +0200
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
With the following table creation queries you can reproduce
the errors:
create table urls(urlid bigint primary key, c bigint, d bigint);
create table keys(urlid bigint, a bigint, b bigint,foreign
key(urlid) references urls);
## Comment 4250
Date: 2005-10-28 09:52:09 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed in the cvs head version. This case wasn't handled byt
the parser. Could you test the solution with your application?
## Comment 4251
Date: 2005-11-03 11:27:03 +0100
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
sorry, but I develop on a windows platform and therefor I'am
not able to easily compile the CVS version. I can send you
an extraction from my Java code which setsup my database and
runs this query.
## Comment 4252
Date: 2005-11-03 13:01:43 +0100
From: @njnes
Logged In: YES
user_id=43556
the code (or a reduced example) would be great. Another
solution might be to test using a different windows
installer version (cvs main branch).
## Comment 4253
Date: 2005-11-17 12:32:58 +0100
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
This is an extrection from my application which causes the bug
## Comment 4254
Date: 2005-11-27 18:07:05 +0100
From: @njnes
Logged In: YES
user_id=43556
Test added to
src/test/BugTracker/Tests/intersect_in_subquery.SF-1339411.sql
fixed the parser to handle this case.
## Comment 4255
Date: 2005-12-19 22:27:33 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
## Comment 4256
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1339411 at http://sourceforge.net/support/tracker.php?aid=1339411
| combination of subquery and intersect fails | https://api.github.com/repos/MonetDB/MonetDB/issues/743/comments | 0 | 2020-11-30T08:51:52Z | 2024-06-27T11:07:03Z | https://github.com/MonetDB/MonetDB/issues/743 | 753,283,834 | 743 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-26 12:19:01 +0200
From: Dave van Soest <<dsoest>>
To: @njnes
Version: -- development
Last updated: 2005-11-09 09:42:06 +0100
## Comment 4232
Date: 2005-10-26 12:19:01 +0200
From: Dave van Soest <<dsoest>>
The following two SQL-queries provide different results
on our database, while they are syntactically the same:
SELECT * FROM urlparts WHERE urlid=218 OR urlid=219 OR
urlid=329 OR urlid=3857 OR urlid=3868;
SELECT * FROM urlparts WHERE urlid=3868 OR urlid=3857
OR urlid=329 OR urlid=219 OR urlid=218;
We tried this on several machines.
The programs needed to create the database instance are
attached. The following commands should be entered to
recreate the problem. (We assume you have the Mserver
with SQL running.)
$ ./MapiClient.py <initdb_adt2.sql
$ ./load_urls_schema2.py 10000urls
$ ./MapiClient.py
>>> [Insert the queries here.]
Perhaps it also works if you fire the queries using an
different client program.
We hope this provides us the promised extra point for
the ADT practical course!
Regards,
Mark de Greef (0108898),
Dave van Soest (0122173)
## Comment 4233
Date: 2005-10-26 12:25:18 +0200
From: @grobian
Logged In: YES
user_id=963970
if you add an ORDER BY clause, does it then give the same
tuples (in the same order)? If so, this bug sounds invalid
to me, as the order of unordered queries is
non-deterministically defined within the SQL standard
itself. Only if different tuples are returned, this seems
to be a real bug to me.
## Comment 4234
Date: 2005-10-26 13:53:52 +0200
From: Dave van Soest <<dsoest>>
Logged In: YES
user_id=876820
One of the queries returns 5 results, the other none. So
this looks like a REAL bug!
## Comment 4235
Date: 2005-10-26 13:58:31 +0200
From: @grobian
Logged In: YES
user_id=963970
food for Niels! :)
## Comment 4236
Date: 2005-10-26 19:11:59 +0200
From: @njnes
Logged In: YES
user_id=43556
It seems the load_urls_schema2.py requires a python module
adt_common, which is missing in the bugreport tar ball.
## Comment 4237
Date: 2005-10-26 21:51:28 +0200
From: Dave van Soest <<dsoest>>
Logged In: YES
user_id=876820
We indeed forgot to send that file. Here it is.
## Comment 4238
Date: 2005-10-26 22:15:31 +0200
From: @njnes
Logged In: YES
user_id=43556
I don't see a newly attached file, ie forgot to press the
submit button.
## Comment 4239
Date: 2005-10-27 10:02:29 +0200
From: Dave van Soest <<dsoest>>
Logged In: YES
user_id=876820
A second try then to upload the file.
## Comment 4240
Date: 2005-10-27 14:52:50 +0200
From: @njnes
Logged In: YES
user_id=43556
A property (hdense) of the kunion operator wasn't reset
correctly. Therefor an incorrect route in the fetchjoin
implementation was taken in case the OR-ed values where
sorted. This is now fixed in the cvs head version
## Comment 4241
Date: 2005-11-02 11:29:18 +0100
From: Dave van Soest <<dsoest>>
Logged In: YES
user_id=876820
It seems it is not solved yet. (I tested it with the last
CVS version on Monday October 31st.)
## Comment 4242
Date: 2005-11-02 11:35:45 +0100
From: @njnes
Logged In: YES
user_id=43556
Did you check with the latest MonetDB (ie this change was
inside the core
of monet)?
## Comment 4243
Date: 2005-11-02 13:36:06 +0100
From: Dave van Soest <<dsoest>>
Logged In: YES
user_id=876820
The MonetDB kernel and SQL versions I am testing with now
where downloaded from CVS on October 31st. Installing Monet
takes about an hour, so I don't have much time to check out
every new version.
## Comment 4244
Date: 2005-11-09 21:42:06 +0100
From: @njnes
Logged In: YES
user_id=43556
fixed in cvs
BugDay_2005-11-09, Niels Nes: TEST ADDED / SUCCESS
src/test/bugs/order_disjunctive_bug.SF-1338309.sql
## Comment 4245
Date: 2005-12-19 22:26:36 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
## Comment 4246
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1338309 at http://sourceforge.net/support/tracker.php?aid=1338309
| Order of disjunctive clauses should not make a difference | https://api.github.com/repos/MonetDB/MonetDB/issues/742/comments | 0 | 2020-11-30T08:51:49Z | 2024-06-27T11:07:02Z | https://github.com/MonetDB/MonetDB/issues/742 | 753,283,805 | 742 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-25 06:25:49 +0200
From: Jan Rittinger <<jan.rittinger>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-10-26 12:37:08 +0200
## Comment 4228
Date: 2005-10-25 18:25:49 +0200
From: Jan Rittinger <<jan.rittinger>>
The first part of the merged union works fine, but
making the sort criterion void|void makes Monet totally
gaga! (It makes an append union and joining the result
results in really funny behaviour -- incomplete joins.)
MonetDB>var a :=
bat(void,oid).insert(nil,1@0).insert(nil,1@0).insert(nil,1@0).insert(nil,2@0).insert(nil,3@0).seqbase(0@0);
MonetDB>var mu :=
merged_union(a,a,a.project("foo"),a.project("bar"));
MonetDB>mu.fetch(0).print();
-----------------
h t name
void oid type
-----------------
[ 0@0, 1@0 ]
[ 1@0, 1@0 ]
[ 2@0, 1@0 ]
[ 3@0, 1@0 ]
[ 4@0, 1@0 ]
[ 5@0, 1@0 ]
[ 6@0, 2@0 ]
[ 7@0, 2@0 ]
[ 8@0, 3@0 ]
[ 9@0, 3@0 ]
MonetDB>mu.fetch(1).print();
-----------------
h t name
void str type
-----------------
[ 0@0, "foo" ]
[ 1@0, "foo" ]
[ 2@0, "foo" ]
[ 3@0, "bar" ]
[ 4@0, "bar" ]
[ 5@0, "bar" ]
[ 6@0, "foo" ]
[ 7@0, "bar" ]
[ 8@0, "foo" ]
[ 9@0, "bar" ]
MonetDB>a.access(BAT_READ);
MonetDB>a := a.mirror();
MonetDB>a.print();
-----------------
h h name
void void type
-----------------
[ 0@0, 0@0 ]
[ 1@0, 1@0 ]
[ 2@0, 2@0 ]
[ 3@0, 3@0 ]
[ 4@0, 4@0 ]
MonetDB>var mu :=
merged_union(a,a,a.project("foo"),a.project("bar"));
MonetDB>mu.fetch(0).print();
-----------------
h t name
void oid type
-----------------
[ 0@0, 0@0 ]
[ 1@0, 1@0 ]
[ 2@0, 2@0 ]
[ 3@0, 3@0 ]
[ 4@0, 4@0 ]
[ 5@0, 0@0 ]
[ 6@0, 1@0 ]
[ 7@0, 2@0 ]
[ 8@0, 3@0 ]
[ 9@0, 4@0 ]
MonetDB>mu.fetch(1).print();
-----------------
h t name
void str type
-----------------
[ 0@0, "foo" ]
[ 1@0, "foo" ]
[ 2@0, "foo" ]
[ 3@0, "foo" ]
[ 4@0, "foo" ]
[ 5@0, "bar" ]
[ 6@0, "bar" ]
[ 7@0, "bar" ]
[ 8@0, "bar" ]
[ 9@0, "bar" ]
MonetDB>mu.fetch(0).leftjoin(bat(void,oid).insert(0@0,1@0).seqbase(0@0)).print();
-----------------
h t name
void oid type
-----------------
[ 5@0, 1@0 ]
## Comment 4229
Date: 2005-10-26 00:37:08 +0200
From: @peterboncz
Logged In: YES
user_id=591107
solves http://sourceforge.net/support/tracker.php?aid=1337630, which claims monet can't even join.
Problem is that merged_union produces an illegal sorted
property
on the tail column of its first result bat (see example
script at sourceforge), in the second case, where the
merged_union
is done on a [void,void] bat that is passed twice.
The problem is that when two threads, or (as in this case)
the same thread, intermittendly use the
BUNhead(b,p)/BUNtail(b,p)/BUNhvar(b,p)/BUNtvar(b,p)
macros on the same bat, but at different BUN positions 'p'
the last invocation overwrites the result delivered by the
former invocations (repeated invocations overwrite the same
field in the bat header. This kludge was adopted in order
to produce a pointer to an oid, which is difficult for a void
column that is never materialized).
Another kludge in monet_interpreter.mx already compensates
for
the multi-threading risk posed by this. The safety mechanism
consists of making a BAT-view temporary copy if we detect
concurrent use of the same void-BAT by multiple threads. As
a
BAT-view gets a private BAT header, this removes the BUN
macro
problems (that stem from re-using a field in the bat header
to materialize the oid in).
Until now, the monet code developer was in charge of ensuring
that this would not go wrong in the single-threaded case.
Thanks to full materialization, this boils down to the case
were the same void-BAT is passed multiple times to a
command.
i.e. todays bug.
Thus, all MIL commands must make sure that those BUN
macros
are never used on *different* BAT parameters *without*
copying
the accessed value to some temporary variable.
Alas, if even Stefan can't handle this, we must conclude that
leaving this to the developer is too optimistic.
The fix of today extends the multi-threaded safety mechanism
(interpret_pin) to the single-threaded case of a multiply
passed bat.
open question: Monet5 developers are you even aware of this
issue?
## Comment 4230
Date: 2005-12-19 22:24:01 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: TEST ADDED / SUCCESS
Added test to pathfinder
tests/BugDay_2005-12-19_0.9.3/Tests/merged_union_and_join.SF-1337630.milM
## Comment 4231
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1337630 at http://sourceforge.net/support/tracker.php?aid=1337630
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.
| Merge Union and join does not work correctly | https://api.github.com/repos/MonetDB/MonetDB/issues/741/comments | 0 | 2020-11-30T08:51:46Z | 2024-06-28T13:34:15Z | https://github.com/MonetDB/MonetDB/issues/741 | 753,283,780 | 741 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-22 12:11:06 +0200
From: Jan Rittinger <<jan.rittinger>>
To: @njnes
Version: -- development
Last updated: 2006-01-18 09:42:25 +0100
## Comment 4216
Date: 2005-10-22 00:11:06 +0200
From: Jan Rittinger <<jan.rittinger>>
If I append a void|void bat to an empty oid|oid bat
Mserver uses wrong seqbases. (An insert works fine.)
MonetDB>var bar := bat
(void,oid).insert(nil,nil).mark(0@0).reverse().mark(0@0);
MonetDB>bar := bar.reverse().mark(0@0).reverse();
MonetDB>var foo := bat(oid,oid);
MonetDB>foo.append(bar);
MonetDB>foo.print();
-----------------
h t name
oid oid type
-----------------
[ 1@0, 0@0 ]
MonetDB>var foo := bat(oid,oid);
MonetDB>foo.insert(bar);
MonetDB>foo.print();
-----------------
h t name
oid oid type
-----------------
[ 0@0, 0@0 ]
## Comment 4217
Date: 2005-10-25 11:20:58 +0200
From: @njnes
Logged In: YES
user_id=43556
Fixed bug in oid_max implementation.
## Comment 4218
Date: 2005-10-25 11:23:19 +0200
From: @njnes
Logged In: YES
user_id=43556
added test script
## Comment 4219
Date: 2005-11-10 10:35:13 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
append is still buggy -- see following example:
var a := bat
(void,oid).seqbase(nil).insert(nil,1@0).insert(nil,2@0).reverse();
a.access(BAT_APPEND);
a.print();
-----------------
t h name
oid void type
-----------------
[ 1@0, nil ]
[ 2@0, nil ]
var b := a.mark(0@0).reverse();
b := b.access(BAT_READ).mirror();
b.print();
-----------------
t t name
void void type
-----------------
[ 0@0, 0@0 ]
[ 1@0, 1@0 ]
MonetDB>a.append(b).print();
-----------------
t h name
oid void type
-----------------
[ 1@0, nil ]
[ 2@0, nil ]
[ nil, nil ]
[ nil, nil ]
## Comment 4220
Date: 2005-11-10 10:42:00 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
Similar problem with insert:
MonetDB>var a := bat
(void,oid).seqbase(nil).insert(nil,1@0).insert(nil,2@0).reverse();
MonetDB>a.access(BAT_APPEND);
MonetDB>a.print();
-----------------
t h name
oid void type
-----------------
[ 1@0, nil ]
[ 2@0, nil ]
MonetDB>var b := a.mark(0@0).reverse();
MonetDB>b := b.access(BAT_READ).mirror();
MonetDB>b.print();
-----------------
t t name
void void type
-----------------
[ 0@0, 0@0 ]
[ 1@0, 1@0 ]
MonetDB>a.insert(b).print();
-----------------
t h name
oid void type
-----------------
[ 1@0, nil ]
[ 2@0, nil ]
[ 0@0, nil ]
[ 1@0, nil ]
## Comment 4221
Date: 2005-11-20 19:03:50 +0100
From: @drstmane
Logged In: YES
user_id=572415
According to the TestWeb, this one seems to be fixed:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests03/GNU.32.32.s-CYGWIN1.5.12/tests_BugsViaSourgeforce/append_empty_oid_bat.SF-1334536.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.32.32.s-CYGWIN1.5.12/tests_BugsViaSourgeforce/append_empty_oid_bat.SF-1334536.out.00.html
Jan, Niels,
could you please check/confirm, and if you agree, mark this
report "fixed" and close it?
Thanks in advance.
Stefan
## Comment 4222
Date: 2005-11-25 13:44:55 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
both examples in the comments still fail ...
(re-assigning it to Peter as he seems to be in a bug-fixing
mood :))
thx
## Comment 4223
Date: 2005-12-19 22:59:03 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
MonetDB/tests/BugsViaSourgeforce/Tests/append_empty_oid_bat.SF-1334536.milS
## Comment 4224
Date: 2005-12-23 16:07:19 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Sorry Niels, but you added these void,void bats..
Also: I'm on holiday (but you might b moving..)
## Comment 4225
Date: 2006-01-05 16:51:15 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
increased priority as test fails for a large number of
algebra compiled XMark queries:
pathfinder/tests/XMark/alg/q08
pathfinder/tests/XMark/alg/q09
pathfinder/tests/XMark/alg/q11
pathfinder/tests/XMark/alg/q12
pathfinder/tests/XMark/alg/q13
pathfinder/tests/XMark/alg/q19
## Comment 4226
Date: 2006-01-18 09:42:25 +0100
From: @drstmane
Logged In: YES
user_id=572415
Fixed by Niels void semantic fixes in CVS.
## Comment 4227
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1334536 at http://sourceforge.net/support/tracker.php?aid=1334536
| data changes by appending/inserting void|void bats | https://api.github.com/repos/MonetDB/MonetDB/issues/740/comments | 0 | 2020-11-30T08:51:44Z | 2024-06-27T11:07:00Z | https://github.com/MonetDB/MonetDB/issues/740 | 753,283,756 | 740 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-21 10:34:56 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-11-09 09:54:10 +0100
## Comment 4210
Date: 2005-10-21 22:34:56 +0200
From: @grobian
create table t (
id serial,
d date default cast(now() as date)
);
insert into t ;
select * from t;
will return a null value for d instead of the current date.
## Comment 4211
Date: 2005-10-21 22:35:30 +0200
From: @grobian
Logged In: YES
user_id=963970
bug wrangling
## Comment 4212
Date: 2005-10-28 10:17:50 +0200
From: @njnes
Logged In: YES
user_id=43556
added support for cast's in the default.
## Comment 4213
Date: 2005-11-09 21:54:10 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: TEST ADDED / SUCCESS
src/test/bugs/Tests/default_with_cast.SF-1334486.sql
## Comment 4214
Date: 2005-12-19 22:49:13 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
sql/src/test/bugs/Tests/default_with_cast.SF-1334486.sql
## Comment 4215
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1334486 at http://sourceforge.net/support/tracker.php?aid=1334486
| SQL: cast(now() as date) in default fails | https://api.github.com/repos/MonetDB/MonetDB/issues/739/comments | 0 | 2020-11-30T08:51:41Z | 2024-06-27T11:06:59Z | https://github.com/MonetDB/MonetDB/issues/739 | 753,283,723 | 739 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-21 11:52:38 +0200
From: @Teggy
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-11-20 06:17:15 +0100
## Comment 4198
Date: 2005-10-21 11:52:38 +0200
From: @Teggy
(This is the first bug report due to my use of
MonetDB/XQuery in the course on "Database-Supported XML
Processors" here @ TUM. Even if nothing comes out of
this course, hopefully we can collect bugs ;-)
The following fails:
<a>
<b><c id="1"><d id="2"/></c>
<c/>
</b>
</a>/child::node()
with
ERROR: merged_union: BAT 9 must have a dense head.
The particular XPath axis used makes no difference, the
evaluation fails with the exact same error message.
Note that my example is fragile in the sense that if I
remove either or both of the 'id' attributes or the
empty <c/> element, the query works fine.
Greetings,
--Teggy
## Comment 4199
Date: 2005-10-21 12:32:02 +0200
From: @drstmane
Logged In: YES
user_id=572415
just a quick shot before I might have time to have a closer
look:
does it work if you run Mserver with property checking enabled,
i.e., `Mserver --debug=10 ...` ?
## Comment 4200
Date: 2005-10-21 13:25:39 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
the following line makes the problem:
merged_result := merged_union (_attr_iter003,
_attr_iter, _attr_qn003, _attr_qn, _attr_prop003,
_attr_prop, _attr_frag003, _attr_frag, _attr_own003, _attr_own);
The solution are again the properties (like Stefan already
sketched --debug=10 works).
The interesting thing is that adding a chk_order() which
would be the obvious solution does not help. Adding a
reverse().mark(0@0).reverse() to the _attr_own003 bat on the
other side works.
Perhaps either chk_order does not work correctly or
merged_union does look at the sorting of the tail (which is
not in order). Perhaps Stefan can have a deeper look into it :)
## Comment 4201
Date: 2005-10-21 14:32:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
thanks, jan.
well, chk_ord cannot help, because merged_union complains
that the head is not dense, and not that it is not sorted;
not dense means either of not sorted, not key, seqbase==nil
-- i'll chek it once I have time...
for now, please stick to using '--debug=10'.
## Comment 4202
Date: 2005-10-21 14:46:50 +0200
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
I fixed the problem at its origin: a leftjoin introduced an
oid column and a later insert probably destroyed the denseness.
Now the leftjoin is marked again and the insert does not
harm the denseness anymore.
Hopefully my checkin compiles :P -- Additionally I just
discovered that I checked in my changes only into the
development branch - Sorry
PS: Could someone close the fixed bug if the checkin
compiles -- Thanks
## Comment 4203
Date: 2005-10-21 16:37:48 +0200
From: @Teggy
Logged In: YES
user_id=642632
Jan's "fix" does not fix the problem for
the 0.8 stable branch.
The behavior is unchanged.
Sorry,
--Teggy
## Comment 4204
Date: 2005-10-21 16:50:08 +0200
From: @drstmane
Logged In: YES
user_id=572415
Obviously not, since Jan's checkins went to the development
trunk ;-))
Jan,
shall I back-port your fixes (and if so, which?) to the
XQuery_0-8 release branch, or would you do it your self?
Stefan
## Comment 4205
Date: 2005-10-21 17:23:32 +0200
From: @Teggy
Logged In: YES
user_id=642632
Hi Stefan,
sorry, I forgot to mention that I applied Jan's fix
manually in my source tree.
Back-porting thus is a good idea, but it will be
disappointing, I'm afraid ;-)
--Teggy
## Comment 4206
Date: 2005-11-06 20:39:04 +0100
From: @drstmane
Logged In: YES
user_id=572415
[a small present on this special day ;-)]
(hopefully) fixed in CVS:
a leftjoin could not (in general) derive that each tuple of
the left input
finds exactly one match, and hence maintains its dense head;
we need to give MonetDB a hand, here...
Teggy,
could you please double-check, whether this fix works for
you, and if so, close this bug report?
Stefan
## Comment 4207
Date: 2005-11-20 18:17:15 +0100
From: @drstmane
Logged In: YES
user_id=572415
I consider this one fixed, and hence close it.
Teggy,
please complain if you disagree!
Stefan
## Comment 4208
Date: 2005-12-19 22:48:31 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
pathfinder/tests/BugsViaSourgeforce/Tests/ID.1333969.*
## Comment 4209
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1333969 at http://sourceforge.net/support/tracker.php?aid=1333969
| PF: XPath step eval (and presence of attributes?) | https://api.github.com/repos/MonetDB/MonetDB/issues/738/comments | 0 | 2020-11-30T08:51:37Z | 2024-06-27T11:06:58Z | https://github.com/MonetDB/MonetDB/issues/738 | 753,283,675 | 738 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-20 03:40:48 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-10-23 12:00:31 +0200
## Comment 4194
Date: 2005-10-20 15:40:48 +0200
From: @grobian
issueing a query with a LIMIT clause results in a
single tuple consisting of NULL values.
monetdb-> select * from sequences;
+----------+--------+----------------------+----------------------+----------------------+----------------------+----------------------+--------+
| name | schema | start | cached
| increment | minvalue
| maxvalue | cycle |
+==========+========+======================+======================+======================+======================+======================+========+
| seq_0""" | sys | 1 |
3 | 1 |
1 | 1 | false |
| seq_1""" | sys | 1 |
3 | 1 |
1 | 1 | false |
+----------+--------+----------------------+----------------------+----------------------+----------------------+----------------------+--------+
2 rows
monetdb-> select * from sequences limit 1;
+--------+--------+----------------------+----------------------+----------------------+----------------------+----------------------+--------+
| name | schema | start | cached
| increment | minvalue
| maxvalue | cycle |
+========+========+======================+======================+======================+======================+======================+========+
| <NULL> | <NULL> | <NULL> |
<NULL> | <NULL> | <NULL>
| <NULL> | <NULL> |
+--------+--------+----------------------+----------------------+----------------------+----------------------+----------------------+--------+
1 row
monetdb-> select * from sequences limit 2;
+--------+--------+----------------------+----------------------+----------------------+----------------------+----------------------+--------+
| name | schema | start | cached
| increment | minvalue
| maxvalue | cycle |
+========+========+======================+======================+======================+======================+======================+========+
| <NULL> | <NULL> | <NULL> |
<NULL> | <NULL> | <NULL>
| <NULL> | <NULL> |
+--------+--------+----------------------+----------------------+----------------------+----------------------+----------------------+--------+
1 row
monetdb-> select * from sequences limit 1 offset 1;
+--------+--------+----------------------+----------------------+----------------------+----------------------+----------------------+--------+
| name | schema | start | cached
| increment | minvalue
| maxvalue | cycle |
+========+========+======================+======================+======================+======================+======================+========+
| <NULL> | <NULL> | <NULL> |
<NULL> | <NULL> | <NULL>
| <NULL> | <NULL> |
+--------+--------+----------------------+----------------------+----------------------+----------------------+----------------------+--------+
1 row
monetdb->
## Comment 4195
Date: 2005-10-23 00:00:31 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed. In the generated mil, some output variables were
nil-ed before being outputted.
## Comment 4196
Date: 2005-12-19 22:47:42 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / REDUNDANT: e.g.
sql/src/test/BugDay_2005-12-19_2.9.3/Tests/weird_reponse_on_limit.SF-1314643.*
## Comment 4197
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1333223 at http://sourceforge.net/support/tracker.php?aid=1333223
| SQL: LIMIT is broken | https://api.github.com/repos/MonetDB/MonetDB/issues/737/comments | 0 | 2020-11-30T08:51:34Z | 2024-06-27T11:06:57Z | https://github.com/MonetDB/MonetDB/issues/737 | 753,283,641 | 737 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-19 03:50:00 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2005-10-26 07:28:21 +0200
## Comment 4185
Date: 2005-10-19 15:50:00 +0200
From: @drstmane
`MapiClient -lxquery` hangs enternally, if it is
provided an empty XQuery,
both via a file on the command line, via a pipe to
stdin, and internally, when the built-in server-side
XQuery compiler produces an error, and hence no MIL
output. In the latter case, the error message is not
printed.
Try
echo -n '' | MapiClient -lxquery
touch empty.xq ; MapiClient -lxquery empty.xq
echo '<a>' | MapiClient -lxquery
Unfortunately, I cannot say, whether this is related to
the recent MAPI changes, or the recent Pathfinder
changes, or both...
## Comment 4186
Date: 2005-10-19 16:04:34 +0200
From: @drstmane
Logged In: YES
user_id=572415
ps: `MapiClient -lmil` & `MapiClient -lsql` do not hang.
## Comment 4187
Date: 2005-10-24 20:13:24 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: jdiepenmaat@users.sourceforge.net ----
Logged In: YES
user_id=1367088
The same error occurs when an invalid document is given, like:
echo "<doc>bla</docsss>" | MapiClient -lxquery
## Comment 4188
Date: 2005-10-25 13:26:46 +0200
From: @njnes
Logged In: YES
user_id=43556
Sjoerd fixed the error handling code. Could users verify
all cases are indeed fixed?
## Comment 4189
Date: 2005-10-25 14:54:06 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: jdiepenmaat@users.sourceforge.net ----
Logged In: YES
user_id=1367088
Problem seems not to be solved, the same errors still occur
here.
## Comment 4190
Date: 2005-10-25 15:01:58 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
When I try your query I don't get a hang:
% echo "<doc>bla</docsss>" | MapiClient -lxquery
XML start/end tags do not match: at (1,1-1,17): <doc> and
</docsss>
%
Did you rebuild from CVS (taking into account that anonymous
CVS at SourceForge is always behind CVS via SSH)? In
particular, you need to rebuild pathfinder.
## Comment 4191
Date: 2005-10-25 18:40:26 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: jdiepenmaat@users.sourceforge.net ----
Logged In: YES
user_id=1367088
Sorry for inconvenience, my mistake, it's working now!
## Comment 4192
Date: 2005-12-19 22:45:33 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / SUCCESS:
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/empty.SF-1331808.*
## Comment 4193
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1331808 at http://sourceforge.net/support/tracker.php?aid=1331808
| XQuery: `MapiClient -lxquery` hangs on empty input | https://api.github.com/repos/MonetDB/MonetDB/issues/736/comments | 0 | 2020-11-30T08:51:31Z | 2024-06-27T11:06:56Z | https://github.com/MonetDB/MonetDB/issues/736 | 753,283,603 | 736 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-19 01:07:41 +0200
From: @peterboncz
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2007-12-21 04:20:03 +0100
## Comment 4178
Date: 2005-10-19 01:07:41 +0200
From: @peterboncz
Hi Jens,
Thanks a lot for implementing those modules.
However, the following issues:
- it seems as 'declare variable' that put variables into the
static context are still ignored
- the http://sourceforge.net/support/tracker.php?aid=1 script hits a core dump. it attempts to load
two modules and calls a function from the second
modules. That function in turn, is defined in the first
module.
- the http://sourceforge.net/support/tracker.php?aid=2 script omits the import for the second
module. Here it just says 'error loading in module ..'. I
think W3C semantics is that indeed an error should be
given (because the query needs to explicitly load all
modules it uses). However, the error message could be
improved.
best,
Peter
## Comment 4179
Date: 2005-10-23 20:06:18 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Hi Peter,
thanks for the report.
(1) I've just committed some changes regarding variables declared in
modules. (If a module was given as Pathfinder's input an that module
loads some other module, it was handled incorrectly.)
However, Pathfinder's behavior was partially intended (but we may change
that to suit our needs). I had implemented module importing via a work
list; modules are added to that list upon `import module' statements, and
loaded until the list is processed. This way, we don't really have the
information about which module has imported which other module, but
rather treat them as they were all loaded independently from the main
query. In that case, variables are not visible between modules. This
"invisibility" in a sense is a feature, though Pathfinder handles it too strict.
But maybe it is better to drop that restriction and be too lax instead. I will
change that.
(2) The segfault produced by http://sourceforge.net/support/tracker.php?aid=1.xq is actually a bit tricky. Function
declarations and their uses have to be translated in correct order. Parse
trees with modules imported look a bit more tricky than they looked before,
and I'll have to see how I can still handle that correctly with Burg. Stay
tuned.
(3) I actually cannot reproduce that one right now. The error actually
indicates there was some problem retrieving the file. Due to the above
mentioned way of loading modules, Pathfinder cannot be intelligent
enough to trigger the error that you suspected.
## Comment 4180
Date: 2005-10-28 11:58:35 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Hi Peter,
I've just committed a fix for fs.brg that hopefully fixes the core dump that
you mentioned. Can you test?
Jens
## Comment 4181
Date: 2005-12-19 22:38:57 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / POSTPONED:
need more time to turn the attached scripts into a proper
test...
## Comment 4182
Date: 2006-12-20 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 4183
Date: 2007-12-21 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 4184
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1330309 at http://sourceforge.net/support/tracker.php?aid=1330309
| module bug | https://api.github.com/repos/MonetDB/MonetDB/issues/735/comments | 0 | 2020-11-30T08:51:28Z | 2024-06-27T11:06:55Z | https://github.com/MonetDB/MonetDB/issues/735 | 753,283,573 | 735 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-18 07:42:41 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2005-10-19 01:03:13 +0200
## Comment 4173
Date: 2005-10-18 19:42:41 +0200
From: @drstmane
(At least) on Fedora Core 4 (64-bit) "make install"
fails for MonetDB in src/tools/ with both gcc 4.0.1 &
icc 8.1:
========
Making install in tools
make[2]: Entering directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.GNU.64.64.d..BUILD./MONETDB/src/tools'
make install-am
make[3]: Entering directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.GNU.64.64.d..BUILD./MONETDB/src/tools'
chmod a+x monetdb-config.bat
chmod a+x monetdb-config
make[4]: Entering directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.GNU.64.64.d..BUILD./MONETDB/src/tools'
chmod a+x monetdb-config.bat
chmod a+x monetdb-config
test -z
"/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin"
|| mkdir -p --
"/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin"
mkdir -p
/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin
rm -f
/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin/monetdb-config.bat
/usr/bin/install -c monetdb-config.bat
/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin/monetdb-config.bat
mkdir -p
/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin
rm -f
/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin/monetdb-config
/usr/bin/install -c monetdb-config
/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin/monetdb-config
test -z
"/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin"
|| mkdir -p --
"/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin"
/bin/sh ../../libtool --mode=install /usr/bin/install
-c 'Mbeddedmil'
'/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin/Mbeddedmil'
libtool: install: warning: `libembeddedmil.la' has not
been installed in
`/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/lib'
/usr/bin/install -c .libs/Mbeddedmil
/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin/Mbeddedmil
test -z
"/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin"
|| mkdir -p --
"/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin"
/bin/sh ../../libtool --mode=install /usr/bin/install
-c 'Mserver'
'/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin/Mserver'
/usr/bin/install -c .libs/Mserver
/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/bin/Mserver
make[4]: *** No rule to make target
`install-initmodulesLTLIBRARIES', needed by
`install-embeddedmilLTLIBRARIES'. Stop.
make[4]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.GNU.64.64.d..BUILD./MONETDB/src/tools'
make[3]: *** [install-am] Error 2
make[3]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.GNU.64.64.d..BUILD./MONETDB/src/tools'
make[2]: *** [install] Error 2
make[2]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.GNU.64.64.d..BUILD./MONETDB/src/tools'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
`/net/corona.ins.cwi.nl/export/scratch0/manegold/Monet/Testing/Current/.GNU.64.64.d..BUILD./MONETDB/src'
make: *** [install-recursive] Error 1
========
## Comment 4174
Date: 2005-10-19 00:58:02 +0200
From: @peterboncz
Logged In: YES
user_id=591107
I looked at this, and these changes make it actually work on
MinGW. I do not have easily another platform for testing here
in Dagstuhl and this autogen stuff is magic for me anyway.
What I did was to add the libraries (used for making Mserver)
also to the embedded client *library*.
anyway, another problem that I can't solve is that I have to
manuall patch libtool on MinGW:
5178c5178
< execv("$SHELL",newargz);
---
> execv("$SHELL",(const char* const*)newargz);
5228,5230c5228
< (((st.st_mode & S_IXOTH) == S_IXOTH) ||
< ((st.st_mode & S_IXGRP) == S_IXGRP) ||
< ((st.st_mode & S_IXUSR) == S_IXUSR)))
---
> ((st.st_mode & S_IXUSR) == S_IXUSR))
## Comment 4175
Date: 2005-10-19 13:03:13 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed with a change in autogen.
The Cygwin stuff has nothing to do with this. I got the
errors when building for MinGW as well, but you can just
ignore them.
## Comment 4176
Date: 2005-12-19 22:37:38 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / COMPILATION
## Comment 4177
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1329720 at http://sourceforge.net/support/tracker.php?aid=1329720
| "make install" fails for MonetDB in src/tools/ | https://api.github.com/repos/MonetDB/MonetDB/issues/734/comments | 0 | 2020-11-30T08:51:25Z | 2024-06-27T11:06:54Z | https://github.com/MonetDB/MonetDB/issues/734 | 753,283,540 | 734 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-17 04:00:25 +0200
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2010-05-04 11:20:49 +0200
## Comment 4167
Date: 2005-10-17 16:00:25 +0200
From: Wouter Alink <<alink>>
given the following query:
<a value="1">
<b value="2"/>
<c value="3"/>
</a>//*/@value[. > 1]
the following error is returned:
ERROR: cannot handle attributes in function
pf:distinct-doc-order.
but i would expect "2" and "3" to be returned and that
the ordering would follow from the ordering of the
parents of the attributes (the elements "b" and "c"). I
don't know if the specs allow this construction...
according to 3.2.2 of http://www.w3.org/tr/xquery it
looks like all axis are supported.
## Comment 4168
Date: 2005-10-17 16:17:36 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
problems (partial ordering) would appear when querying the
following:
<a value="1">
<b value="2" name="4"/>
<c value="3"/>
</a>//*/@*[. > 1]
This list can only be partially ordered and the result may
either be
2,4,3 or 4,2,3
If the query however is translated to the following:
<a value="1">
<b value="2" name="4"/>
<c value="3"/>
</a>//*[@*[. > 1]]/@*
an expected result (4,2,3) is returned.
## Comment 4169
Date: 2005-11-25 01:06:57 +0100
From: @peterboncz
Logged In: YES
user_id=591107
Amazing, this now returns:
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult value="2" value="3">
</XQueryResult>
is this correct??
## Comment 4170
Date: 2005-11-25 08:27:46 +0100
From: @Teggy
Logged In: YES
user_id=642632
Hi Peter,
the serialization is not correct: the attributes of an XML
element are required to have unique names. Unfortunately,
the 'xml' output method doesn't have a chance to serialize
this OK in any case, since the correct result of query is
attribute value { 2 },
attribute value { 3 }
If the query returns the result above (it seems it does),
this bug should be closed. A different bug should be
opened, though: currently, I don't see how the 'xml' output
method could be tweaked to behave in a meaningful fashion in
such a case.
Cheers,
--Teggy
## Comment 4171
Date: 2005-12-19 22:37:17 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / SUCCESS:
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/doc-order_in_attributes.SF-1328671.*
## Comment 4172
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1328671 at http://sourceforge.net/support/tracker.php?aid=1328671
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
| XQuery: doc-order in attributes | https://api.github.com/repos/MonetDB/MonetDB/issues/733/comments | 0 | 2020-11-30T08:51:23Z | 2024-06-28T13:34:14Z | https://github.com/MonetDB/MonetDB/issues/733 | 753,283,515 | 733 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-16 12:10:33 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2005-10-19 02:58:53 +0200
## Comment 4162
Date: 2005-10-16 12:10:33 +0200
From: @drstmane
compiler/compile.c fails to compile with gcc:
========
gcc -m32 -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler
-I..
-I/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler
-Iinclude
-I/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/include
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/common
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/gdk
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/monet
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/plain
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/contrib
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/mapi
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/C
-DLIBCOMPILER1 -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer -finline-functions
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-uninitialized -c
/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/compile.c
-fno-common -DPIC -o .libs/libcompiler1_la-compile.o
cc1: warnings being treated as errors
/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/compile.c:
In function 'pf_compile_MonetDB':
/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/compile.c:504:
warning: variable 'timing' might be clobbered by
'longjmp' or 'vfork'
/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/compile.c:500:
warning: argument 'mode' might be clobbered by
'longjmp' or 'vfork'
make[3]: *** [libcompiler1_la-compile.lo] Error 1
========
## Comment 4163
Date: 2005-10-18 19:30:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
For the bookkeeping; from "mission-control" "back
home" in
A'dam:
here's what gcc 4.0.1 & icc 8.1 on Fedora Core 4
(64-bit)
say about revision 1.48 of
pathfinder/compiler/compile.c:
========
gcc -m64 -DHAVE_CONFIG_H -I.
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler
-I..
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler
-Iinclude
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/common
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/gdk
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/monet
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/plain
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/contrib
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/mapi
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/C
-DLIBCOMPILER1 -g -O2 -std=c99 -Wall -W
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -c
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/compile.c
-fPIC -DPIC -o .libs/libcompiler1_la-compile.o
cc1: warnings being treated as errors
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/compile.c:
In function 'pf_compile_MonetDB':
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/compile.c:517:
warning: 'timing' is used uninitialized in this function
make[3]: *** [libcompiler1_la-compile.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler
-I..
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler
-Iinclude
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/common
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/gdk
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/monet
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/plain
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/contrib
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/mapi
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/C
-DLIBCOMPILER1 -g -we140 -wd1418 -c99
-Wall -w2 -we266 -Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-c
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/compile.c
-KPIC -DPIC -o .libs/libcompiler1_la-compile.o
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/compile.c(517):
error 592: variable "timing" is used before its value is set
if (!timing) timing = 1;
^
compilation aborted for
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/compile.c
(code 2)
make[3]: *** [libcompiler1_la-compile.lo] Error 1
========
## Comment 4164
Date: 2005-10-19 14:58:53 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS.
## Comment 4165
Date: 2005-12-19 22:26:23 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / COMPILATION
## Comment 4166
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1327855 at http://sourceforge.net/support/tracker.php?aid=1327855
| pathfinder/compiler/compile.c fails to compile | https://api.github.com/repos/MonetDB/MonetDB/issues/732/comments | 0 | 2020-11-30T08:51:20Z | 2024-06-27T11:06:52Z | https://github.com/MonetDB/MonetDB/issues/732 | 753,283,487 | 732 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-16 12:09:12 +0200
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2005-10-19 02:58:25 +0200
## Comment 4156
Date: 2005-10-16 12:09:12 +0200
From: @drstmane
compiler/mil/milprint_summer.c fails to compile with
both gcc & icc:
========
gcc -m32 -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/mil
-I../..
-I/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/mil
-I../include
-I/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/mil/../include
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/common
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/gdk
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/monet
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/plain
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/contrib
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/mapi
-I/var/tmp/monet.GNU.32.32.d.22389/MonetDB/.GNU.32.32.d-Darwin8.2.0/include/MonetDB/C
-DLIBMIL -O2 -std=c99 -Wall -W -O6 -fomit-frame-pointer
-finline-functions
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-uninitialized -c
/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/mil/milprint_summer.c
-fno-common -DPIC -o .libs/libmil_la-milprint_summer.o
cc1: warnings being treated as errors
/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/mil/milprint_summer.c:
In function 'translateUDF':
/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/mil/milprint_summer.c:6480:
warning: cast from pointer to integer of different size
/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/mil/milprint_summer.c:
In function 'PFstopMIL':
/var/tmp/monet.GNU.32.32.d.22389/pathfinder/compiler/mil/milprint_summer.c:10301:
warning: statement with no effect
make[4]: *** [libmil_la-milprint_summer.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/tmp/monet.ntv.64.64.d.22389/pathfinder/compiler/mil
-I../..
-I/tmp/monet.ntv.64.64.d.22389/pathfinder/compiler/mil
-I../include
-I/tmp/monet.ntv.64.64.d.22389/pathfinder/compiler/mil/../include
-I/tmp/monet.ntv.64.64.d.22389/MonetDB/.ntv.64.64.d-Fedora3/include/MonetDB
-I/tmp/monet.ntv.64.64.d.22389/MonetDB/.ntv.64.64.d-Fedora3/include/MonetDB/common
-I/tmp/monet.ntv.64.64.d.22389/MonetDB/.ntv.64.64.d-Fedora3/include/MonetDB/gdk
-I/tmp/monet.ntv.64.64.d.22389/MonetDB/.ntv.64.64.d-Fedora3/include/MonetDB/monet
-I/tmp/monet.ntv.64.64.d.22389/MonetDB/.ntv.64.64.d-Fedora3/include/MonetDB/plain
-I/tmp/monet.ntv.64.64.d.22389/MonetDB/.ntv.64.64.d-Fedora3/include/MonetDB/contrib
-I/tmp/monet.ntv.64.64.d.22389/MonetDB/.ntv.64.64.d-Fedora3/include/MonetDB/mapi
-I/tmp/monet.ntv.64.64.d.22389/MonetDB/.ntv.64.64.d-Fedora3/include/MonetDB/C
-DLIBMIL -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -DHWCOUNTERS -DHW_Linux
-DHW_x86_64 -we266 -Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-c
/tmp/monet.ntv.64.64.d.22389/pathfinder/compiler/mil/milprint_summer.c
-KPIC -DPIC -o .libs/libmil_la-milprint_summer.o
/tmp/monet.ntv.64.64.d.22389/pathfinder/compiler/mil/milprint_summer.c(1630):
error 268: the format string ends before this argument
bool_res, bool_res, bool_res,
^
/tmp/monet.ntv.64.64.d.22389/pathfinder/compiler/mil/milprint_summer.c(10299):
error 174: expression has no effect
"});\n"
^
compilation aborted for
/tmp/monet.ntv.64.64.d.22389/pathfinder/compiler/mil/milprint_summer.c
(code 2)
make[4]: *** [libmil_la-milprint_summer.lo] Error 1
========
## Comment 4157
Date: 2005-10-18 19:24:27 +0200
From: @drstmane
Logged In: YES
user_id=572415
For the bookkeeping; from "mission-control" "back home" in
A'dam:
here's what gcc 4.0.1 & icc 8.1 on Fedora Core 4 (64-bit)
say about revision 1.117 of
pathfinder/compiler/mil/milprint_summer.c:
========
gcc -m64 -DHAVE_CONFIG_H -I.
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil
-I../..
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil
-I../include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/../include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/common
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/gdk
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/monet
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/plain
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/contrib
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/mapi
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/C
-DLIBMIL -g -O2 -std=c99 -Wall -W
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -c
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c
-fPIC -DPIC -o .libs/libmil_la-milprint_summer.o
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c:
In function 'translateUDF':
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c:6487:
error: 'ssize_t' undeclared (first use in this function)
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c:6487:
error: (Each undeclared identifier is reported only once
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c:6487:
error: for each function it appears in.)
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c:6487:
error: syntax error before 'fun'
make[4]: *** [libmil_la-milprint_summer.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil
-I../..
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil
-I../include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/../include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/common
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/gdk
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/monet
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/plain
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/contrib
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/mapi
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/C
-DLIBMIL -g -we140 -wd1418 -c99 -Wall -w2 -we266 -Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-c
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c
-KPIC -DPIC -o .libs/libmil_la-milprint_summer.o
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c(1637):
error 268: the format string ends before this argument
bool_res, bool_res, bool_res,
^
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c(6487):
error: identifier "ssize_t" is undefined
{ int tmp = (ssize_t) fun; snprintf(procname, 128,
"fn_%x_%i", tmp, fun->arity); }
^
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c(6487):
error: expected a ";"
{ int tmp = (ssize_t) fun; snprintf(procname, 128,
"fn_%x_%i", tmp, fun->arity); }
^
compilation aborted for
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c
(code 2)
make[4]: *** [libmil_la-milprint_summer.lo] Error 1
========
Btw, it seems a bit "scary" to cast a "PFfun_t*" to a
"ssize_t" in order to assign it to an "int" ...
## Comment 4158
Date: 2005-10-18 19:28:49 +0200
From: @drstmane
Logged In: YES
user_id=572415
For the bookkeeping; from "mission-control" "back home" in
A'dam:
here's what gcc 4.0.1 & icc 8.1 on Fedora Core 4 (64-bit)
say about revision 1.117 of
pathfinder/compiler/mil/milprint_summer.c:
========
gcc -m64 -DHAVE_CONFIG_H -I.
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil
-I../..
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil
-I../include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/../include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/common
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/gdk
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/monet
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/plain
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/contrib
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/mapi
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.GNU.64.64.d..PREFIX./MONETDB/include/MonetDB/C
-DLIBMIL -g -O2 -std=c99 -Wall -W
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -c
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c
-fPIC -DPIC -o .libs/libmil_la-milprint_summer.o
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c:
In function 'translateUDF':
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c:6487:
error: 'ssize_t' undeclared (first use in this function)
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c:6487:
error: (Each undeclared identifier is reported only once
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c:6487:
error: for each function it appears in.)
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c:6487:
error: syntax error before 'fun'
make[4]: *** [libmil_la-milprint_summer.lo] Error 1
--------
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil
-I../..
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil
-I../include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/../include
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/common
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/gdk
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/monet
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/plain
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/contrib
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/mapi
-I/ufs/manegold/_/scratch0/Monet/Testing/Current/.ntv.64.64.d..PREFIX./MONETDB/include/MonetDB/C
-DLIBMIL -g -we140 -wd1418 -c99 -Wall -w2 -we266 -Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-c
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c
-KPIC -DPIC -o .libs/libmil_la-milprint_summer.o
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c(1637):
error 268: the format string ends before this argument
bool_res, bool_res, bool_res,
^
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c(6487):
error: identifier "ssize_t" is undefined
{ int tmp = (ssize_t) fun; snprintf(procname, 128,
"fn_%x_%i", tmp, fun->arity); }
^
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c(6487):
error: expected a ";"
{ int tmp = (ssize_t) fun; snprintf(procname, 128,
"fn_%x_%i", tmp, fun->arity); }
^
compilation aborted for
/ufs/manegold/_/scratch0/Monet/Testing/Current/pathfinder/compiler/mil/milprint_summer.c
(code 2)
make[4]: *** [libmil_la-milprint_summer.lo] Error 1
========
Btw, it seems a bit "scary" to cast a "PFfun_t*" to a
"ssize_t" in order to assign it to an "int" ...
## Comment 4159
Date: 2005-10-19 14:58:25 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS.
## Comment 4160
Date: 2005-12-19 22:26:03 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / COMPILATION
## Comment 4161
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1327854 at http://sourceforge.net/support/tracker.php?aid=1327854
| pathfinder/compiler/mil/milprint_summer.c fails to compile | https://api.github.com/repos/MonetDB/MonetDB/issues/731/comments | 0 | 2020-11-30T08:51:16Z | 2024-06-27T11:06:51Z | https://github.com/MonetDB/MonetDB/issues/731 | 753,283,450 | 731 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-12 09:31:36 +0200
From: @Teggy
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-10-12 11:26:41 +0200
## Comment 4151
Date: 2005-10-12 09:31:36 +0200
From: @Teggy
With XQuery_0-8 and MonetDB_4-8 (CVS), I am unable to
execute any XQuery expression involving an XPath
location step. The generated MIL code references a MIL
proc which is nonexistent in pf_support.
Example: Input query
<a/>//a
Output from 'Mapiclient -lxquery':
ERROR: interpret: no matching MIL operator to
'loop_lifted_descendant_step_with_nsloc_test(BAT[void,oid],
BAT[void,void], BAT[void,oid], BAT[void,BAT], int, str,
str)'.
Note: the MIL procs
'loop_lifted_descendant_step_with_nsloc_test_pre'
and
'loop_lifted_descendant_step_with_nsloc_test_post'
do exist in pf_support.
Back-porting glitch?
## Comment 4152
Date: 2005-10-12 10:48:54 +0200
From: @drstmane
Logged In: YES
user_id=572415
hm, if
'loop_lifted_descendant_step_with_nsloc_test_pre'
and
'loop_lifted_descendant_step_with_nsloc_test_post'
do exist in pf_support,
then you're using the XQuery_0-8_demo branch,
which is admittedly not tested any more,
since the "official" demos are over,
and our testing resources are limited ...
I'll check-out, compile, and test the XQuery_0-8_demo asap.
For me, everything works fine with the HEAD of the
"MonetDB_4-8" & "XQuery_0-8" release branches (i.e., MonetDB
4.8.3 & XQuery 0.8.3) ...
## Comment 4153
Date: 2005-10-12 11:26:41 +0200
From: @Teggy
Logged In: YES
user_id=642632
Resolved via re-compilation and re-installation
(make uninstall, de-bootstrap, bootstrap, configure, make,
make install)
Thanks, Stefan.
## Comment 4154
Date: 2005-12-19 21:23:51 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
Many tests with Xpath expressions exist
## Comment 4155
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1324575 at http://sourceforge.net/support/tracker.php?aid=1324575
| PF: MIL code for loc.steps references nonexistent procs | https://api.github.com/repos/MonetDB/MonetDB/issues/730/comments | 0 | 2020-11-30T08:51:13Z | 2024-06-28T13:34:13Z | https://github.com/MonetDB/MonetDB/issues/730 | 753,283,409 | 730 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-11 10:59:38 +0200
From: Wouter Alink <<alink>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2005-11-25 01:22:51 +0100
## Comment 4147
Date: 2005-10-11 22:59:38 +0200
From: Wouter Alink <<alink>>
Het is weer prijsschieten...
This time two bugs, probably related:
echo 'doc("result_set1.xml")/@notexist' | MapiClient -lxq
ERROR: interpret: no matching MIL operator to
'mvaljoin(oid, BAT[void,oid], BAT[void,BAT])'.
echo 'for $d in doc("result_set1.xml") return element {
"test" } { max($d//@notexist) }' | MapiClient -lxq
ERROR: BATmalleftfetchjoin: Cannot perform
leftfetchjoin: right head is no dense OID column.
## Comment 4148
Date: 2005-11-10 16:32:24 +0100
From: Jan Rittinger <<jan.rittinger>>
Logged In: YES
user_id=993208
in first case item is a constant instead of a column.
In the second something similiar (line 499):
var input_iter :=
input_order.leftfetchjoin(iter002).chk_order();
print(iter002);
-----------------
h t name
void oid type
-----------------
[ nil, 1@0 ]
So please assign this bug to Stefan or Peter.
## Comment 4149
Date: 2005-12-19 22:24:53 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / SUCCESS:
pathfinder/tests/BugDay_2005-12-19_0.9.3/Tests/non-existent_attribute.SF-1324219.*
## Comment 4150
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1324219 at http://sourceforge.net/support/tracker.php?aid=1324219
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQuery: querying non-existent attribute | https://api.github.com/repos/MonetDB/MonetDB/issues/729/comments | 0 | 2020-11-30T08:51:10Z | 2024-06-27T11:06:49Z | https://github.com/MonetDB/MonetDB/issues/729 | 753,283,378 | 729 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-11 02:19:57 +0200
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2007-05-25 02:29:33 +0200
## Comment 4139
Date: 2005-10-11 14:19:57 +0200
From: Wouter Alink <<alink>>
Suppose you don't want to wait for the answer to an
XQuery issued from a MapiClient. In that case I found
the option on the Mserver-console to press Ctrl-C most
useful.
The expected behaviour is that Mserver exits 'clean',
but if it is busy with an XQuery, it exits accompanied
with a Segfault.
## Comment 4140
Date: 2005-10-11 14:28:19 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
now that i'm thinking of it... if a MapiClient gets killed
with Ctrl-C, it would be nice of MapiClient if it at least
tries to send a "i'm dying" message to the Mserver before it
actually dies, so that Mserver can stop computing the answer.
## Comment 4141
Date: 2005-12-19 21:18:28 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: RELEASED / REASSIGN
Could maybe be tested using a long running xquery query, but
with a low timeout
## Comment 4142
Date: 2006-06-06 21:04:36 +0200
From: @grobian
Logged In: YES
user_id=963970
Wouter, is this still working for you? Also is it possible
to create a long-running query (with a small dataset) that
Mtest can timeout on?
## Comment 4143
Date: 2007-02-27 16:43:06 +0100
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Assigned to Wouter since he was asked a question.
## Comment 4144
Date: 2007-05-24 23:48:45 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Originator: YES
i'm still using Ctrl-C quite often these days, but i haven't seen Mserver segfault anymore (neither 0.12 nor 0.16) for quite a while. When i reported the bug it almost always segfaulted on ctrl-c. Is this enough reason to close the bug? i will reopen the bug on the first ctrl-c segfault i encounter.
about finding a test query: i don't know how to slow down monetdb without monetdb being (memory) I/O bound. the best xquery test i can come up with at the moment is:
count(1 to 125000000)
which at least has to allocate about 1GB of memory (which often takes at least a second), but it is difficult to guarantee a certain duration. On systems with little available memory it might cause other errors, and on high-end systems it might not even take a second.
## Comment 4145
Date: 2007-05-25 02:29:33 +0200
From: @peterboncz
Logged In: YES
user_id=591107
Originator: NO
closing this one then
## Comment 4146
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1323802 at http://sourceforge.net/support/tracker.php?aid=1323802
| Mserver/XQuery: Segfault on Ctrl-C | https://api.github.com/repos/MonetDB/MonetDB/issues/728/comments | 0 | 2020-11-30T08:51:07Z | 2024-06-27T11:06:48Z | https://github.com/MonetDB/MonetDB/issues/728 | 753,283,332 | 728 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-09 03:52:59 +0200
From: Wouter Alink <<alink>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2007-12-21 04:20:03 +0100
## Comment 4130
Date: 2005-10-09 15:52:59 +0200
From: Wouter Alink <<alink>>
When MonetDB is used for shredding and deleting
XML-docs (via MapiClient) and querying those XML docs
(via MapiClient), after a while, I guess it takes
several 100's of sequential MapiClient invocations, the
server crashes with the following error message:
MonetDB>!ERROR: initClient: Out of client slots
*** glibc detected *** Mserver: free(): invalid
pointer: 0x00000000417ff598 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3a2366a94e]
/lib64/libc.so.6(__libc_free+0x6e)[0x3a2366ae7e]
/home/alink/local/lib/libbat.so.0(GDKfree+0x38)[0x2aaaab74bb38]
/home/alink/local/lib/MonetDB/lib_mapi.so(MAPIlisten+0xabc)[0x2aaab5ae012c]
/home/alink/local/lib/libmonet.so.0(interpret+0xd5e)[0x2aaaaaac54ce]
/home/alink/local/lib/libmonet.so.0(interpret_seqblock+0xa5)[0x2aaaaaacd7a5]
/home/alink/local/lib/libmonet.so.0(interpret+0xa53)[0x2aaaaaac51c3]
/home/alink/local/lib/libmonet.so.0(interpret_seqblock+0xa5)[0x2aaaaaacd7a5]
/home/alink/local/lib/libmonet.so.0(interpret+0xa53)[0x2aaaaaac51c3]
/home/alink/local/lib/libmonet.so.0(interpret+0x5a4)[0x2aaaaaac4d14]
/home/alink/local/lib/libmonet.so.0(interpret_seqblock+0xa5)[0x2aaaaaacd7a5]
/home/alink/local/lib/libmonet.so.0(interpret+0xa53)[0x2aaaaaac51c3]
/home/alink/local/lib/libmonet.so.0(interpret_seqblock+0xa5)[0x2aaaaaacd7a5]
/home/alink/local/lib/libmonet.so.0(interpret+0xa53)[0x2aaaaaac51c3]
/home/alink/local/lib/libmonet.so.0(interpret+0x5a4)[0x2aaaaaac4d14]
/home/alink/local/lib/libmonet.so.0(handleRequest+0xa7)[0x2aaaaaad0327]
/home/alink/local/lib/libmonet.so.0(doRequest+0x49)[0x2aaaaaad0999]
/home/alink/local/lib/libmonet.so.0(monetInterpreter+0x6d)[0x2aaaaab0ad8d]
/lib64/libpthread.so.0[0x3a2470697c]
/lib64/libc.so.6(__clone+0x6e)[0x3a236c9c2e]
======= Memory map: ========
./start_mserver.sh: line 2: 21540 Aborted
Mserver --dbfarm=/home/alink/dbfarm49
--dbinit="module(pathfinder);pfstart();mapi_start();"
## Comment 4131
Date: 2005-10-09 18:53:35 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
Here is a test-script (in my best bash-scripting) that
produces the error... on my PC (MonetDB 4.9.3, 64bit,
32bit-oid, FC4, x86_64) it always crashes after 509 times.
!/bin/bash
declare -i i=0
echo "1+1" > test.xq
==== lets execute this query a few times ===
while [[ $i -lt 1000 ]]
do
MapiClient -lxq test.xq > /dev/null
if [ $? != 0 ]
then
crashed=true
break
fi
i=$(($i+1))
printf .
done
==== did we crash? ===
if [ $crashed ]
then
echo "crashed at query attempt $i"
fi
~
## Comment 4132
Date: 2005-10-09 18:57:56 +0200
From: Wouter Alink <<alink>>
Logged In: YES
user_id=621590
p.s. forgot to mention: the script itself does not let
Mserver crash... the next MapiClient session attempt will :)
## Comment 4133
Date: 2005-10-10 15:15:05 +0200
From: @grobian
Logged In: YES
user_id=963970
Fixed in current CVS.
## Comment 4134
Date: 2005-10-10 15:21:22 +0200
From: @grobian
Logged In: YES
user_id=963970
I attached the (modified) scripts files to do the same sort
of testing for:
mil,
sql and
xquery
## Comment 4135
Date: 2005-12-19 21:14:30 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: RELEASED / REASSIGN
Should be test using a xquery version of mapi sample/smack tests
## Comment 4136
Date: 2006-12-20 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 4137
Date: 2007-12-21 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 4138
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1320331 at http://sourceforge.net/support/tracker.php?aid=1320331
| MonetDB: \"Out of client slots\" | https://api.github.com/repos/MonetDB/MonetDB/issues/727/comments | 0 | 2020-11-30T08:51:03Z | 2024-06-27T11:06:47Z | https://github.com/MonetDB/MonetDB/issues/727 | 753,283,291 | 727 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-09 10:44:03 +0200
From: Bastiaan de Groot <<bgroot>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2005-10-09 12:14:39 +0200
## Comment 4126
Date: 2005-10-09 10:44:03 +0200
From: Bastiaan de Groot <<bgroot>>
I'am not sure if this is a bug or a feature but, when i
deinstall monetDB through configuration-->software it
doesn't remove the files under C:\Documents and
Settings\<user>\Application Data\MonetDB. Which leaves
all the log files and databases on your system. I think
the Deinstaller should at least give a warning that
those files remain on the system since they can get
pretty big.
I am using Windows XP
## Comment 4127
Date: 2005-10-09 12:14:39 +0200
From: @grobian
Logged In: YES
user_id=963970
It's uncommon to remove user data when uninstalling a
product (it's like removing all .doc files from your system
when you uninstall word). A warning or note on reinstall
("previous dbfarm detected" or something) might be nice.
## Comment 4128
Date: 2005-12-19 21:01:51 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / NOT A Bug but a feature
## Comment 4129
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1319852 at http://sourceforge.net/support/tracker.php?aid=1319852
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.
| deinstallation doesn't remove database files | https://api.github.com/repos/MonetDB/MonetDB/issues/726/comments | 0 | 2020-11-30T08:51:00Z | 2024-06-28T13:34:12Z | https://github.com/MonetDB/MonetDB/issues/726 | 753,283,258 | 726 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-08 10:00:29 +0200
From: Bastiaan de Groot <<bgroot>>
To: @njnes
Version: -- development
Last updated: 2005-11-10 11:32:40 +0100
## Comment 4116
Date: 2005-10-08 22:00:29 +0200
From: Bastiaan de Groot <<bgroot>>
The following sql statements crashes the monetDB sql
server:
create table bla(foo integer primary key);
create table foo(bar integer unique);
while the following statement works fine:
create table foo(bar integer not null);
I'am using monetDB 4.8.2 on windows XP
## Comment 4117
Date: 2005-10-09 10:20:18 +0200
From: @grobian
Logged In: YES
user_id=963970
The development version doesn't crash, but doesn't make
sense either:
monetdb-> create table foo(bar integer primary key);
Error: CONSTRAINT PRIMARY KEY: a table can have only one
PRIMARY KEY
## Comment 4118
Date: 2005-10-09 12:12:00 +0200
From: @grobian
Logged In: YES
user_id=963970
it seems to be a windows issue judging from what I see on my
'stable' version:
% JdbcClient
Connection warning: database specifier not supported on this
server (mserver_sql), protocol version 4
Welcome to the MonetDB interactive JDBC terminal!
Database: MonetDB 4.8.2
Driver: MonetDB Native Driver 1.2 (Blunt+)
Type \q to quit, \h for a list of available commands
auto commit mode: on
monetdb-> \d
monetdb-> create table foo (
monetdb=( bar int,
monetdb=( primary key(bar)
monetdb=( );
Operation successful
monetdb-> drop table foo;
Operation successful
monetdb-> create table foo (bar int primary key);
Operation successful
monetdb-> \d foo
CREATE TABLE "sys"."foo" (
"bar" int NOT NULL,
CONSTRAINT "foo_bar_pkey" PRIMARY KEY ("bar")
);
monetdb->
## Comment 4119
Date: 2005-10-09 20:12:23 +0200
From: Bastiaan de Groot <<bgroot>>
Logged In: YES
user_id=1358666
note that the statement:
create table foo(bar integer, primary key(bar));
also crashes monet.
## Comment 4120
Date: 2005-10-23 00:01:30 +0200
From: @njnes
Logged In: YES
user_id=43556
can anybody verify this with the current version.
## Comment 4121
Date: 2005-11-02 19:48:23 +0100
From: @grobian
Logged In: YES
user_id=963970
niels is your windows installer ready to quickly test this yet?
## Comment 4122
Date: 2005-11-09 21:58:46 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-11-09, Niels Nes: ALREADY IN TESTWEB
some tests which create keys exists, ie this is allready tested.
Too do test on windows
## Comment 4123
Date: 2005-11-10 11:32:40 +0100
From: @njnes
Logged In: YES
user_id=43556
tested with latest version on windows. Doesn't crash anymore...
## Comment 4124
Date: 2005-12-19 20:54:25 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
## Comment 4125
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1318743 at http://sourceforge.net/support/tracker.php?aid=1318743
| primary key usage crashes monetDB | https://api.github.com/repos/MonetDB/MonetDB/issues/725/comments | 0 | 2020-11-30T08:50:57Z | 2024-06-27T11:06:45Z | https://github.com/MonetDB/MonetDB/issues/725 | 753,283,228 | 725 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-07 02:49:07 +0200
From: @sjoerdmullender
To: @sjoerdmullender
Version: -- development
Last updated: 2005-10-07 03:09:49 +0200
## Comment 4111
Date: 2005-10-07 14:49:07 +0200
From: @sjoerdmullender
This hangs when executed through MapiClient, but not
when executed directly on the console:
module(xtables);
CTgroup(new(void,int).insert(nil,0).seqbase(0@0)).print();
## Comment 4112
Date: 2005-10-07 14:55:23 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Test script added to web:
tests/BugDay_2005-10-06_4.8/print_CTgroup.SF-1315791.*
## Comment 4113
Date: 2005-10-07 15:09:49 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Fixed in mel.
## Comment 4114
Date: 2005-12-19 20:51:51 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: ALREADY IN TESTWEB
tests/BugDay_2005-10-06_4.8/print_CTgroup.SF-1315791.*
## Comment 4115
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1315791 at http://sourceforge.net/support/tracker.php?aid=1315791
| printing CTgroup result through Mapi hangs | https://api.github.com/repos/MonetDB/MonetDB/issues/724/comments | 0 | 2020-11-30T08:50:53Z | 2024-06-27T11:06:44Z | https://github.com/MonetDB/MonetDB/issues/724 | 753,283,191 | 724 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-07 01:01:41 +0200
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2005-10-11 01:56:33 +0200
## Comment 4105
Date: 2005-10-07 13:01:41 +0200
From: @drstmane
Apparently already since Wednesday, September 28 2005,
Pathfinder fails to compile with Intel's icc;
the current errors are
========
make[5]: Entering directory
`/var/tmp/monet.ntv.64.64.d.23099/pathfinder/SuSE9.3/compiler/algebra'
/bin/sh ../../libtool --tag=CC --mode=compile icc
-no-gcc -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/algebra
-I../..
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/algebra
-I../include
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/algebra/../include
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/common
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/gdk
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/monet
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/plain
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/contrib
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/mapi
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/C
-DLIBALGEBRA -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266
-Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-c -o libalgebra_la-algopt.lo `test -f 'algopt.c' ||
echo
'/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/algebra/'`algopt.c
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/algebra
-I../..
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/algebra
-I../include
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/algebra/../include
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/common
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/gdk
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/monet
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/plain
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/contrib
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/mapi
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/C
-DLIBALGEBRA -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-c algopt.c -KPIC -DPIC -o .libs/libalgebra_la-algopt.o
/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/algebra/algopt.brg(778):
error 185: dynamic initialization in unreachable code
PFalg_proj_t *projlist1 = p->sem.proj.items;
^
compilation aborted for algopt.c (code 2)
make[5]: *** [libalgebra_la-algopt.lo] Error 1
--------
/bin/sh ../../libtool --tag=CC --mode=compile icc
-no-gcc -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/mil
-I../..
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/mil
-I../include
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/mil/../include
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/common
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/gdk
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/monet
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/plain
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/contrib
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/mapi
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/C
-DLIBMIL -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266
-Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-c -o libmil_la-milprint_summer.lo `test -f
'milprint_summer.c' || echo
'/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/mil/'`milprint_summer.c
icc -no-gcc -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/mil
-I../..
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/mil
-I../include
-I/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/mil/../include
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/common
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/gdk
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/monet
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/plain
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/contrib
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/mapi
-I/var/tmp/monet.ntv.64.64.d.23099/MonetDB/.ntv.64.64.d-SuSE9.3/include/MonetDB/C
-DLIBMIL -we140 -wd1418 -c99 -Wall -w2 -mp1 -O3
-restrict -unroll -tpp7 -axWP -we266 -Werror
-wd1418,1419,279,310,981,810,444,193,111,177,171,181,764,269,108,188,1357,102,70,1572
-c
/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/mil/milprint_summer.c
-KPIC -DPIC -o .libs/libmil_la-milprint_summer.o
/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/mil/milprint_summer.c(3241):
error 268: the format string ends before this argument
i, i, i, i, i, i, i, i, i);
^
compilation aborted for
/var/tmp/monet.ntv.64.64.d.23099/pathfinder/compiler/mil/milprint_summer.c
(code 2)
make[4]: *** [libmil_la-milprint_summer.lo] Error 1
========
see also (e.g.)
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.ntv.64.64.d-Fedora3/make.out
## Comment 4106
Date: 2005-10-11 13:09:05 +0200
From: Jens Teubner <<teubner>>
Logged In: YES
user_id=731390
Seems like we really worked parallel here, Stefan. You were faster,
though.
Can you close the bug?
## Comment 4107
Date: 2005-10-11 13:12:26 +0200
From: @drstmane
Logged In: YES
user_id=572415
Well, I first stated taking care of the bug, and then
assigned it to me --- wrong order, sorry!
Anyway, I'll close it at soon as I'm completely sue it's fixed.
## Comment 4108
Date: 2005-10-11 13:56:33 +0200
From: @drstmane
Logged In: YES
user_id=572415
fixed in CVS
## Comment 4109
Date: 2005-12-19 20:49:04 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / COMPILATION
## Comment 4110
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1315733 at http://sourceforge.net/support/tracker.php?aid=1315733
| Pathfinder fails to compile with Intel's icc | https://api.github.com/repos/MonetDB/MonetDB/issues/723/comments | 0 | 2020-11-30T08:50:51Z | 2024-06-27T11:06:43Z | https://github.com/MonetDB/MonetDB/issues/723 | 753,283,159 | 723 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-07 12:43:00 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2005-10-07 07:05:16 +0200
## Comment 4100
Date: 2005-10-07 12:43:00 +0200
From: @drstmane
gmake[4]: Entering directory
`/scratch/monet.GNU.64.64.d.23099/MonetDB/SunOS5.8/src/common'
/bin/bash ../../libtool --mode=compile gcc -m64
-DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.64.64.d.23099/MonetDB/src/common
-I../..
-I/var/tmp/monet.GNU.64.64.d.23099/MonetDB/src/common
-I/var/tmp/soft64/local/include
-I/var/tmp/soft64/local/include -DLIBSTREAM -O2
-std=c99 -D__EXTENSIONS__ -Wall -W -O2
-fomit-frame-pointer -finline-functions -DHWCOUNTERS
-DHW_SunOS -DHW_sun4u
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-uninitialized -D_REENTRANT -c -o
libstream_la-stream.lo `test -f 'stream.c' || echo
'/var/tmp/monet.GNU.64.64.d.23099/MonetDB/src/common/'`stream.c
chmod a+x monet_options.py
gcc -m64 -DHAVE_CONFIG_H -I.
-I/var/tmp/monet.GNU.64.64.d.23099/MonetDB/src/common
-I../..
-I/var/tmp/monet.GNU.64.64.d.23099/MonetDB/src/common
-I/var/tmp/soft64/local/include
-I/var/tmp/soft64/local/include -DLIBSTREAM -O2
-std=c99 -D__EXTENSIONS__ -Wall -W -O2
-fomit-frame-pointer -finline-functions -DHWCOUNTERS
-DHW_SunOS -DHW_sun4u
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label
-Wno-uninitialized -D_REENTRANT -c stream.c -fPIC
-DPIC -o .libs/libstream_la-stream.o
/var/tmp/monet.GNU.64.64.d.23099/MonetDB/src/common/stream.mx:
In function `bstream_readline':
/var/tmp/monet.GNU.64.64.d.23099/MonetDB/src/common/stream.mx:2525:
`LINE_MAX' undeclared (first use in this function)
/var/tmp/monet.GNU.64.64.d.23099/MonetDB/src/common/stream.mx:2525:
(Each undeclared identifier is reported only once
/var/tmp/monet.GNU.64.64.d.23099/MonetDB/src/common/stream.mx:2525:
for each function it appears in.)
gmake[4]: *** [libstream_la-stream.lo] Error 1
see also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.64.64.d-SunOS5.8/make.out
or
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.ntv.64.64.d-SunOS5.8/make.out
## Comment 4101
Date: 2005-10-07 12:46:10 +0200
From: @drstmane
Logged In: YES
user_id=572415
and
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.32.32.s-CYGWIN1.5.12/make.out
and
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.32.32.d-Darwin8.2.0/make.out
## Comment 4102
Date: 2005-10-07 19:05:16 +0200
From: @njnes
Logged In: YES
user_id=43556
LINE_MAX (or better _POSIX2_LINE_MAX) is usually defined in
limits.h
which we now include. Also added a fallback incase its not
defined.
## Comment 4103
Date: 2005-12-19 20:47:32 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / COMPILATION
## Comment 4104
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1315724 at http://sourceforge.net/support/tracker.php?aid=1315724
| src/common/stream.mx fails to compile on Sun, Darwin, CygWin | https://api.github.com/repos/MonetDB/MonetDB/issues/722/comments | 0 | 2020-11-30T08:50:47Z | 2024-06-27T11:06:42Z | https://github.com/MonetDB/MonetDB/issues/722 | 753,283,127 | 722 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-07 10:31:33 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-10-23 12:07:20 +0200
## Comment 4096
Date: 2005-10-07 10:31:33 +0200
From: @grobian
currently we can create foreign keys with ON DELETE
CASCADE or ON UPDATE CASCADE, but this is actually
being ignored. We should either report an error that
we don't support it, or somehow send a warning message.
Since the latter is not really possible at the moment,
I opt for an error message to at least be a bit more
correct.
## Comment 4097
Date: 2005-10-23 00:07:20 +0200
From: @njnes
Logged In: YES
user_id=43556
duplicate of 1296395
## Comment 4098
Date: 2005-12-19 20:32:28 +0100
From: @njnes
Logged In: YES
user_id=43556
BugDay_2005-12-19, Niels: NO TEST / REDUNDANT
Test exist
./src/test/BugDay_2005-12-19_2.9.3/Tests/delete_cascade.SF-1296395.sql
## Comment 4099
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1315653 at http://sourceforge.net/support/tracker.php?aid=1315653
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| SQL: ON DELETE CASCADE accepted but ignored | https://api.github.com/repos/MonetDB/MonetDB/issues/721/comments | 0 | 2020-11-30T08:50:45Z | 2024-06-28T13:34:12Z | https://github.com/MonetDB/MonetDB/issues/721 | 753,283,097 | 721 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-06 11:12:17 +0200
From: Wouter Alink <<alink>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2005-11-25 01:37:47 +0100
## Comment 4092
Date: 2005-10-06 23:12:17 +0200
From: Wouter Alink <<alink>>
The query: 2.5 idiv 2
returns the correct result: 1
Hoever, the query: 25 idiv 2
returns:
WARNING: BBPdecref: range error -120
The only difference i can observer is that the first
arguments is now a integer instead of a decimal.
added this case to the test-script:
/tests/XQuery/Tests/idiv.xq
## Comment 4093
Date: 2005-11-25 01:37:47 +0100
From: @peterboncz
Logged In: YES
user_id=591107
fixed
## Comment 4094
Date: 2005-12-19 16:59:11 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
pathfinder/tests/XQuery/Tests/idiv.*
## Comment 4095
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1315339 at http://sourceforge.net/support/tracker.php?aid=1315339
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| XQuery: 'integer' idiv 'integer' | https://api.github.com/repos/MonetDB/MonetDB/issues/720/comments | 0 | 2020-11-30T08:50:41Z | 2024-06-27T11:06:40Z | https://github.com/MonetDB/MonetDB/issues/720 | 753,283,056 | 720 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-06 04:27:35 +0200
From: @BitGrit
To: @njnes
Version: -- development
Last updated: 2005-10-07 07:07:52 +0200
## Comment 4088
Date: 2005-10-06 16:27:35 +0200
From: @BitGrit
Parts of the website are not reachable due to incorrect
file permissions. For example:
http://monetdb.cwi.nl/GetGoing/Setup/MonetDB/index.html
and http://monetdb.cwi.nl/GetGoing/Setup/SQL/index.html
## Comment 4089
Date: 2005-10-06 21:35:17 +0200
From: @njnes
Logged In: YES
user_id=43556
Did some fixing, does it work now
## Comment 4090
Date: 2005-12-19 16:57:51 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / WEBSITE
## Comment 4091
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1314995 at http://sourceforge.net/support/tracker.php?aid=1314995
| Incorrect file permissions on website | https://api.github.com/repos/MonetDB/MonetDB/issues/719/comments | 0 | 2020-11-30T08:50:38Z | 2024-06-27T11:06:39Z | https://github.com/MonetDB/MonetDB/issues/719 | 753,283,022 | 719 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-06 04:18:49 +0200
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2006-01-15 02:14:56 +0100
## Comment 4080
Date: 2005-10-06 16:18:49 +0200
From: @sjoerdmullender
Start Mserver, enter
kill(0);
This causes a SEGFAULT.
Also see SF http://sourceforge.net/support/tracker.php?aid=994842.
## Comment 4081
Date: 2005-10-06 16:26:00 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
BugDay_2005-10-06: CLAIMED BY sjoerd
BugDay_2005-10-06: TEST ADDED / FAILURE
tests/BugDay_2005-10-06_4.8/kill_0.milS
## Comment 4082
Date: 2005-12-19 16:56:42 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
MonetDB/tests/BugDay_2005-10-06_4.8/Tests/kill_0.SF-1314982.*
## Comment 4083
Date: 2006-01-13 23:33:36 +0100
From: @drstmane
Logged In: YES
user_id=572415
Fixed in CVS by Niels:
"Don't print anything after the client(0) is gone
Stop the server the hardway as soon as we are the last
interpreter"
## Comment 4084
Date: 2006-01-14 13:16:44 +0100
From: @drstmane
Logged In: YES
user_id=572415
Apparently, I was too quick/eager closing this one:
The testweb revels that it now (still) causes a segvault on
Darwin 8.4.0, Fedora Core 4, Gentoo 1.6.13, SuSE 9.3 & SuSE
9ES (all 32 bit), i.e., the same platforms that also
1292727 "Mserver segfault because of 'col_name'"
https://sourceforge.net/tracker/index.php?func=detail&aid=1292727&group_id=56967&atid=482468
segvaults on; hence both might be related...
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.32.32.d-Darwin8.4.0/tests_BugDay_2005-10-06_4.8/kill_0.SF-1314982.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.32.32.d-Fedora4/tests_BugDay_2005-10-06_4.8/kill_0.SF-1314982.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.32.32.d-Gentoo1.6.13/tests_BugDay_2005-10-06_4.8/kill_0.SF-1314982.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.32.32.d-SuSE9.3/tests_BugDay_2005-10-06_4.8/kill_0.SF-1314982.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.mTests103/GNU.32.32.d-SuSE9ES/tests_BugDay_2005-10-06_4.8/kill_0.SF-1314982.err.00.html
## Comment 4085
Date: 2006-01-14 13:35:40 +0100
From: @drstmane
Logged In: YES
user_id=572415
The same platforms segfault also with the test of http://sourceforge.net/support/tracker.php?aid=921173 "extremely long and complex query causes SEGFAULT"
https://sourceforge.net/tracker/index.php?func=detail&aid=921173&group_id=56967&atid=482468
## Comment 4086
Date: 2006-01-15 14:14:56 +0100
From: @drstmane
Logged In: YES
user_id=572415
Closed as the actual/original bug is fixed.
The segfault on some platforms is file in this new report
1406591 "several tests cause segfault on the same subset
of
platforms"
https://sourceforge.net/tracker/index.php?func=detail&aid=1406591&group_id=56967&atid=482468
## Comment 4087
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1314982 at http://sourceforge.net/support/tracker.php?aid=1314982
| kill(0) causes SEGFAULT | https://api.github.com/repos/MonetDB/MonetDB/issues/718/comments | 0 | 2020-11-30T08:50:35Z | 2024-06-27T11:06:38Z | https://github.com/MonetDB/MonetDB/issues/718 | 753,282,984 | 718 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-06 03:45:58 +0200
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2005-10-08 10:33:14 +0200
## Comment 4075
Date: 2005-10-06 15:45:58 +0200
From: @swingbit
*** This bug was initially reported as a 'BTW, this
also fails...' as a comment to a different bug
(933546). Here, it is re-opened a a new bug:
sql>create view m as select * from tables with check
option;
sql>select * from m;
MAPI = monetdb@localhost:45123
ACTION= mapi_fetch_line
QUERY = select * from m;
ERROR = Connection terminated
## Comment 4076
Date: 2005-10-06 15:57:17 +0200
From: @swingbit
Logged In: YES
user_id=883451
BugDay_2005-10-06: CLAIMED BY cornuz
BugDay_2005-10-06: TEST ADDED / SUCCESS
Test added for http://sourceforge.net/support/tracker.php?aid=1314951 as
sql/src/test/BugDay_2005-10-06_2.9.3/Tests/create_view_with_check_options.SF-1314951.*
## Comment 4077
Date: 2005-10-06 23:07:23 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed, ie removed with check options from views query.
## Comment 4078
Date: 2005-12-19 16:56:10 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
sql/src/test/BugDay_2005-10-06_2.9.3/Tests/create_view_with_check_options.SF-1314951.*
## Comment 4079
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1314951 at http://sourceforge.net/support/tracker.php?aid=1314951
| create view with check options | https://api.github.com/repos/MonetDB/MonetDB/issues/717/comments | 0 | 2020-11-30T08:50:32Z | 2024-06-27T11:06:37Z | https://github.com/MonetDB/MonetDB/issues/717 | 753,282,943 | 717 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-06 03:40:03 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2005-10-08 10:32:50 +0200
## Comment 4070
Date: 2005-10-06 15:40:03 +0200
From: @drstmane
select not true;
triggers the error:
ERROR = !syntax error, unexpected BOOL_TRUE, expecting
EXISTS in: "select not true"
instead of simply returning "false".
## Comment 4071
Date: 2005-10-06 15:46:03 +0200
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-10-06: CLAIMED BY stmane
BugDay_2005-10-06: TEST ADDED / FAILES
sql/src/test/BugDay_2005-10-06_2.9.3/Tests/select_not_true.SF-1314945.*
this is a new bug which still has to be fixed.
## Comment 4072
Date: 2005-10-06 23:39:36 +0200
From: @njnes
Logged In: YES
user_id=43556
added handeling of 'not' in the parser
## Comment 4073
Date: 2005-12-19 16:55:30 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
sql/src/test/BugDay_2005-10-06_2.9.3/Tests/select_not_true.SF-1314945.*
## Comment 4074
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1314945 at http://sourceforge.net/support/tracker.php?aid=1314945
| SQL: "select not true;" failes | https://api.github.com/repos/MonetDB/MonetDB/issues/716/comments | 0 | 2020-11-30T08:50:29Z | 2024-06-27T11:06:36Z | https://github.com/MonetDB/MonetDB/issues/716 | 753,282,920 | 716 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-06 02:56:30 +0200
From: roeland <<rweve>>
To: @njnes
Version: -- development
Last updated: 2005-10-27 01:59:42 +0200
## Comment 4061
Date: 2005-10-06 14:56:30 +0200
From: roeland <<rweve>>
Connection warning: database specifier not supported on
this server (mserver_sql
), protocol version 4
Welcome to the MonetDB interactive JDBC terminal!
Database: MonetDB 4.8.2
Driver: MonetDB Native Driver 1.2 (Blunt-SR1)
Type \q to quit, \h for a list of available commands
auto commit mode: on
monetdb-> create table test1 (testid int, testchar
varchar(255));
Operation successful
monetdb-> create table test2 (testid unknowntype,
testchar varchar(255));
Error: Connection reset (Mserver still alive?)
monetdb->
I know this is not SQL99, but the Mserver crashes
instead of reporting the sql is incorrect.
This also happens if the (incorrect) query is executed
in the MonetDB SQL client.
Operating System: Windows XP
## Comment 4062
Date: 2005-10-08 10:35:57 +0200
From: @njnes
Logged In: YES
user_id=43556
I cannot reproduce this bug.
## Comment 4063
Date: 2005-10-08 10:38:40 +0200
From: @grobian
Logged In: YES
user_id=963970
on windows?
## Comment 4064
Date: 2005-10-08 10:42:30 +0200
From: @njnes
Logged In: YES
user_id=43556
switched back to resolution None as I cannot test on windows.
## Comment 4065
Date: 2005-10-08 13:13:37 +0200
From: roeland <<rweve>>
Logged In: YES
user_id=1352508
Yes,
Operating System: Windows XP
## Comment 4066
Date: 2005-10-23 00:03:54 +0200
From: @njnes
Logged In: YES
user_id=43556
can anybody verify this bug on windows with the cvs head version
## Comment 4067
Date: 2005-10-27 13:59:42 +0200
From: @njnes
Logged In: YES
user_id=43556
fixed in the current (cvs head) version
## Comment 4068
Date: 2005-12-19 16:54:20 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / SUCCESS:
sql/src/test/BugDay_2005-12-19_2.9.3/Tests/crash_on_incorrect_SQL.SF-1314904.s*
## Comment 4069
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1314904 at http://sourceforge.net/support/tracker.php?aid=1314904
| Crash with incorrect SQL input | https://api.github.com/repos/MonetDB/MonetDB/issues/715/comments | 0 | 2020-11-30T08:50:26Z | 2024-06-27T11:06:35Z | https://github.com/MonetDB/MonetDB/issues/715 | 753,282,890 | 715 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-06 02:42:09 +0200
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2007-05-29 02:13:58 +0200
## Comment 4055
Date: 2005-10-06 14:42:09 +0200
From: @swingbit
MapiClient -l sql -u this_user_does_not_exist -P
this_pwd_does_not_exist ...
actually gives the prompt, instead of reporting a
connection error.
Then, it quits upon whatever input.
I'd add a test script, but I've no Idea how to....
## Comment 4056
Date: 2005-10-26 22:08:43 +0200
From: @njnes
Logged In: YES
user_id=43556
the error was handled inside the Mapi library. This is now
forwarded to the mapi client.
## Comment 4057
Date: 2005-12-19 16:49:46 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / POSTPONED:
need more time to think of a good test script...
## Comment 4058
Date: 2006-12-20 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 4059
Date: 2007-05-29 14:13:58 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
test script added to src/test/Users/Tests/unknown_user.SQL.py
## Comment 4060
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1314887 at http://sourceforge.net/support/tracker.php?aid=1314887
| SQL: MapiCient \"seems\" to accept wrong username/pwd | https://api.github.com/repos/MonetDB/MonetDB/issues/714/comments | 0 | 2020-11-30T08:50:23Z | 2024-06-27T11:06:34Z | https://github.com/MonetDB/MonetDB/issues/714 | 753,282,856 | 714 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-06 10:29:27 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-10-08 10:29:49 +0200
## Comment 4048
Date: 2005-10-06 10:29:27 +0200
From: @grobian
% java -jar jars/MonetDB_JDBC.jar
Connection warning: database specifier not supported on
this server (mserver_sql), protocol version 4
Welcome to the MonetDB interactive JDBC terminal!
Database: MonetDB 4.9.3
Driver: MonetDB Native Driver 1.2 (Blunt+)
Type \q to quit, \h for a list of available commands
auto commit mode: on
monetdb-> set explain='performance';
1 affected row
monetdb-> select 1;
+--------------+
| single_value |
+==============+
| 1 |
+--------------+
1 row
monetdb-> select * from history;
+---------------------+--------+------------+------------+------------+------------+---------+
| start | query | parse | optimize
| exec | total | user |
+=====================+========+============+============+============+============+=========+
| 2005-10-06 08:27:23.0 | (null) | 0 |
0 | 11456163 | -11456163 | monetdb |
+---------------------+--------+------------+------------+------------+------------+---------+
1 row
monetdb-> select count(*) from tables;
+------------+
| count_id |
+============+
| 23 |
+------------+
1 row
monetdb-> select * from history;
+---------------------+--------+------------+------------+------------+------------+---------+
| start | query | parse | optimize
| exec | total | user |
+=====================+========+============+============+============+============+=========+
| 2005-10-06 08:27:23.0 | (null) | 0 |
0 | 11456163 | -11456163 | monetdb |
+---------------------+--------+------------+------------+------------+------------+---------+
1 row
monetdb->
The values in the history table look extremely weird
(negative for example) to me, as well as no new entries
seem to be added.
## Comment 4049
Date: 2005-10-06 12:16:44 +0200
From: roeland <<rweve>>
Logged In: YES
user_id=1352508
The performance feature only seems to work with MonetDB
4.9.3 and not with 4.8.2:
Connection warning: database specifier not supported on this
server (mserver_sql), protocol version 4
Welcome to the MonetDB interactive JDBC terminal!
Database: MonetDB 4.8.2
Driver: MonetDB Native Driver 1.2 (Blunt-SR1)
Type \q to quit, \h for a list of available commands
auto commit mode: on
monetdb-> select count(*) from history;
+-------------+
| count_start |
+=============+
| 0 |
+-------------+
1 row
monetdb-> set explain='performance';
monetdb-> select 1;
+--------------+
| single_value |
+==============+
| 1 |
+--------------+
1 row
monetdb-> select count(*) from history;
+-------------+
| count_start |
+=============+
| 0 |
+-------------+
I do not get a '1 affected row' message after executing 'set
explain='performance';'.
It should be nicer to give a error/warning message that this
feature is not implemented, rather than giving no message at
all (or am I missing something?).
Roeland
## Comment 4050
Date: 2005-10-06 12:27:48 +0200
From: @grobian
Logged In: YES
user_id=963970
try a query (select 1 or select count(*) from tables) and
see if the history table is still empty.
The absence of an affected row count or anything else,
doesn't really make a point here.
## Comment 4051
Date: 2005-10-06 12:38:19 +0200
From: roeland <<rweve>>
Logged In: YES
user_id=1352508
I tried all sort of different queries but the history table
still stays empty. I've just put the count(*) statements
here for layout purposes.
Here goes the example you've tried as well:
Connection warning: database specifier not supported on this
server (mserver_sql
), protocol version 4
Welcome to the MonetDB interactive JDBC terminal!
Database: MonetDB 4.8.2
Driver: MonetDB Native Driver 1.2 (Blunt-SR1)
Type \q to quit, \h for a list of available commands
auto commit mode: on
monetdb-> set explain='performance';
monetdb-> select 1;
+--------------+
| single_value |
+==============+
| 1 |
+--------------+
1 row
monetdb-> select * from history;
+---------------------+--------+------------+------------+------------+---------
---+--------+
| start | query | parse | optimize |
exec | total
| user |
+=====================+========+============+============+============+=========
===+========+
+---------------------+--------+------------+------------+------------+---------
---+--------+
0 rows
monetdb-> select count(*) from tables;
+------------+
| count_id |
+============+
| 31 |
+------------+
1 row
monetdb-> select * from history;
+---------------------+--------+------------+------------+------------+---------
---+--------+
| start | query | parse | optimize |
exec | total
| user |
+=====================+========+============+============+============+=========
===+========+
+---------------------+--------+------------+------------+------------+---------
---+--------+
0 rows
---------------------------
some more examples:
---------------------------
monetdb-> CREATE TABLE url_click_B (hour_id INT, url
VARCHAR(255));
Operation successful
monetdb-> select * from history;
+---------------------+--------+------------+------------+------------+---------
---+--------+
| start | query | parse | optimize |
exec | total
| user |
+=====================+========+============+============+============+=========
===+========+
+---------------------+--------+------------+------------+------------+---------
---+--------+
0 rows
monetdb-> insert into url_click_b values (12,'test');
1 affected row
monetdb-> select * from history;
+---------------------+--------+------------+------------+------------+---------
---+--------+
| start | query | parse | optimize |
exec | total
| user |
+=====================+========+============+============+============+=========
===+========+
+---------------------+--------+------------+------------+------------+---------
---+--------+
0 rows
monetdb-> select * from url_click_b;
+------------+--------+
| hour_id | url |
+============+========+
| 12 | test |
+------------+--------+
1 row
monetdb-> select * from history;
+---------------------+--------+------------+------------+------------+---------
---+--------+
| start | query | parse | optimize |
exec | total
| user |
+=====================+========+============+============+============+=========
===+========+
+---------------------+--------+------------+------------+------------+---------
---+--------+
0 rows
monetdb->
## Comment 4052
Date: 2005-10-08 10:29:49 +0200
From: @njnes
Logged In: YES
user_id=43556
changed all preformance/history/profile to one keyword 'profile'
So it is now possible to profile a query using for example
profile select 1;
Or a set of queries using
set explain='profile';
select 1;
The results of profiling are stored in a profile table which
can be queried using
select * from profile;
BEWARE the profile table is a user temporary table, meaning
the profile results will be gone as soon as you exit your
session.
BugDay Claimed Niels DONE
Script is in test/bugs/profile_bug-ID.1314649
## Comment 4053
Date: 2005-12-19 16:43:47 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: ALREADY IN TESTWEB:
sql/src/test/bugs/Tests/profile_bug-SF.1314649.sql
## Comment 4054
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1314649 at http://sourceforge.net/support/tracker.php?aid=1314649
| SQL: history/performance 'feature' is broken | https://api.github.com/repos/MonetDB/MonetDB/issues/713/comments | 0 | 2020-11-30T08:50:19Z | 2024-06-27T11:06:33Z | https://github.com/MonetDB/MonetDB/issues/713 | 753,282,819 | 713 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-06 10:26:59 +0200
From: @grobian
To: @njnes
Version: -- development
Last updated: 2005-10-23 12:05:19 +0200
## Comment 4044
Date: 2005-10-06 10:26:59 +0200
From: @grobian
% java -jar jars/MonetDB_JDBC.jar
Connection warning: database specifier not supported on
this server (mserver_sql), protocol version 4
Welcome to the MonetDB interactive JDBC terminal!
Database: MonetDB 4.9.3
Driver: MonetDB Native Driver 1.2 (Blunt+)
Type \q to quit, \h for a list of available commands
auto commit mode: on
monetdb-> select * from tables limit 1;
+------------+---------+------------+--------+---------+--------+--------+-----------+
| id | name | schema_id | query | istable
| system | clear | temporary |
+============+=========+============+========+=========+========+========+===========+
| <NULL> | <NULL> | <NULL> | <NULL> | <NULL>
| <NULL> | <NULL> | <NULL> |
+------------+---------+------------+--------+---------+--------+--------+-----------+
1 row
monetdb-> select * from tables limit 2;
+------------+---------+------------+--------+---------+--------+--------+-----------+
| id | name | schema_id | query | istable
| system | clear | temporary |
+============+=========+============+========+=========+========+========+===========+
| <NULL> | <NULL> | <NULL> | <NULL> | <NULL>
| <NULL> | <NULL> | <NULL> |
+------------+---------+------------+--------+---------+--------+--------+-----------+
1 row
monetdb->
something tells me this is not healthy. A normal
select without LIMIT gives correct results.
## Comment 4045
Date: 2005-10-23 00:05:19 +0200
From: @njnes
Logged In: YES
user_id=43556
same fix as the other limit bug.
## Comment 4046
Date: 2005-12-19 16:42:51 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: TEST ADDED / SUCCESS:
sql/src/test/BugDay_2005-12-19_2.9.3/Tests/weird_reponse_on_limit.SF-1314643.s*
## Comment 4047
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1314643 at http://sourceforge.net/support/tracker.php?aid=1314643
| SQL: weird response on LIMIT query | https://api.github.com/repos/MonetDB/MonetDB/issues/712/comments | 0 | 2020-11-30T08:50:16Z | 2024-06-27T11:06:32Z | https://github.com/MonetDB/MonetDB/issues/712 | 753,282,782 | 712 |
[
"MonetDB",
"MonetDB"
] | Date: 2005-10-04 10:55:09 +0200
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2005-10-04 11:21:36 +0200
## Comment 4039
Date: 2005-10-04 22:55:09 +0200
From: @drstmane
since revision 1.25, src/modules/plain/url.mx fails to
compile with:
========
/bin/sh ../../../libtool --tag=CC --mode=compile gcc
-m64 -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain
-I../../..
-I/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain
-I../../common -I../../gdk -I../../monet
-DLIBURL -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer
-finline-functions -falign-loops=4 -falign-jumps=4
-falign-functions=4 -fexpensive-optimizations
-funroll-loops -frerun-cse-after-loop
-frerun-loop-opt -Werror-implicit-function-declaration
-Werror -Wno-unused-function -Wno-unused-label
-D_REENTRANT -c -o lib_url_la-url.glue.lo `test -f
'url.glue.c' || echo
'/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain/'`url.glue.c
gcc -m64 -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain
-I../../..
-I/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain
-I../../common -I../../gdk -I../../monet -DLIBURL -O2
-std=c99 -Wall -W -O6 -fomit-frame-pointer
-finline-functions -falign-loops=4 -falign-jumps=4
-falign-functions=4 -fexpensive-optimizations
-funroll-loops -frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -D_REENTRANT -c
url.glue.c -fPIC -DPIC -o .libs/lib_url_la-url.glue.o
/bin/sh ../../../libtool --tag=CC --mode=compile gcc
-m64 -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain
-I../../..
-I/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain
-I../../common -I../../gdk -I../../monet
-DLIBURL -O2 -std=c99 -Wall -W -O6
-fomit-frame-pointer
-finline-functions -falign-loops=4 -falign-jumps=4
-falign-functions=4 -fexpensive-optimizations
-funroll-loops -frerun-cse-after-loop
-frerun-loop-opt -Werror-implicit-function-declaration
-Werror -Wno-unused-function -Wno-unused-label
-D_REENTRANT -c -o lib_url_la-url.lo `test -f 'url.c'
|| echo
'/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain/'`url.c
gcc -m64 -DHAVE_CONFIG_H -I.
-I/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain
-I../../..
-I/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain
-I../../common -I../../gdk -I../../monet -DLIBURL -O2
-std=c99 -Wall -W -O6 -fomit-frame-pointer
-finline-functions -falign-loops=4 -falign-jumps=4
-falign-functions=4 -fexpensive-optimizations
-funroll-loops -frerun-cse-after-loop -frerun-loop-opt
-Werror-implicit-function-declaration -Werror
-Wno-unused-function -Wno-unused-label -D_REENTRANT -c
url.c -fPIC -DPIC -o .libs/lib_url_la-url.o
cc1: warnings being treated as errors
/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain/url.mx:
In function ‘url_getQueryArg’:
/export/scratch0/monet/monet.GNU.64.64.d.4511/MonetDB/src/modules/plain/url.mx:514:
warning: ‘unescapedval’ is used uninitialized in this
function
make[5]: *** [lib_url_la-url.lo] Error 1
========
See also
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB/.GNU.64.64.d-Fedora4/make.out
## Comment 4040
Date: 2005-10-04 23:21:36 +0200
From: @yzchang
Logged In: YES
user_id=341633
Sorry, is now fixed in CVS.
## Comment 4041
Date: 2005-10-04 23:50:37 +0200
From: @drstmane
Logged In: YES
user_id=572415
Thanks for the quick fix, Jennie.
(I actually felt free to "polish" the code a bit more ... ;-))
## Comment 4042
Date: 2005-12-19 16:39:49 +0100
From: @drstmane
Logged In: YES
user_id=572415
BugDay_2005-12-19, stmane: NO TEST / COMPILATION
## Comment 4043
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 1313271 at http://sourceforge.net/support/tracker.php?aid=1313271
| url.mx fails to compile | https://api.github.com/repos/MonetDB/MonetDB/issues/711/comments | 0 | 2020-11-30T08:50:13Z | 2024-06-27T11:06:31Z | https://github.com/MonetDB/MonetDB/issues/711 | 753,282,745 | 711 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.