This is not the way our development cycle works.
We have a feeling, an idea, but the basic concept is that we do not target a specific R Release. We only target quality. I know, I’m repeating myself, but this is really the key concept.
We knew since two weeks what will be in R3. We knew because we closed all development and started to work on R4. We don’t know yet what will be in R4. Or to be more exact: we think to know two specific features will be in R4, as development is finished, all tests finished, so normally nothing should happen. But if we run into a major issue in the next weeks, we might delay those.
We have a couple more features close to be finished, we think they will make it as well. Here it is more fuzzy. And there are more features in the process, which have a good chance.
But finally, at the end, it is not the developer deciding what is in the release, it is just the result of quality assurance. They give the final go. Everything else will be delayed for the next one. And this is followed even if the big boss himself developed something really important…
And this is why we don’t name a release number if it is not directly the next one, where we already finished all testing and are sure it will be included.
But to answer your question: as you can see in the R3 docu, language classes are ready. As you could see in LR’s demo, database classes works in the database engine, “just” the user interface is not ready (you might have noticed he showed it in a text editor). When you follow our concept to release smaller, but well tested parts, you might guess that database classes will be released step by step, and LR mentioned that database class member functions will come first, with events and features like restricted queries coming in a later release(s)