Encontrar

Artículo
· 3 hr atrás Lectura de 1 min

Aprovechando Server Manager al crear extensiones de VS Code que se conectan a servidores de InterSystems

Fue alentador ver a más personas creando extensiones de VS Code para el concurso reciente. Sin embargo, noté que de las tres extensiones que requieren credenciales para realizar sus conexiones, solo la de @John Murraygj :: dataLoader, aprovecha la extensión InterSystems Server Manager, ampliamente establecida y oficialmente soportada, para obtener las definiciones de conexión y gestionar las credenciales de manera segura.

Podéis encontrar más detalles sobre cómo hacerlo en el README de la extensión.

Si tenéis problemas al usar esta funcionalidad, o una opinión sobre por qué las extensiones deberían crear su propia solución en este ámbito, discutámoslo aquí.

Comentarios (0)1
Inicie sesión o regístrese para continuar
Comentarios
· 4 hr atrás

A small challenge for you - enhancing Interoperability message trace for mixed JSON and XML content

Hello community!
I have a small challenge for you :)

One of customers is sending quite a lot of messages between interoperability components, which mix standard request content and streams representing serialized JSON objects. As these JSON streams can be quite long (but not too long, just couple hundreds of characters) they would appreciate if the JSON content of stream was displayed in a nice-to-read way, using syntax highlighting by message trace view.

This picture illustrates the challenge - we are talking about the text framed by a red rectangle:
 I'd love to hear from anyone that you were able to come with some solution and post it to open exchange portal!

Dan

1 nuevo comentario
Comentarios (1)2
Inicie sesión o regístrese para continuar
Artículo
· 4 hr atrás Lectura de 2 min

Indexes: The Silent Power Behind Fast Queries

The Power of Indexing in Database Tables

When working with databases, most developers understand the concept of an index and why it's used: to speed up data retrieval. But the real impact of indexing often becomes clear only when you compare scenarios with and without it.

Do you Know what Happens Without an Index?
Imagine a table with three columns: Name, Age, and MobileNumber.


Now, consider this query:

If the Age column does not have an index, the database engine will:

  • Check if the WHERE condition field has an index.
  • If not, it will scan the entire table (a full table scan).
  • For each row, it will check the Age value and return matches.

This means the engine traverses the entire data structure, which is time-consuming for large tables.

What Happens With an Index?
Now, if the Age column is indexed, the process changes dramatically:

  • The engine goes directly to the index structure.
  • It finds the node for Age = 26.
  • The index points to the corresponding record IDs in the main table.
  • The result is fetched almost instantly.

This is why indexing is such a powerful optimization tool.

A Real-Life Lesson
Recently, we encountered an interesting situation that highlighted the importance of indexes.
Our table had 5 records, and the Age column was indexed. Then, by mistake, we deleted two entries from the index structure (not from the main table). These entries corresponded to IDs X001 and X005, both having Age = 26.


When we ran:
SELECT ID, Age, EmpId, Mobile, NameFROM Company.Employee WHERE Age = 26
We expected 3 records (since the main table still had them), but only 2 records appeared.

Why? Because the query relied on the index, and the index was incomplete.

Key Takeaway
Indexes are powerful, but they must be maintained properly. If an index is accidentally deleted or corrupted, don’t worry, you can rebuild the index using the below command:

Do ##Class(Company.Employee).%BuildIndices()

Moral of the story: Indexes make queries fast, but they also become a single point of truth for retrieval. Handle them carefully!😅

Comentarios (0)1
Inicie sesión o regístrese para continuar
Anuncio
· 5 hr atrás

2025 en retrospectiva: ¡celebrad vuestro año con la comunidad de desarrolladores!

Hola, comunidad:

✨ Mientras cerramos otro año increíble en la comunidad de desarrolladores, es el momento de echar la vista atrás y repasar todo lo que habéis conseguido en 2025. Vuestro resumen personal de 2025 ya está disponible: una visión a medida de vuestra actividad, vuestros logros y el valor que habéis aportado a la comunidad este año.

Desde los artículos que compartisteis hasta los debates que impulsasteis, vuestras contribuciones ayudaron a dar forma al conocimiento y a la colaboración en nuestra plataforma. Ahora podéis revisarlo todo en un solo lugar.

¿Qué incluye vuestro resumen de 2025? Una visión personalizada de vuestro año que incluye:

  • Vuestras publicaciones, comentarios y visualizaciones
  • Vuestra etiqueta favorita
  • Vuestra contribución más destacada
  • Y algunos momentos divertidos que hemos preparado solo para vosotros

Para abrir vuestro resumen, solo tenéis que ir a la página principal y hacer clic en «Ver mi resumen», o abrir vuestro perfil.

Una vez allí, encontraréis un resumen con un formato cuidado que podéis compartir fácilmente con compañeros, amigos o en vuestras redes sociales favoritas, mostrando el impacto que habéis tenido a lo largo del año. Para compartir vuestro resumen con otros, solo tenéis que hacer clic en Compartir en la esquina inferior derecha.

¡Nos encantaría saber a qué club pertenecéis! No dudéis en compartir en los comentarios qué momentos destacados os sorprendieron más.

Celebremos el conocimiento, la innovación y la colaboración que habéis aportado a la comunidad en 2025. ¡Por otro año increíble que está por venir!

Comentarios (0)1
Inicie sesión o regístrese para continuar
Artículo
· 5 hr atrás Lectura de 2 min

[Quick tip] How to create an AI agent using Intersystems documentation in Teams

Hi everyone.

I'm going to give you a quick tip on how to implement an AI agent to search the Intersystems documentation integrated into Teams.

Yes, I know the documentation page has its own AI search engine and it's quite effective, but this way we'd have faster access, especially if Teams is your company's corporate tool.

You can also create another AI agent to search articles published in the developer community (which also has its own integrated AI search engine).

Step 1

Select the "Copilot" option

Step 2

Select the option "Create agent".

If you don't initially see this option, press the button that appears in the upper left.

Step 3

Select the Configure option to avoid using existing templates.

Give your AI agent a name, for example, "Intersystems Docs," and a description. You can also customize the agent's icon.

In the "Instructions" section, add the following entries.

- The agent must search for information on the InterSystems website.
- Provide accurate and relevant answers based on the information found.
- Maintain a professional and clear tone in all interactions.
- Do not provide information that is unverified or not found on the InterSystems website.
- Guide the user to additional resources if necessary.

Add the URL to the Intersystems documentation

https://docs.intersystems.com

Note: If you want to create an agent that queries the developer community, use the following link:

https://community.intersystems.com

Or add both to make the search more complete.

Step 4

We can add prompt suggestions.

Title Message
Search for information Can you search for information about [topic] on the InterSystems website?
Resource guide Can you guide me to the resources available about [topic] on the InterSystems website?
Specific details I need specific details about [topic] from the InterSystems website.
Latest updates What are the latest updates about [topic] on the InterSystems website?

Press the "Create" button and that's it... we can now use our AI agent

We can look up anything using our new agent; we can do it in any language, because it already has its translation included.

I hope you find it as useful as I have.

Comentarios (0)1
Inicie sesión o regístrese para continuar