Development Discussion Board

phpBB.com's database is around 8GiB (That includes the CDB and other pages ofcourse, but we are not using the database for search but are using sphinx instead). You should not forget that phpBB would require a huge amount of events. It is not just posting/editing/registring, but also all actions in...

Actually I don't think so much more data will be generated. Except maybe for the "views" (view counter of the topics): if it would be a problem to store these as events, you could give the option to keep them out of the ES and still store these as "state". Although, storing the &...

Ok that can be a point of discussion. It is then to find out/to have an idea how much more data is to be expected. And how much disk space will have impact on the price. i.e My current shared hosting package is in the lowest category, I pay 0,5 euro/month and it gives 1.5GB. Currently I have a 55 MB...

I think I follow in principle what this is about but the first thing that comes into my mind is that if you are storing all events that occur on a phpBB board in the database will this not result in a massive data storage problem, possibly beyond the resources for many boards? Or maybe I do not ful...

Hi, did anyone ever fantasize on using Event Sourcing and CQRS for phpBB in the unknown future? It seems a good idea to me. Instead of directly storing current state in the relational database it's storing all events or state changes sequantially in an append-only database. This can be done in almos...

However there's been some discussions about just going with Doctrine's ORM instead of continuing with our dbal so maybe this would get addressed at that point. Isn't it Doctrine DBAL instead of ORM? I hope it's not ORM! https://area51.phpbb.com/phpBB/viewtopic.php?f=108&t=44487&p=255735&...

3Di wrote: ↑Tue Apr 24, 2018 9:18 am https://github.com/phpbb/phpbb/pulls?q= ... teus%29%22

That's great!

Using shorthands/acronyms is the way to go. As it is now, no need to add rules/regulations here IMHO. mae_settings ---> MyAwesomeExtension_settings That's good for now, but it would be cleaner if you use the same prefix everywhere (instant recognisable) for anything related to your extension. It's ...

3Di wrote: ↑Tue Apr 24, 2018 5:24 am Let someone then open a ticket about it. So that someone else can take care of it. Yes I know, sounds like rounding in circles, but...

I've created a ticket.

How about keeping the 30 character limit for the core, but allowing 63 bytes for the extensions? That would imply that anyone using Oracle would not be installing extensions (may possibly be true, but cannot be guaranteed) Only Oracle pre 12.2 Only extensions that define column or table names longe...