[LDTP-Dev] Changing "doesrowexist" behavior

[Saravana Prabhu]

Hi,

Just to add some oil after seeing this discussion, I feel I would share
how we would have handled  such things in WRAFS. Have Both as Prem said
:) , but still in an effective way, with different function names
instead of a additional parameter(s). At this point in time we have both
the functions in hand(one checking for partial match and the other for
exact match), instead of further changing teh code to incorporate
additional parameter(s) we will have these two existing functions with
different names. Any comments!

Are we discussing about the function in the following link:
http://gnomebangalore.org/ldtp/index.php/Doesrowexist . I believe the
document there says it checks if the table is empty or not. Plz correct
me if i am wrong.

Thanks & Regards,
Saravana

>>> "Shaheed Shaik" <sshaik at novell.com> 10/06/05 3:36 PM >>>
Hi Prem,

May be we can take the optional part later if there is any requirement.
For time being
attaching a patch for exact match.

Thanks,
shaheed. 
 
>>> jpremkumar <jpremkumar at novell.com> 10/06/05 2:52 pm >>> 
Hi Shaheed,

I think you are right, the name of the API itself suggests that we
look
for an exact match. But why cant we make it perform both like getting
an
optional argument specifying whether the user is expecting a partial
match or a complete match for the given string. Will this make sense?
Any comments ?

Regards
Premkumar

On Thu, 2005- 10- 06 at 03:05 - 0600, Shaheed Shaik wrote:
> Hi,
> 
> Currently "doesrowexist" component function performs a partial match
on
> a particular row. I feel this behavior is not much useful. I would
like
> to change its behavior to perform exact match.
> 
> Any comments...
> 
> Thanks,
> Shaheed.
> 
> 
> Khasim Shaheed
> Novell Software Development (I) Ltd.
> Bangalore- 68.
> 
> _______________________________________________
> Ldtp- dev mailing list
> Ldtp- dev at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/ldtp- dev