Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is very weird, I've struggled with this issue myself many times, over the last 15 years and generally come up with structures that separate area codes, country codes and number into separate fields etc. But whilst reading your question another solution just popped into my head, it does require a separate field though so may not be appropriate for you.</p> <p>You could have a separate field called reverse_phone_number, have this automatically populated by the DB engine then when people search simply reverse the search string and use the indexed reverse field with just a % at the end of the like string, thereby allowing the use of the index.</p> <p>Dependant on your DB engine you may be able to create an index based on a user-defined function that does the reverse for you obviating the need for an additional field.</p> <p>In some countries, e.g. the UK, you may have an issue with leading zeros. A UK phone number is represented as (area code)(Phone Number) e.g. 01634 511098, when this is internationalised the leading zero of the area code is removed and the international dial code (+ or 00) and the country code (44) are added. This results in an international phone number of +441634511098. Any user searching for 0163451109 would not find the phone number if it was entered in internationalised format. You can overcome this issue by removing leading zeros from the search string.</p> <p><strong>EDIT</strong> Based on suggestions from Ollie Jones you should store the number as entered by the user and then strip leading zeros, punctuation and white space from the number before reversing and storing in the reversed field. Then simply use the same algorithm to strip the search string before reversing, find the record and then display the originally entered number back to the user.</p>
    singulars
    1. This table or related slice is empty.
    1. POStruggling with a MySQL database of phone numbers
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSteve Weet
    1. USSteve Weet
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POStruggling with a MySQL database of phone numbers
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSteve that reverse # field is genius.
      singulars
      1. PO
      1. USJNK
    2. COTo make sure I get what you mean, you'd have a second table storing all their queries, with a bridge table matching the phone numbers it brought up? Automatically populated for every new query, so if somebody enters an existing search, it would just look at the old results? Nifty idea.
      singulars
      1. PO
      1. USTarka
    3. COdoh! you beat me to it by a few seconds. I think the reverse_phone_number field is a very good solution, as long as we can assume that the user will always know the last digits of the phone number they are searching for.
      singulars
      1. PO
      1. USPeter Recore
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload