Timeline for How would you go about making a search algorithm for a CRM?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2016 at 0:01 | history | tweeted | twitter.com/StackSoftEng/status/795778324626866176 | ||
| Nov 3, 2016 at 18:04 | vote | accept | Captain Hypertext | ||
| Nov 1, 2016 at 22:42 | answer | added | Torisuda | timeline score: 1 | |
| Nov 1, 2016 at 9:10 | answer | added | devnull | timeline score: 3 | |
| Oct 31, 2016 at 18:42 | history | edited | Captain Hypertext | CC BY-SA 3.0 |
Added more clarity and detail
|
| Oct 31, 2016 at 18:26 | comment | added | Captain Hypertext |
@Dank Not to worry, we're actually using Laravel with prepared statements and all that. My point was that our global search pours through contacts, tasks, sales opportunities, and all that simply based on WHERE LIKE "Search String". There's really no rhyme or reason besides that for returning results.
|
|
| Oct 31, 2016 at 17:24 | comment | added | user190064 |
Be careful.. if your search is as simple as you describe, it looks vulnerable to SQL Injection. If an end user were to pass in a quote and semicolon they could possibly turn LIKE '%rick flair%' into LIKE %'; SELECT * FROM information_schema.tables; It can be a hassle trying to recreate the wheel... you might try looking at ORMs available for PHP.
|
|
| Oct 31, 2016 at 14:30 | answer | added | Vlad | timeline score: 0 | |
| Oct 31, 2016 at 14:10 | review | Close votes | |||
| Nov 7, 2016 at 3:01 | |||||
| Oct 31, 2016 at 13:52 | comment | added | user22815 | I think you could improve this question by scoping it a bit more narrowly, removing the resource requests, and explaining in more detail what the goals of your search algorithm are. | |
| Oct 31, 2016 at 13:40 | review | First posts | |||
| Nov 1, 2016 at 15:54 | |||||
| Oct 31, 2016 at 13:32 | history | asked | Captain Hypertext | CC BY-SA 3.0 |