[Monetdb-developers] MonetDB release meeting
MonetDB developers On wednessday morning (june 7) from 10:00 till 12:00 we will have another MonetDB meeting. Reason we missed our target freeze date and therefor will miss the release date of end of june. So we should reset those dates, assess the tasks at hand and possibly resuffle some of the work. Niels -- Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes@cwi.nl
Niels, I will not be back in A'dam on Wednesday (most probaly only next Monday), but I'll be online. Hence, we might consider setting up a skype (or telephone) connection from C0.01 to me so that I could join the meeting remotely. ... provided, it is technically possible and "convenient". Stefan On Mon, Jun 05, 2006 at 12:13:24PM +0200, Niels Nes wrote:
MonetDB developers
On wednessday morning (june 7) from 10:00 till 12:00 we will have another MonetDB meeting.
Reason we missed our target freeze date and therefor will miss the release date of end of june. So we should reset those dates, assess the tasks at hand and possibly resuffle some of the work.
Niels
--
Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes@cwi.nl
-- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
LS, To speedup a discussion on Wednesday and to give everyone (offline) an opportunity to contribute, I would greatly appreciate an a priori email discussion to identify scope of delay, tasks pending, and possible actions to be undertaken. This way, the meeting can concentrate on decision making, rather then status assessment. From our website: -------------------------------------------------------------------- Items planned for release V4.12 25-06-2006 This release is geared at consolidation of the XQuery functionality. * XQuery: XUpdate and API's * XQuery: support for large numbers of small documents * XQuery: standoff, extension to the XPath axis * Kernel: caching small garbaged BATs for speed * APIs: Xrpc (remote procedure using soap) * SQL: support for triggers * SQL: full support for global and local temporary tables * Kernel: support for fragmented memory mapped BATs * Mapi: an other round of performance improvements * 64 bit Windows installer. * Kernel: cleanup (removal of uchr, new types byte and word). Items planned for later and upon need * SQL: support for the XMLtype * SQL: Stored procedures. * A basic GIS module. * Improve bulk-loading stream-based processing * DatabasePool, to manage multiple Mserver instances * Re-organize and redo performance benchmarks * Migration tools from Oracle, MS SQL Server, MySQL, and PostgreSQL Alpha release of the MonetDB V5 05-05-2006 This is an alpha release for the new strand and provides a fully functional MonetDB/SQL/JDBC setup. Until the official release date, the code is available to our partners on a need to know basis. A peek preview into the new architecture and its impact on you application setting can obtained from the (highly volatile) MonetDB Version 5 Reference Manual. ----------------------------- End 'Quote' ---------------------------- Please could each of you responsible for the item summarize its state, roadblocks, and time needed to prepare for a freeze/release. Also indicate features that should start finding its place on the list for the next release(s). Note, we should adhire to the modus in open-source software land to release repeatedly. Not when everything is carved in concrete. In this respect I welcome 'keyword-focussed' improvements since the previous release that are worthwhile for others (e.g. SQL catalog management has been revamped into a full delta-processing scheme. This made triggers possible.) I wouldn't be surprised if the First-price may not be in immediate reach, but that sufficient meat is on the table to get a release out. regards, Martin Niels Nes wrote:
MonetDB developers
On wednessday morning (june 7) from 10:00 till 12:00 we will have another MonetDB meeting.
Reason we missed our target freeze date and therefor will miss the release date of end of june. So we should reset those dates, assess the tasks at hand and possibly resuffle some of the work.
Niels
Alpha release of the MonetDB V5 05-05-2006 - Responsible: Martin/Niels - Delay: mostly due to agenda constraints - Status: -- M5 tree has been cleaned out to enable selective dissemination of a workable system. -- M5/SQL quality >= M4/SQL -- Testweb is 99% clean - New Date: any day now - Roadblocks: --the envisioned meta-bootstrap is not available, which requires users to be aware on how to compile/install SQL and M4 kernel [Stefan? weeks into the future] -- the distribution should be tested on Windows as well. [Sjoerd? days into the future?] -Features foreseen in 2006: -- SQL documentation completion -- Replication Services -- Distributed Query Execution -- Merge with (revamped) MonetDB web -- Datacell demo application As soon as the first XQuery examples run, the full-release date will be set, marking the transition to the 5-line and consequential roll-forward of other bits & pieces. regards, Martin Martin Kersten wrote:
LS,
To speedup a discussion on Wednesday and to give everyone (offline) an opportunity to contribute, I would greatly appreciate an a priori email discussion to identify scope of delay, tasks pending, and possible actions to be undertaken.
This way, the meeting can concentrate on decision making, rather then status assessment.
From our website: -------------------------------------------------------------------- Items planned for release V4.12 25-06-2006 This release is geared at consolidation of the XQuery functionality.
* XQuery: XUpdate and API's * XQuery: support for large numbers of small documents * XQuery: standoff, extension to the XPath axis * Kernel: caching small garbaged BATs for speed * APIs: Xrpc (remote procedure using soap) * SQL: support for triggers * SQL: full support for global and local temporary tables * Kernel: support for fragmented memory mapped BATs * Mapi: an other round of performance improvements * 64 bit Windows installer. * Kernel: cleanup (removal of uchr, new types byte and word).
Items planned for later and upon need
* SQL: support for the XMLtype * SQL: Stored procedures. * A basic GIS module. * Improve bulk-loading stream-based processing * DatabasePool, to manage multiple Mserver instances * Re-organize and redo performance benchmarks * Migration tools from Oracle, MS SQL Server, MySQL, and PostgreSQL
Alpha release of the MonetDB V5 05-05-2006
This is an alpha release for the new strand and provides a fully functional MonetDB/SQL/JDBC setup. Until the official release date, the code is available to our partners on a need to know basis. A peek preview into the new architecture and its impact on you application setting can obtained from the (highly volatile) MonetDB Version 5 Reference Manual. ----------------------------- End 'Quote' ----------------------------
Please could each of you responsible for the item summarize its state, roadblocks, and time needed to prepare for a freeze/release.
Also indicate features that should start finding its place on the list for the next release(s).
Note, we should adhire to the modus in open-source software land to release repeatedly. Not when everything is carved in concrete. In this respect I welcome 'keyword-focussed' improvements since the previous release that are worthwhile for others (e.g. SQL catalog management has been revamped into a full delta-processing scheme. This made triggers possible.)
I wouldn't be surprised if the First-price may not be in immediate reach, but that sufficient meat is on the table to get a release out.
regards, Martin
Niels Nes wrote:
MonetDB developers
On wednessday morning (june 7) from 10:00 till 12:00 we will have another MonetDB meeting.
Reason we missed our target freeze date and therefor will miss the release date of end of june. So we should reset those dates, assess the tasks at hand and possibly resuffle some of the work.
Niels
Hi all, Was busy with CIKM deadline on monday, and today in Twente at TDM.. so now my input. For the XQuery release, the following input: - finish commit and recovery MUST 3 weeks peter,sjoerd (help from Niels?) - fixing of the indexing strategy under updates MUST 1 week stefan (sjoerd?) - adapting scj for candidate lists to be resistent against holes SHOULD 1 day stefan - finishing the multi-document support (shredding, api, parent/anc steps) MUST 1 week peter (sjoerd?) - stabilizing SOAP MUST 3 weeks jennie (can be done in testing phase) - porting standoff to updates MUST 1 week? wouter - making standoff a runtime setting purely SHOULD ? wouter - implementing flexible standoff 'declare option' SHOULD ? wouter - support for w3c update syntax DONE - performance testing under read-only scenarios (at least XMark) MUST 1 week, sjoerd,peter,stefan - formulating some benchmark update queries, testing those, fixing most pressing issues MUST 3 weeks, sjoerd,peter,stefan plus documentation.. -----Original Message----- From: Martin Kersten [mailto:Martin.Kersten@cwi.nl] Sent: 05 June 2006 14:23 To: Martin Kersten Cc: Niels Nes; Peter Boncz; Stefan Manegold; Sjoerd Mullender; Fabian Groffen; Marcin Zukowski; Ying Zhang; Milena Ivanova; sandor@cwi.nl; Stratos Idreos; Romulo Antonio Goncalves; Monica Manzano Hidalgo; monetdb-developers@lists.sourceforge.net Subject: Re: MonetDB release meeting Alpha release of the MonetDB V5 05-05-2006 - Responsible: Martin/Niels - Delay: mostly due to agenda constraints - Status: -- M5 tree has been cleaned out to enable selective dissemination of a workable system. -- M5/SQL quality >= M4/SQL -- Testweb is 99% clean - New Date: any day now - Roadblocks: --the envisioned meta-bootstrap is not available, which requires users to be aware on how to compile/install SQL and M4 kernel [Stefan? weeks into the future] -- the distribution should be tested on Windows as well. [Sjoerd? days into the future?] -Features foreseen in 2006: -- SQL documentation completion -- Replication Services -- Distributed Query Execution -- Merge with (revamped) MonetDB web -- Datacell demo application As soon as the first XQuery examples run, the full-release date will be set, marking the transition to the 5-line and consequential roll-forward of other bits & pieces. regards, Martin Martin Kersten wrote:
LS,
To speedup a discussion on Wednesday and to give everyone (offline) an opportunity to contribute, I would greatly appreciate an a priori email discussion to identify scope of delay, tasks pending, and possible actions to be undertaken.
This way, the meeting can concentrate on decision making, rather then status assessment.
From our website: -------------------------------------------------------------------- Items planned for release V4.12 25-06-2006 This release is geared at consolidation of the XQuery functionality.
* XQuery: XUpdate and API's * XQuery: support for large numbers of small documents * XQuery: standoff, extension to the XPath axis * Kernel: caching small garbaged BATs for speed * APIs: Xrpc (remote procedure using soap) * SQL: support for triggers * SQL: full support for global and local temporary tables * Kernel: support for fragmented memory mapped BATs * Mapi: an other round of performance improvements * 64 bit Windows installer. * Kernel: cleanup (removal of uchr, new types byte and word).
Items planned for later and upon need
* SQL: support for the XMLtype * SQL: Stored procedures. * A basic GIS module. * Improve bulk-loading stream-based processing * DatabasePool, to manage multiple Mserver instances * Re-organize and redo performance benchmarks * Migration tools from Oracle, MS SQL Server, MySQL, and PostgreSQL
Alpha release of the MonetDB V5 05-05-2006
This is an alpha release for the new strand and provides a fully functional MonetDB/SQL/JDBC setup. Until the official release date, the code is available to our partners on a need to know basis. A peek preview into the new architecture and its impact on you application setting can obtained from the (highly volatile) MonetDB Version 5 Reference Manual. ----------------------------- End 'Quote' ----------------------------
Please could each of you responsible for the item summarize its state, roadblocks, and time needed to prepare for a freeze/release.
Also indicate features that should start finding its place on the list for the next release(s).
Note, we should adhire to the modus in open-source software land to release repeatedly. Not when everything is carved in concrete. In this respect I welcome 'keyword-focussed' improvements since the previous release that are worthwhile for others (e.g. SQL catalog management has been revamped into a full delta-processing scheme. This made triggers possible.)
I wouldn't be surprised if the First-price may not be in immediate reach, but that sufficient meat is on the table to get a release out.
regards, Martin
Niels Nes wrote:
MonetDB developers
On wednessday morning (june 7) from 10:00 till 12:00 we will have another MonetDB meeting.
Reason we missed our target freeze date and therefor will miss the release date of end of june. So we should reset those dates, assess the tasks at hand and possibly resuffle some of the work.
Niels
On 06/06/2006 07:17 PM, Peter Boncz wrote:
Hi all,
Was busy with CIKM deadline on monday, and today in Twente at TDM.. so now my input.
For the XQuery release, the following input:
- finish commit and recovery MUST 3 weeks peter,sjoerd (help from Niels?) - fixing of the indexing strategy under updates MUST 1 week stefan (sjoerd?) - adapting scj for candidate lists to be resistent against holes SHOULD 1 day stefan - finishing the multi-document support (shredding, api, parent/anc steps) MUST 1 week peter (sjoerd?) - stabilizing SOAP MUST 3 weeks jennie (can be done in testing phase) - porting standoff to updates MUST 1 week? wouter - making standoff a runtime setting purely SHOULD ? wouter - implementing flexible standoff 'declare option' SHOULD ? wouter - support for w3c update syntax DONE
There is a slight misconception here: the update syntax implementation is not yet done. The syntax is recognized, but not all queries that I have tried can yet be compiled. Furthermore, the MIL code that is behind it all isn't complete yet either.
- performance testing under read-only scenarios (at least XMark) MUST 1 week, sjoerd,peter,stefan - formulating some benchmark update queries, testing those, fixing most pressing issues MUST 3 weeks, sjoerd,peter,stefan
plus documentation..
-----Original Message----- From: Martin Kersten [mailto:Martin.Kersten@cwi.nl] Sent: 05 June 2006 14:23 To: Martin Kersten Cc: Niels Nes; Peter Boncz; Stefan Manegold; Sjoerd Mullender; Fabian Groffen; Marcin Zukowski; Ying Zhang; Milena Ivanova; sandor@cwi.nl; Stratos Idreos; Romulo Antonio Goncalves; Monica Manzano Hidalgo; monetdb-developers@lists.sourceforge.net Subject: Re: MonetDB release meeting
Alpha release of the MonetDB V5 05-05-2006 - Responsible: Martin/Niels - Delay: mostly due to agenda constraints - Status: -- M5 tree has been cleaned out to enable selective dissemination of a workable system. -- M5/SQL quality >= M4/SQL -- Testweb is 99% clean - New Date: any day now
- Roadblocks: --the envisioned meta-bootstrap is not available, which requires users to be aware on how to compile/install SQL and M4 kernel [Stefan? weeks into the future] -- the distribution should be tested on Windows as well. [Sjoerd? days into the future?]
-Features foreseen in 2006: -- SQL documentation completion -- Replication Services -- Distributed Query Execution -- Merge with (revamped) MonetDB web -- Datacell demo application
As soon as the first XQuery examples run, the full-release date will be set, marking the transition to the 5-line and consequential roll-forward of other bits & pieces.
regards, Martin Martin Kersten wrote:
LS,
To speedup a discussion on Wednesday and to give everyone (offline) an opportunity to contribute, I would greatly appreciate an a priori email discussion to identify scope of delay, tasks pending, and possible actions to be undertaken.
This way, the meeting can concentrate on decision making, rather then status assessment.
From our website: -------------------------------------------------------------------- Items planned for release V4.12 25-06-2006 This release is geared at consolidation of the XQuery functionality.
* XQuery: XUpdate and API's * XQuery: support for large numbers of small documents * XQuery: standoff, extension to the XPath axis * Kernel: caching small garbaged BATs for speed * APIs: Xrpc (remote procedure using soap) * SQL: support for triggers * SQL: full support for global and local temporary tables * Kernel: support for fragmented memory mapped BATs * Mapi: an other round of performance improvements * 64 bit Windows installer. * Kernel: cleanup (removal of uchr, new types byte and word).
Items planned for later and upon need
* SQL: support for the XMLtype * SQL: Stored procedures. * A basic GIS module. * Improve bulk-loading stream-based processing * DatabasePool, to manage multiple Mserver instances * Re-organize and redo performance benchmarks * Migration tools from Oracle, MS SQL Server, MySQL, and PostgreSQL
Alpha release of the MonetDB V5 05-05-2006
This is an alpha release for the new strand and provides a fully functional MonetDB/SQL/JDBC setup. Until the official release date, the code is available to our partners on a need to know basis. A peek preview into the new architecture and its impact on you application setting can obtained from the (highly volatile) MonetDB Version 5 Reference Manual. ----------------------------- End 'Quote' ----------------------------
Please could each of you responsible for the item summarize its state, roadblocks, and time needed to prepare for a freeze/release.
Also indicate features that should start finding its place on the list for the next release(s).
Note, we should adhire to the modus in open-source software land to release repeatedly. Not when everything is carved in concrete. In this respect I welcome 'keyword-focussed' improvements since the previous release that are worthwhile for others (e.g. SQL catalog management has been revamped into a full delta-processing scheme. This made triggers possible.)
I wouldn't be surprised if the First-price may not be in immediate reach, but that sufficient meat is on the table to get a release out.
regards, Martin
Niels Nes wrote:
MonetDB developers
On wednessday morning (june 7) from 10:00 till 12:00 we will have another MonetDB meeting.
Reason we missed our target freeze date and therefor will miss the release date of end of june. So we should reset those dates, assess the tasks at hand and possibly resuffle some of the work.
Niels
_______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- Sjoerd Mullender
On Tue, Jun 06, 2006 at 10:37:16PM +0200, Sjoerd Mullender wrote:
On 06/06/2006 07:17 PM, Peter Boncz wrote: [...]
For the XQuery release, the following input: [...] - fixing of the indexing strategy under updates MUST 1 week stefan (sjoerd?)
I hope to be back in A'dm next week (i.e., after June 12). Despite different planning, I won't be able to do much on this before then.
- adapting scj for candidate lists to be resistent against holes SHOULD 1 day stefan
Hm, IMHO scj is already hole-resistent --- at least it once was with the "old" hole implementation (w/o paging)... Maybe, there's an other / a new problem that I'm not aware of, yet ... [...]
- performance testing under read-only scenarios (at least XMark) MUST 1 week, sjoerd,peter,stefan
I'll be available once I'm back in A'dam.
- formulating some benchmark update queries, testing those, fixing most pressing issues MUST 3 weeks, sjoerd,peter,stefan
I'll be available once I'm back in A'dam.
plus documentation..
- plus functionality-, stability-, portability-testing (incl. creating new test cases!), and bug fixing. MUST, >= 3 week, ALL of us.
-----Original Message----- From: Martin Kersten [mailto:Martin.Kersten@cwi.nl] Sent: 05 June 2006 14:23 [...] Alpha release of the MonetDB V5 05-05-2006 [...] - Roadblocks: --the envisioned meta-bootstrap is not available, which requires users to be aware on how to compile/install SQL and M4 kernel [Stefan? weeks into the future]
The "meta-build" (not only "-bootstrap") is only for "convenience", hence not a (major) "roadblock". (Whoever wants/need to install M5 from (cvs-) sources, should be skilled enough to be able to install (buildtools,) MonetDB, monet5, sql (in that order) by running `(bootstrap;) configure; make; make install` for each of them. "end-users" should/will eventually get binary packages/installers that support "one-click-installation"... The "meta-build" is still on my todo list (though mainly to releave us from the "support-overhead"); however, under the current "circumstance", its priority has decreased...) [...]
Martin Kersten wrote: [...]
From our website: -------------------------------------------------------------------- Items planned for release V4.12 25-06-2006 This release is geared at consolidation of the XQuery functionality. [...] * Kernel: cleanup (removal of uchr, new types byte and word).
no news here. Unless there is an urgend request, I'd vote for scrapping it from this release, postponing it to the next one --- there are more important tasks for this release... [...] Stefan -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
- stabilizing SOAP MUST 3 weeks jennie (can be done in testing phase)
More on SOAP status: Implementation is done, indead needs more tests. Delayed because of my vacations. Last week when I came back from vacation, I was working on extending de tests with xmark queries, but I would not have time to finish it this week because of meetings, preparing presentation and poster. I will be on vacation from June 12th until June 23rd. From June 26th on, my work time will be more normal, since the end of my parents' vacation is then close. I would appreciate 3 weeks extension to make SOAP releasable. About the release meeting tomorrow: I will not be able to attend the meeting, although I would like to. Since Sjoerd will also not be able to attend the meeting at the suggested time, I'm wondering if it would be possible to shift the release meeting at Thursday afternoon, after TTT? Jennie
On 05-06-2006 14:03:51 +0200, Martin Kersten wrote:
From our website: -------------------------------------------------------------------- Items planned for release V4.12 25-06-2006 This release is geared at consolidation of the XQuery functionality.
* XQuery: XUpdate and API's * XQuery: support for large numbers of small documents * XQuery: standoff, extension to the XPath axis * Kernel: caching small garbaged BATs for speed * APIs: Xrpc (remote procedure using soap) * SQL: support for triggers This is not in there, I think, and I also guess won't be in. * SQL: full support for global and local temporary tables * Kernel: support for fragmented memory mapped BATs * Mapi: an other round of performance improvements This one didn't make it, so it's also not in. * 64 bit Windows installer. * Kernel: cleanup (removal of uchr, new types byte and word). Are they in? Stefan?
Items planned for later and upon need
* SQL: support for the XMLtype * SQL: Stored procedures. I'd like to add here SQL: VACUUM TABLE and CLUSTER TABLE support * A basic GIS module. * Improve bulk-loading stream-based processing * DatabasePool, to manage multiple Mserver instances * Re-organize and redo performance benchmarks * Migration tools from Oracle, MS SQL Server, MySQL, and PostgreSQL
Alpha release of the MonetDB V5 05-05-2006 ok.
Wat zijn de verbeteringen aan de API kant? PHP has been renovated completely, but doesn't work on Windows yet? JDBC issues? Authorization issues? Oftewel, wat is er wel te 'verkopen'? Fabian Groffen wrote:
On 05-06-2006 14:03:51 +0200, Martin Kersten wrote:
From our website: -------------------------------------------------------------------- Items planned for release V4.12 25-06-2006 This release is geared at consolidation of the XQuery functionality.
* XQuery: XUpdate and API's * XQuery: support for large numbers of small documents * XQuery: standoff, extension to the XPath axis * Kernel: caching small garbaged BATs for speed * APIs: Xrpc (remote procedure using soap) * SQL: support for triggers This is not in there, I think, and I also guess won't be in. * SQL: full support for global and local temporary tables * Kernel: support for fragmented memory mapped BATs * Mapi: an other round of performance improvements This one didn't make it, so it's also not in. * 64 bit Windows installer. * Kernel: cleanup (removal of uchr, new types byte and word). Are they in? Stefan?
Items planned for later and upon need
* SQL: support for the XMLtype * SQL: Stored procedures. I'd like to add here SQL: VACUUM TABLE and CLUSTER TABLE support * A basic GIS module. * Improve bulk-loading stream-based processing * DatabasePool, to manage multiple Mserver instances * Re-organize and redo performance benchmarks * Migration tools from Oracle, MS SQL Server, MySQL, and PostgreSQL
Alpha release of the MonetDB V5 05-05-2006 ok.
_______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
On 06-06-2006 07:28:22 +0200, Martin Kersten wrote:
Wat zijn de verbeteringen aan de API kant? {improvements on the API side}
I don't know about API changes in SQL. I think the XQuery people have. The only thing that comes close IMO is the change to have every language (mil, sql, xquery) work on the same port on the server: 50000.
PHP has been renovated completely, but doesn't work on Windows yet? JDBC issues? Authorization issues?
- PHP: new and improved, now without crashes! (PostgreSQL compatible) - JDBC: no changes (that I know of) - Authorisation: would like my patches to get into the M5 release, but I cannot figure out how to do some little things, hence upon restart of the server authorisation doesn't work any more.
Oftewel, wat is er wel te 'verkopen'? {IOW, what can we 'sell'}
Not much. Just bugfixes and improved stability for SQL. The focus is for the XQuery people to define their new features.
On Tue, Jun 06, 2006 at 09:13:30AM +0200, Fabian Groffen wrote:
On 06-06-2006 07:28:22 +0200, Martin Kersten wrote:
Wat zijn de verbeteringen aan de API kant? {improvements on the API side}
I don't know about API changes in SQL. I think the XQuery people have. The only thing that comes close IMO is the change to have every language (mil, sql, xquery) work on the same port on the server: 50000.
PHP has been renovated completely, but doesn't work on Windows yet? JDBC issues? Authorization issues?
- PHP: new and improved, now without crashes! (PostgreSQL compatible) - JDBC: no changes (that I know of) - Authorisation: would like my patches to get into the M5 release, but I cannot figure out how to do some little things, hence upon restart of the server authorisation doesn't work any more.
Oftewel, wat is er wel te 'verkopen'? {IOW, what can we 'sell'}
Not much. Just bugfixes and improved stability for SQL. The focus is for the XQuery people to define their new features.
SQL has initial support for triggers, have to fill in the details arround the release as it will get some more support soon. Full support for local/global temporaries (which was a lot of changes in the transaction layer, net effect should be faster transactions) Session variable support using @varname. Indeed this is besides bug fixes / stability (an important bug in primary key constraints was fixed) I'd like to assess the stability the comming weeks using dots and possibly some other test frameworks. Niels -- Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes@cwi.nl
About StandOff support: - I would like to know whether the multi-document-in-one-container-feature is going to be in the release. Without this feature its probably going to be less trouble to bugfix the axis steps (they are currently broken due to the new bat-representation of XML-documents). - also, with a minor checkin we have runtime-option (instead of compilerflag) support for the StandOff axis steps. Wouter p.s. there are currently still 50 open bugs for MonetDB... and I haven't even tried the update-branch yet ;) if you would ask me, it seems that a quick release is not possible. -----Original Message----- From: monetdb-developers-bounces@lists.sourceforge.net [mailto:monetdb-developers-bounces@lists.sourceforge.net] On Behalf Of Niels Nes Sent: dinsdag 6 juni 2006 9:21 To: monetdb-developers@lists.sourceforge.net Subject: Re: [Monetdb-developers] MonetDB release meeting On Tue, Jun 06, 2006 at 09:13:30AM +0200, Fabian Groffen wrote:
On 06-06-2006 07:28:22 +0200, Martin Kersten wrote:
Wat zijn de verbeteringen aan de API kant? {improvements on the API side}
I don't know about API changes in SQL. I think the XQuery people have. The only thing that comes close IMO is the change to have every language (mil, sql, xquery) work on the same port on the server: 50000.
PHP has been renovated completely, but doesn't work on Windows yet? JDBC issues? Authorization issues?
- PHP: new and improved, now without crashes! (PostgreSQL compatible) - JDBC: no changes (that I know of) - Authorisation: would like my patches to get into the M5 release, but I cannot figure out how to do some little things, hence upon restart of the server authorisation doesn't work any more.
Oftewel, wat is er wel te 'verkopen'? {IOW, what can we 'sell'}
Not much. Just bugfixes and improved stability for SQL. The focus is for the XQuery people to define their new features.
SQL has initial support for triggers, have to fill in the details arround the release as it will get some more support soon. Full support for local/global temporaries (which was a lot of changes in the transaction layer, net effect should be faster transactions) Session variable support using @varname. Indeed this is besides bug fixes / stability (an important bug in primary key constraints was fixed) I'd like to assess the stability the comming weeks using dots and possibly some other test frameworks. Niels -- Niels Nes, Centre for Mathematics and Computer Science (CWI) Kruislaan 413, 1098 SJ Amsterdam, The Netherlands room C0.02, phone ++31 20 592-4098, fax ++31 20 592-4312 url: http://www.cwi.nl/~niels e-mail: Niels.Nes@cwi.nl _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
On 06-06-2006 20:11:55 +0200, Wouter Alink wrote:
About StandOff support:
- I would like to know whether the multi-document-in-one-container-feature is going to be in the release. Without this feature its probably going to be less trouble to bugfix the axis steps (they are currently broken due to the new bat-representation of XML-documents).
- also, with a minor checkin we have runtime-option (instead of compilerflag) support for the StandOff axis steps.
From a packaging perspective, as well as general user-experience, I would prefer such flag. What is the burden that the runtime-conditional puts upon the system in comparison to a compile-time flag?
p.s. there are currently still 50 open bugs for MonetDB... and I haven't even tried the update-branch yet ;) if you would ask me, it seems that a quick release is not possible.
Positive thinking :) Without bugs, there is nothing to fix, and nothing to improve ;)
On Tue, Jun 06, 2006 at 08:40:09PM +0200, Fabian Groffen wrote:
On 06-06-2006 20:11:55 +0200, Wouter Alink wrote:
About StandOff support:
- I would like to know whether the multi-document-in-one-container-feature is going to be in the release. Without this feature its probably going to be less trouble to bugfix the axis steps (they are currently broken due to the new bat-representation of XML-documents).
I strongly hope that the multi-document-in-one-container-feature will be in the release. But now matter, whether it will or will not, the standoff "stuff" MUST work in either case to be part of the release. I highly recommend to add standoff tests to the "testweb" to (1) assess the current state of the standoff implementation/code and (2) monitor the impact of other code changes on the (functionality/correctness of) the standoff implementation/code --- just like Jennie has (once had ;-)) tests for XRPC...
- also, with a minor checkin we have runtime-option (instead of compilerflag) support for the StandOff axis steps.
From a packaging perspective, as well as general user-experience, I would prefer such flag. What is the burden that the runtime-conditional puts upon the system in comparison to a compile-time flag?
Yesy, we should (must?) go for the runtime-option and abandon the compiletime-switch!
p.s. there are currently still 50 open bugs for MonetDB... and I haven't even tried the update-branch yet ;) if you would ask me, it seems that a quick release is not possible.
there is no "update-branch" any more. all update code/development has been merged into the main development trunk in February 2006 ... !
Positive thinking :) Without bugs, there is nothing to fix, and nothing to improve ;)
Right. I'm not scarred by the 50 open bugs, but very concerned about the fact that there are less(!) red(!) X's in the testweb. This means that there are still quite some test scripts missing --- maybe we should also plan an other "BugDay" before the next release? Stefan -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |
participants (8)
-
Fabian Groffen -
Martin Kersten -
Niels Nes -
Peter Boncz -
Sjoerd Mullender -
Stefan Manegold -
Wouter Alink -
Ying Zhang