![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello everyone! I have a slight problem matching rows. My problem is the Value in a textfield is: "87682<next>39857" I created that with concat. Is there a way to match one specific number out of that field? like WHERE SUPERFUNCTION(concated_field) = 87682 Is something like that possible in any way? Or does something like that function exists? Well in PHP you a function called in_array() which would work kind of similiar what i want to do. Any help is very appriciated ^_^ Many thanks for any replies Barry Ok found a solution: |
#3
| |||
| |||
|
|
Hello everyone! I have a slight problem matching rows. My problem is the Value in a textfield is: "87682<next>39857" I created that with concat. Is there a way to match one specific number out of that field? like WHERE SUPERFUNCTION(concated_field) = 87682 |
|
Is something like that possible in any way? Or does something like that function exists? Well in PHP you a function called in_array() which would work kind of similiar what i want to do. Any help is very appriciated ^_^ Many thanks for any replies Barry |
#4
| |||
| |||
|
|
Barry wrote: Hello everyone! I have a slight problem matching rows. My problem is the Value in a textfield is: "87682<next>39857" I created that with concat. Is there a way to match one specific number out of that field? like WHERE SUPERFUNCTION(concated_field) = 87682 WHERE concated_field LIKE '%87682%' It would also give me Fields that have 987682 or 876825. |

#5
| |||
| |||
|
|
try this: WHERE concated_field LIKE '87682%' or WHERE concated_field LIKE '87682<next>_____' would give me 876825 what i am not looking for. |

#6
| |||
| |||
|
|
WHERE concated_field LIKE '%87682%' |
|
2. This doesn't sound like a good DB-Design, why don't you use two seperated fields for both numbers, or a m:n table if there are more possible entries? |
#7
| |||
| |||
|
|
On 9 May 2006, at 14:27, Wolfram Kraus wrote: WHERE concated_field LIKE '%87682%' No, because that would also match numbers that contain that sequence like '187682<next>32876825'. 2. This doesn't sound like a good DB-Design, why don't you use two seperated fields for both numbers, or a m:n table if there are more possible entries? Definitely. |
#8
| |||
| |||
|
|
On 9 May 2006, at 14:27, Wolfram Kraus wrote: WHERE concated_field LIKE '%87682%' No, because that would also match numbers that contain that sequence like '187682<next>32876825'. |
|
Marcus |
![]() |
| Thread Tools | |
| Display Modes | |
| |