[OpenSER-Devel] FUNCTION ser.bitand does not exist

[Bogdan-Andrei Iancu]

Hi everybody,

 From my point of view, this is more a problem of module design, rather 
than a DB issues. The nathelper module (or any other module) should not 
rely too much on DB ops that may be specific to a certain DB type. Maye 
the best place for this logic should be in the module itself, but we end 
up in another problem. If complex ops are moved in the modules, it means 
the modules will need to fetch large amount of data from data from DB...:(

regards,
Bogdan

Dan Pascu wrote:
> On Tuesday 13 May 2008, Iouri Kharon wrote:
>   
>>    Hi Dan!
>>
>> Tuesday, May 13, 2008, you wrote:
>>
>> DP> My idea was that each db module can offer functions like:
>>
>> DP> inline str bitand(int a, int b)
>> DP> {
>> DP> }
>>
>> Yes, of cause. But for this (and analogoue) function need  _big_
>> chnages (expand) for db-api. When i propose this, answer was - "after
>> 1.4 complete" :)
>>     
>
> I didn't say we should do this before 1.4. I just said I think this is a 
> better approach than to use user defined procedures to cover for database 
> differences. At least it doesn't affect performance for any of them as 
> the current approach does.
>
>