Bruce Momjian wrote:
> >
> >
> > Morning all...
> >
> > Just curious, but what *is* planned for v6.4? We have a TODO
> > list, but I imagine there are things on that TODO list that ppl are
> > planning on for v6.4? Can we add a "planned for v6.4" to various items,
> > such that ppl have an idea of what they could be expecting? Even a
> > disclaimer at the top that states that altho "the following items are
> > planned for v6.4, time might not permit completion"?
> >
> > With that in mind, is anyone working on 'row level locking'? I
> > would think that, as far as importance is concerned, that would be one of
> > the most important features we are missing...
>
> We do have in the TODO list:
>
> A dash(-) marks changes to be in the next release.
>
> and appears to be fairly accurate. Haven't hear much about people
> claiming items for 6.4 yet.
>
Bruce,
Item "Remove restriction that ORDER BY field must be in SELECT list", in the
TODO list, has been completed.
Stephan or Anyone,
What is the status of the HAVING clause? I noticed that it almost made the
6.3.2 cut, but I haven't heard any thing for a while. I would really like to
see this feature implemented. It is important to my user community.
Everyone especially Vadim,
I agree with Marc. Row locking is huge. In my user community, it is
unacceptable to wait for up to 30 minutes (or even one minute) for a report to
finish so that a users can commit an invoice or commit a change to a customer
attribute. I can deal with it for now because my databases are batch loaded
for reporting purposes only. However, I plan to go forward with some pretty
important projects that assume that record/page locking will exist within the
next 12 month or so. Am I being too presumptuous?
