Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #6233
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: implode/explode vs serialize/unserialize |
| Date | 2012-05-30 17:37 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <jq63uh$ffd$1@dont-email.me> (permalink) |
| References | <jq2im6$u4p$1@speranza.aioe.org> <4fc4dae4$0$6908$e4fe514c@news2.news.xs4all.nl> <jq576g$phf$1@speranza.aioe.org> <jq5jhu$1k6$1@dont-email.me> <jq60a8$ot8$1@dont-email.me> |
On 5/30/2012 4:35 PM, Scott Johnson wrote: > On 5/30/2012 9:57 AM, Jerry Stuckle wrote: <snip> >> Which would violate rdb normalization rules... >> > > Yes I tried that before while experimenting. > > I got lazy and just create a 'user_data' field to store some form data > without creating an actual field for each one. > > Well it worked just fine and danady until I needed to do a search for a > particular value. > > I then had to pull ALL the data, deserialize and search that data. > > What a nightmare. But I did learn some new algorithms in the process. > > I suppose sometimes it is our failures that teach us the best. > > :) > Scotty Scotty, Yup, there are reasons for those rules, and good reasons to follow them! :) That doesn't mean you should always follow every normalization rule every time; there are good reasons why you might not (i.e. performance). But when you do violate the rules, you should have a good reason and be aware of the possible consequences. After all, having to later change the database and rewrite the programs can be a long, involved process! -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ==================
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
implode/explode vs serialize/unserialize bill <william@TechServSys.com> - 2012-05-29 09:24 -0400
Re: implode/explode vs serialize/unserialize Jerry Stuckle <jstucklex@attglobal.net> - 2012-05-29 09:53 -0400
Re: implode/explode vs serialize/unserialize Erwin Moller <erwinmollerusenet@xs4all.nl> - 2012-05-29 16:19 +0200
Re: implode/explode vs serialize/unserialize Erwin Moller <erwinmollerusenet@xs4all.nl> - 2012-05-29 16:22 +0200
Re: implode/explode vs serialize/unserialize bill <william@TechServSys.com> - 2012-05-30 09:26 -0400
Re: implode/explode vs serialize/unserialize Jerry Stuckle <jstucklex@attglobal.net> - 2012-05-30 12:57 -0400
Re: implode/explode vs serialize/unserialize Scott Johnson <noonehome@chalupasworld.com> - 2012-05-30 13:35 -0700
Re: implode/explode vs serialize/unserialize Jerry Stuckle <jstucklex@attglobal.net> - 2012-05-30 17:37 -0400
Re: implode/explode vs serialize/unserialize Scott Johnson <noonehome@chalupasworld.com> - 2012-05-31 16:45 -0700
Re: implode/explode vs serialize/unserialize Erwin Moller <erwinmollerusenet@xs4all.nl> - 2012-05-30 20:37 +0200
Re: implode/explode vs serialize/unserialize Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-05-30 22:34 +0200
Re: implode/explode vs serialize/unserialize Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2012-05-29 16:07 +0200
csiph-web