search

propelorm / Propel3

High performance data-mapper ORM with optional active-record traits for RAD and modern PHP 7.2+
MIT License
252 stars 35 forks source link

Table prefix and packages #87

Closed cristianoc72 closed 5 years ago

cristianoc72 commented 5 years ago

Now that the new object model is almost ready, it's time to decide the fate of package and table prefix options. Should we continue to support them or they can be removed? @gossi @marcj

gossi commented 5 years ago

If I recall the last discussion, we are at the point to drop them. That is, table prefixes were a thing back in the day, when hosters only offered you one database and you want to probably install the same app twice and more databases were expensive. Nowadays deployment of apps changed drastically. It's like spinning up databases on demand =) Drop them, they just cause confusion and recall a thing from the past.

gossi commented 5 years ago

I think packages only confused me ;) I also think they predated php 5.3 (namespaces) where packages were used by phpdoc to structure code into folders for documentation purpose? I don't know if I'm correct here, if so drop them, too.

marcj commented 5 years ago

I'd drop both

cristianoc72 commented 5 years ago

Agree. I'm going to drop both.

Il giorno sab 26 gen 2019, 00:32 Marc J. Schmidt notifications@github.com ha scritto:

I'd drop both

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/propelorm/Propel3/issues/87#issuecomment-457770843, or mute the thread https://github.com/notifications/unsubscribe-auth/AA00neq-AKRJWuoFOdf2LvwiVLRQv94Wks5vG5QTgaJpZM4aS88M .

cristianoc72 commented 5 years ago

closed via #83