Gossamer Forum
Home : Products : Gossamer Mail : Discussion :

[BUG 2.0.2] search problems and suggestion

Quote Reply
[BUG 2.0.2] search problems and suggestion
Hello!

The following does not give any correct result. This is an URL that results after Admin search.

http://www...../admin/admin.cgi?db=users&db=dgraph&do=search_results&email_users.userid=
&email_users.userid-opt==
&email_users.user=&domain=Troubles.Com
&email_users.user-opt=LIKE
&email_users.password=
&email_users.password-opt=LIKE
&email_users.users_status=Validated
&email_users.users_last_login=Mon+Jul+01
&email_users.users_last_login-opt=>
&email_users.users_space_used=
&email_users.users_space_used-opt=LIKE
&email_users.users_space_allowed=
&email_users.users_space_allowed-opt=LIKE
&email_users.users_max_pop=
&email_users.users_max_pop-opt=LIKE
&email_users.users_pass_phrase=
&email_users.users_pass_phrase-opt=LIKE
&email_users.users_pass_answer=
&email_users.users_pass_answer-opt=LIKE
&email_users.users_join_time=
&email_users.users_join_time-opt=LIKE
&email_users.users_default_template=
&email_users.users_default_template-opt=LIKE
&email_dgraph.dgraph_email=
&email_dgraph.dgraph_email-opt=LIKE
&email_dgraph.dgraph_first_name=
&email_dgraph.dgraph_first_name-opt=LIKE
&email_dgraph.dgraph_last_name=
&email_dgraph.dgraph_last_name-opt=LIKE
&email_dgraph.dgraph_address=
&email_dgraph.dgraph_address-opt=LIKE
&email_dgraph.dgraph_city=
&email_dgraph.dgraph_city-opt=LIKE
&email_dgraph.dgraph_state=
&email_dgraph.dgraph_state-opt=LIKE
&email_dgraph.dgraph_zip=
&email_dgraph.dgraph_zip-opt=LIKE
&email_dgraph.dgraph_country=
&email_dgraph.dgraph_country-opt=LIKE&mh=25&ma=on
&keyword=&query=&sb=&so=

What I wonder is an idea as following apart from the above problem and I write here as it occured to me while composing:

Is it not possible to develop a general table in the database called TEMP or CACHE for the purpose of inserting such long URL in the table and the user sees only the ID of the table? For e.g. the entire above URL would be inserted in the TEMP table with respect to their session ID and then shooted to the users webpage. The next time the user wanna go further, the further surfing continues with the Temp_ID in their table "CACHE".

The advantage of this system is that every user shall never ever come to know any of the correct link of any URL in the database like that of above!!! This will also supress the entire programming sub_routine names as above one could easily understand. Such a temp_ID could be allso generalised for all the GT products!!!

Subject Author Views Date
Thread [BUG 2.0.2] search problems and suggestion dearnet 1435 Jul 17, 2001, 12:10 AM
Post Re: [BUG 2.0.2] search problems and suggestion
dearnet 1359 Sep 8, 2001, 1:10 AM
Post Re: [BUG 2.0.2] search problems and suggestion
Alex 1342 Sep 10, 2001, 12:13 PM