XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. 2.6.x Support 
  4.  / Idea : Norme for XOOPS tables
Register
1
alain01
Idea : Norme for XOOPS tables

  • 2012/7/12 9:10

  • alain01

  • Just can't stay away

  • Posts: 536

  • Since: 2003/6/20


Hello,

I have a request, may be for XOOPS 2.6 (or not)...

We've get in our XOOPS database many tables with different name, not friendly readable in PhpMyAdmin (melting Pot).

I suggest norme for XOOPS tables

modules tables :
Quote:
_mod_nomdumodule_table1dumodule
_mod_nomdumodule_table2dumodule
_mod_nomdumodule_table3dumodule

Example :
Quote:
_mod_publisher_categories
_mod_publisher_files
_mod_publisher_items
_mod_publisher_meta
_mod_publisher_mimetypes
_mod_publisher_rating

For the next plugins, we could get
Quote:
_pgin_avatar
_pgin_smiley

For system tables, we could get :
Quote:
_core_config
_core_configcategory
_core_configoption
_ core_groups
_core_groups_users_link
_core_group_permission
...

it will be more clear.

Sure, it's note a revolution, just more clear.
Actually, there are sytem tables then, modules tables, other system tables, then others modulestables...

See :
Quote:
_avatar
_avatar_user_link
_banner
_bannerclient
_bannerfinish
_block_module_link
_cache_model
_config
_configcategory
_configoption
_groups
_groups_users_link
_group_permission
_image
_imagebody
_imagecategory
_imgset
_imgsetimg
_imgset_tplset_link
_modules

_mysearch_searches

_newblocks
_online
_priv_msgs

_protector_access
_protector_log

_publisher_categories
_publisher_files
_publisher_items
_publisher_meta
_publisher_mimetypes
_publisher_rating

_ranks
_session
_smiles

_stories
_stories_files
_stories_votedata
_topics

_tplfile
_tplset
_tplsource
_users
_xoopscomments
_xoopsnotifications

Moreover, Is it possible to get clean table for the next "news module" version:
_topics => _stories_topics (Then, with norm, _mod_stories_topics)

Finally, in phpmyadmin, we could get this
Quote:
_core_table1
_core_table2
_core_table2

_mod_module1_table1
_mod_module1_table2
_mod_module1_table3

_mod_module2_table1
_mod_module2_table2
_mod_module2_table3

_pgin_plungin1_table1
_pgin_plungin1_table2

_pgin_plungin2_table1
_pgin_plungin2_table2
2
luciorota
Re: Idea : Norme for XOOPS tables

  • 2012/7/12 10:26

  • luciorota

  • Module Developer

  • Posts: 216

  • Since: 2007/4/20


+1
3
Mamba
Re: Idea : Norme for XOOPS tables

  • 2012/7/12 10:42

  • Mamba

  • Moderator

  • Posts: 11409

  • Since: 2004/4/23


I like it.

The challenge will be in converting existing tables.

For new modules, this should be a required standard.
Support XOOPS => DONATE
Use 2.5.11 | Docs | Modules | Bugs
4
irmtfan
Re: Idea : Norme for XOOPS tables

  • 2012/7/14 6:00

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


+1
But IMO these are just some "Cosmetics features".

XOOPS have more important "bugs" that should be solved and there are some very very important requested "features" that should be implemented in the next versions.
IMO Core team should set the priority for features based on their technical ideas.

a sidenote:
Mamba:
AFAIK You are a full democratic man and like to choose features based on the number of community requests (for example set a poll for each of them to find the priority. is there any?) but IMO it is up to current core developers to set the priorities.
Your way of choosing is very time consuming and finally Xoops will not reach to anywhere. Also all of us in the community is not equal because our websites is not equal in visits, features, revenue and ...

I repeat IMO core team should do what they intend to do. Just community can put pressure on them for a feature. eg: bombard the xoops.org forums for one needed feature and write the reasons and keep posting and ...

5
Mamba
Re: Idea : Norme for XOOPS tables

  • 2012/7/15 1:09

  • Mamba

  • Moderator

  • Posts: 11409

  • Since: 2004/4/23


Quote:
Moreover, Is it possible to get clean table for the next "news module" version:
_topics => _stories_topics (Then, with norm, _mod_stories_topics)

I've done it on my local installation. It seems to work OK, so once I'm done with some more testing, I'll release it as a new version 1.68 Beta for your testing.
Support XOOPS => DONATE
Use 2.5.11 | Docs | Modules | Bugs
6
Mamba
Re: Idea : Norme for XOOPS tables

  • 2012/7/15 1:22

  • Mamba

  • Moderator

  • Posts: 11409

  • Since: 2004/4/23


Quote:
I repeat IMO core team should do what they intend to do. Just community can put pressure on them for a feature. eg: bombard the xoops.org forums for one needed feature and write the reasons and keep posting and ...

I think, it's better to cooperate and work together as a one "XOOPS Community" instead of bombarding each other with features request, and getting on each other nerves.

We have now Roadmap for XOOPS 2.6.0 and the community can discuss it and provide feedback in this thread. As Nicolas said, the Core team is open for suggestions, and if possible within given time and resources, they will try to accommodate them.

The most successful products are those that are "customer focused". There are too many products that while technically superior, have failed because they missed what the customers wanted (for example, see Betamax vs. VHS).

But that's only my view, so I would be curious what the rest of the community thinks about your comments...
Support XOOPS => DONATE
Use 2.5.11 | Docs | Modules | Bugs
7
irmtfan
Re: Idea : Norme for XOOPS tables

  • 2012/7/15 4:30

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


Mamba:
I mean core team (and not community) should set priorities for features because as you and ForMuss said there are limited times and resources for core team.
Also when i told everybody can bombard the xoops.org forums for a feature i mean they can show their support and feed back for a mentioned feature even when they dont have anything to add or could not wrote in English. (so they just can send a single word or two)
eg: I told somebody in our local community to support the "Thank you button" feature in xoops.org

when i said it is up to the core team technically it will be interpreted to the below action:
community can send features in sf.net and core team can go to the sourceforge feature tracker and set priorities.
This feature to rename the xoops tables in more comprehensive way is good one but I mean there are many features already submitted that have higher priority.

Also you just said this feature is not a simple renaming tables because then it will break the backward compatiblities.
8
Mamba
Re: Idea : Norme for XOOPS tables

  • 2012/8/8 22:51

  • Mamba

  • Moderator

  • Posts: 11409

  • Since: 2004/4/23


News 1.68 Beta with normalized table names and updated makepdf.php file for TCPDF is ready for testing.

Download: XOOPS SVN

Follow-up: please use this thread

Support XOOPS => DONATE
Use 2.5.11 | Docs | Modules | Bugs

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

227 user(s) are online (192 user(s) are browsing Support Forums)

Members: 0

Guests: 227

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits