Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 11 to 11 of 11 total |
sensitive query |
Thu, Oct 25 2018 11:10 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | 1
>OK, I was starting from my way of programming and therefore things seemed to me simple. This is why programmers should never produce their own documentation - after all they know what should happen - its obvious init >By example, I use idents strictly as hidden information that user never can change and is used only for locate records, and, I never use text information for identification of records. Generally speaking I use a integer generated by default as the primary key. It was an example only and nothing I would do normally. Even the best programmer have off days and things like this happen. Lots of companies out there use text customer "numbers" eg my heating oil supplier knows me as LAM0256, and I a few systems that will allow that to be altered at will. >There are many programming techniques you mentioned and in some cases there could be dangerous situations in implementation of my proposal. I accept your explanation and thank you for it. You're welcome. Roy |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |