Hi MonetDB people,
I encountered this TODO message while running a query:
sql>SELECT objects.name
more> FROM sys.keys, sys.objects, sys.tables, sys.schemas
more> WHERE sys.keys.id = objects.id
more> AND keys.table_id = tables.id
more> AND tables.schema_id = schemas.id
more> AND keys.type = 0
more> AND tables.id = 11323;
TODO: column names of level >= 3
--
Gijs Molenaar
http://www.astro.uva.nl/people/gijs-molenaar/
Hi MonetDB people,
Do the TIME(STAMP) types support microsecond precision? They accept a
'postint' argument, but no matter what I set it to it looks like the
timestamp is rounded to milliseconds.
greetings,
--
Gijs Molenaar
http://www.astro.uva.nl/people/gijs-molenaar/
The MonetDB team at CWI/MonetDB BV is pleased to announce the
Feb2013-SP4 bugfix release of the MonetDB suite of programs.
More information about MonetDB can be found on our website at
<http://www.monetdb.org/>.
For details on this release, please see the release notes at
<http://www.monetdb.org/Downloads/ReleaseNotes>.
As usual, the download location is <http://dev.monetdb.org/downloads/>.
Feb 2013-SP4 bugfix release
Merovingian
* monetdb now no longer compresses output when not connected to a
terminal, bug #3292
Bug Fixes
* 2781: SQL localtime() returns GMT time
* 2962: client timezone information needs to be handled also for
modifications to timestamp values
* 3232: The function weekofyear returns results not according to the
iso 8601 standard
* 3255: M5 tests inlineFunction & ifthencst fail since changeset
207ed7d7e03a
* 3292: monetdb status should print full line
* 3307: distinct multicolumn performance and implementation
suggestion for count distinct
* 3310: Cast value to integer gives wrong result
* 3311: strLength assertion on join and concat
* 3313: Assertion in rel2bin_project
* 3315: Incorrect behavior with subqueries in DELETE
* 3317: correlated subselect does not work
* 3318: UPDATE does not work with DECLEAREd TABLE in FUNCTION
* 3319: UNIQUE column in DECLAREd TABLE in FUNCTION results in
segfault
* 3329: Function AVG fails during runtime in a procedure
* 3330: Corrupt mitosis plan with group-by query
* 3332: MEDIAN: no such operator 'median(decimal)'
* 3336: DB files not removed if all rows are deleted, even after
restart
* 3337: Monet ODBC gives wrong schema information
* 3339: Segvault in complex function call
* 3340: crash on seeming incorrect SQL query
* 3341: segfault caused by select rank() on a newly-loaded table
* 3342: incorrect automatic cast from decimal to tinyint
* 3345: copy binary into fails with the wrong error message
* 3346: Deadlock in mal_dataflow's q_dequeue() (SciQL-2 branch)
* 3348: SQL: LIKE incorrect with _
* 3349: When selecting everything from a joined result, column
contents are incorrect in one of my use cases.
* 3351: gzip'ed files cannot be bulkloaded into DB
* 3352: Median function with decimal type doesn't work
* 3353: Readonly tables call for UNSET
* 3354: Introduce query time-out
* 3358: Remote client connection stays in CLOSE_WAIT state
* 3360: uninitialized memory causing bad output in query plans
* 3362: ALTER TABLE operations silently remove previously set READ
ONLY property
* 3363: a join causes SIGSEGV after creation of Unique Key
* 3367: Fully qualified order by column gives "relational query
without result"
* 3369: \0 Byte appears in MAPI
Hi ,
During my periodic search for "Is a new monetdb build is going to be released soon" , I found one is placed under testing recently.
Is there a place where it can be seen and reviewed what kind of features/fixes are expected in upcoming release? That will be a great help for some of the folks like me to plan ahead!
Regards,
Ashish
Dear MonetDB Developers,
I'm doing some research about colmn oriented databases and I began with MonetDB.
In fact I would like to know how can I get the real disk space used to store a given tabel??
After some research on the web I found that I can use the storage table as follow:
select "schema", "table", sum("columnsize") as size from storage() group by "schema","table" having "schema" <> 'tmp';
But it seems to me that this is something like a "logical" storage space without any compression (all columns with type "int" have the same size), is there a way to know the actual disk space used by MonetDB to store a table??
Thank you in advance for your help,
RegardsBaraa
On 9/8/13 8:45 PM, Stefan Manegold wrote:
> Changeset: a331af9e20ea for MonetDB
> URL: http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a331af9e20ea
> Modified Files:
> monetdb5/modules/mal/batcalc.mal
> monetdb5/modules/mal/batcalc.mal.sh
> Branch: int128
> Log Message:
>
> backing-out changeset 77c9c3da562c:
>
> Unfortunately, MonetDB / mserver5 / MAL parser / MAL interpreter
> is/are unable to handle the new monetdb5/modules/mal/batcalc.mal
> correctly.
>
> When starting the server, it complains about
> !TypeException:jaqlfunc.count[7]:'batcalc.lng' undefined in: r:any := batcalc.lng(x:bat[:oid,:wrd])
> although the respective batcalc.lng(x:bat[:oid,:wrd])
> is in monetdb5/modules/mal/batcalc.mal .
> Some tests indicate that the systems (MAL parser ?)
> has some problems handling MAL files >= ~1 MB
> correctly, but I did not manage to locate the
> actual nature or origin of the problem.
>
> Any help to get this working is highly appreciated.
Most likely it is in mal_import where the complete mal file is loaded first
Hello All,
Has anyone managed to auto-vectorize (automatic SIMDfication) any of the loops in the kernel? If yes, I would like to know the complier and the complier flags used.
Thanks,
Geoffrey