[FIX] base_name_search_improved: interactive search
Translate Spanish texts to Englishpull/2477/head
Rad0van
filoquin
parent
adaf70ed5e
commit
a2de47b8c5
|
|
@ -58,13 +58,11 @@ def _get_name_search_domain(self):
|
|||
def _extend_name_results(self, domain, results, limit, name_get_uid):
|
||||
result_count = len(results)
|
||||
if result_count < limit:
|
||||
domain += [("id", "not in", [x[0] for x in results])]
|
||||
domain += [("id", "not in", results)]
|
||||
rec_ids = self._search(
|
||||
domain, limit=limit - result_count, access_rights_uid=name_get_uid
|
||||
)
|
||||
results.extend(
|
||||
models.lazy_name_get(self.browse(rec_ids).with_user(name_get_uid))
|
||||
)
|
||||
results.extend(rec_ids)
|
||||
return results
|
||||
|
||||
|
||||
|
|
@ -169,13 +167,13 @@ class Base(models.AbstractModel):
|
|||
@api.model
|
||||
def _search_smart_search(self, operator, value):
|
||||
"""
|
||||
Por ahora este método no llama a
|
||||
self._name_search(name, operator=operator) ya que este no es tan
|
||||
performante si se llama a ilimitados registros que es lo que el
|
||||
name search debe devolver. Por eso se reimplementa acá nuevamente.
|
||||
Además name_search tiene una lógica por la cual trata de devolver
|
||||
primero los que mejor coinciden, en este caso eso no es necesario
|
||||
Igualmente seguro se puede mejorar y unificar bastante código
|
||||
For now this method does not call
|
||||
self._name_search(name, operator=operator) since it is not as
|
||||
performant if unlimited records are called which is what name
|
||||
search should return. That is why it is reimplemented here
|
||||
again. In addition, name_search has a logic which first tries
|
||||
to return best match, which in this case is not necessary.
|
||||
Surely, it can be improved and a lot of code can be unified.
|
||||
"""
|
||||
name = value
|
||||
if name and operator in ALLOWED_OPS:
|
||||
|
|
@ -195,7 +193,7 @@ class Base(models.AbstractModel):
|
|||
class IrModel(models.Model):
|
||||
_inherit = "ir.model"
|
||||
|
||||
add_smart_search = fields.Boolean(help="Add Smart Search on search views",)
|
||||
add_smart_search = fields.Boolean(help="Add Smart Search on search views")
|
||||
use_smart_name_search = fields.Boolean(
|
||||
string="Smart Name Search Enabled?",
|
||||
help="Use Smart Search for 'name_search', this will affect when "
|
||||
|
|
@ -211,22 +209,19 @@ class IrModel(models.Model):
|
|||
for rec in self:
|
||||
if len(rec.name_search_ids) > 4:
|
||||
msgs.append(
|
||||
"Ha seleccionado más de 4 campos para smart search, "
|
||||
"recomendamos que intente utilizar menos "
|
||||
"campos"
|
||||
"You have selected more than 4 fields for smart search, "
|
||||
"fewerer fields is recommended"
|
||||
)
|
||||
if any(x.translate for x in rec.name_search_ids):
|
||||
msgs.append(
|
||||
"Ha seleccionado campos traducibles en la búsqueda "
|
||||
"inteligente, de ser posible intente "
|
||||
"evitar los mismos"
|
||||
"You have selected translatable fields in the smart search,"
|
||||
" try to avoid them if possible"
|
||||
)
|
||||
# rec.smart_search_warning = msg
|
||||
if msgs:
|
||||
rec.smart_search_warning = (
|
||||
"<p>Si tiene problemas de performance en las búsquedas le "
|
||||
"recomendamos revisar estas "
|
||||
"sugerencias: <ul>%s</ul></p>"
|
||||
"<p>In case of performance issues we recommend to review "
|
||||
"these suggestions: <ul>%s</ul></p>"
|
||||
) % "".join(["<li>%s</li>" % x for x in msgs])
|
||||
else:
|
||||
rec.smart_search_warning = False
|
||||
|
|
|
|||
|
|
@ -1,2 +1,3 @@
|
|||
* Daniel Reis <https://github.com/dreispt>
|
||||
* Kitti U. <kittiu@ecosoft.co.th> (migrate to v14)
|
||||
* Radovan Skolnik <radovan@skolnik.info>
|
||||
|
|
|
|||
|
|
@ -15,24 +15,28 @@
|
|||
</h1>
|
||||
</div>
|
||||
<p class="alert alert-info" role="alert" style="margin-bottom:0px;">
|
||||
Smart Search se puede activar de dos formas que pueden ser complementarias:
|
||||
Smart Search can be activated in two complementary ways:
|
||||
<ul>
|
||||
<li><b
|
||||
>Vista de búsqueda</b>: a la hora de buscar en vistas listas, kanban y demás, la primer opción será buscar mediante "Smart Search"
|
||||
<li>
|
||||
<b
|
||||
>Smart Search</b>: when searching in list, kanban and other views, the first option will be to search using "Smart Search"
|
||||
</li>
|
||||
<li><b
|
||||
>Name Search</b>: es para cuando estemos queriendo buscar un registro desde otro registro a través de los widgets m2o/m2m, por ejemplo al agregar un producto en una línea de venta o al elegir un contacto en una factura.
|
||||
<li>
|
||||
<b
|
||||
>Smart Name Search</b>: when searching for a record from another record through the m2o/m2m widgets, for example when adding a Product in a Sales Order Line or when selecting a Contact in an Invoice.
|
||||
</li>
|
||||
</ul>
|
||||
En donde se haya activado "Smart Search" las búsquedas tendrán un comportmiento más "relajado". Nativamente Odoo busca por registors que incluyan las palabras ingresadas tal cual las ha ingresado, al activar esta opción se buscará por registros que contegan dichas palabras y sin importar el orden en el que se ingresen. Por ej. si buscamos un Contacto con "Pedro Picapiedra", naticamente Odoo solo nos retornaría aquellos registros que contengan exactamente ese texto, con smart search activo se devolverá cualquier registro que contenga las palabras "Pedro" y "Picapiedra".<br
|
||||
/><br />
|
||||
If "Smart Search" has been activated, searches will have a more "relaxed" behaviour. Odoo natively searches for records that include the phrases entered as they are entered. When activating this option it will search for records that contain entered words regardless of the order in which they are entered. For example if we search for a Contact "Fred Flinstone", Odoo would by default only return those records that contain exactly that phrase. With Smart Search active any record containing the words "Fred" and "Flinstone" will be returned.
|
||||
<br />
|
||||
<br />
|
||||
|
||||
Al activar Smart Search podrá además agregar configurar estos dos comportamientos opcionales:
|
||||
By enabling Smart Search you can also add configure these two optional behaviours:
|
||||
<ul>
|
||||
<li>Definir un <b
|
||||
>dominio personalizado</b> (por ejemplo solo mostrar usuarios internos y no los portal)</li>
|
||||
<li><b
|
||||
>Búsquedas por otros campos</b>. Podremos definir un conjunto de campos por el cual querramos buscar</li>
|
||||
<li>Define a <b
|
||||
>Smart Search Domain</b> (for example, only show internal users and not portal users)</li>
|
||||
<li>
|
||||
<b
|
||||
>Smart Search Fields</b>. You can define a set of fields by which we want to search</li>
|
||||
</ul>
|
||||
</p>
|
||||
<p
|
||||
|
|
@ -41,7 +45,7 @@
|
|||
style="margin-bottom:0px;"
|
||||
>
|
||||
<b
|
||||
>IMPORTANTE:</b> tenga en cuenta que activar smart search puede afectar la performance de las búsquedas y del sistema en general.
|
||||
>IMPORTANT:</b> Please note that enabling smart search may affect the performance of searches and the system in general.
|
||||
<field name="smart_search_warning" />
|
||||
</p>
|
||||
<group>
|
||||
|
|
|
|||
Loading…
Reference in New Issue