Hieu Do

OMG, thanks so much Soma, much appreciated. I'll try your module when I get home. I just think why don't we make a fieldtype with arbitrary amount of text fields inside, each text field is a column in a table? I know the Repeater field is capable for this but it actually contains a link to other fields, thus it has to use JOIN query which I don't desire. I just want to get all info at once by issuing one SELECT query.

Hello, I need to save product's dimensions (example: a phone has dimensions 5.38" x 2.75" x 0.31") but don't want to use 3 float-number fields. Instead, I want to use a field type that can display 3 input boxes on edit-page screen then store entered values into a single table in database. I don't want to separate them into 3 tables because they're simply unnecessary. Is it possible to create this kind of field? Thank you!

Wow, thanks for your advices, they help me a lot and give me more confidence to keep using PW. I just forgot about indexing and caching, they're wide matter but really helpful in scalability indeed. I heard someone said that MySQL would run efficiently with optimized single queries rather than complex queries. About the searching in PW, I think there are a lot of dedicated full text search servers like Sphinx, Solr, Lucence, Xapian that are feature-rich and more powerful than MySQL native search functionality. I used to use Sphinx to replace Wordpress built-in search and it worked perfectly, very fast and very less memory consumption. I can say it's a must for every database-driven website. A little question, is there any module/plugin support integrating one of those search engines in PW yet??

Hi everyone, I'm a PW newbie, I just switched from Wordpress to PW a few days ago. After installing and playing around with PW, I do have a concern about PW's database structure. I'm afraid it may not scale easily with several millions of records since it has too many tables. I'm not either a DBA or database expert but I hate joining in relational DB. It is really a pain that slows down most of my WP sites because continuous joining consumes much CPU/RAM. You know, WP has a table wp_postmeta contains metadata of posts (it's really big, at least 10x bigger than wp_posts if you have 10 fields associated with a post) and everytime I want to gather all fields of a book (assuming my site is a book library) WP has to issue a very long query, it also makes mysqld always in top of heavy processes in my VPS. I can see PW uses separate table for each field. I don't understand the intention of this approach. Could anyone help me catch the idea behind this? Is there anything impact the performance? I just thought that most information of a book is one-to-one relationship, why we need to separate them then have to join them again? Thanks

Thanks so much Ryan, I'm just getting started with PW and am totally new here. Being a Wordpress developer for at least 5 years, now I realize that I've been stucked too long in its fixed structure. PW opens my eyes and gives me more innovation. This new site profile is awesome and totally convince me to stay with PW. Again, thanks so much Ryan. You're a super man.