age icon indicating copy to clipboard operation
age copied to clipboard

Write the extension to use those hooks

Open eyab opened this issue 3 years ago • 16 comments

eyab avatar Jan 05 '23 15:01 eyab

Fahad Zaheer

FahadZaheerfzr avatar Jan 10 '23 07:01 FahadZaheerfzr

hey I'm Urooj Fatima. Excited for this project

fatimafatimaprogrammer avatar Jan 10 '23 07:01 fatimafatimaprogrammer

Hello, Its Syed Umer Tariq !!

umer200 avatar Jan 10 '23 17:01 umer200

Hi, I am the new Operations Manager Steve from Vancouver Team.

Steves452 avatar Jan 10 '23 19:01 Steves452

Hi! It's Rafsun.

rafsun42 avatar Jan 30 '23 18:01 rafsun42

Hi! I'm Abdul Manan. I'm excited to work on this project!

abdulmanann avatar Feb 07 '23 03:02 abdulmanann

Hi! I am Abdullah. Excited for this project !!

abduu11aahh avatar Feb 07 '23 03:02 abduu11aahh

Hi! I am Waleed, excited to work on this project

waleedahmed0001 avatar Feb 07 '23 05:02 waleedahmed0001

Hi I am Talha and I am excited to start working on this project

talhahahae avatar Feb 07 '23 15:02 talhahahae

Hi, Jawad Ali here Excited

JawadAliAbbasi avatar Feb 13 '23 18:02 JawadAliAbbasi

  1. First identify the hooks offered by the application. The hooks can be methods or functions.
  2. Write your own code that will be executed in these functions or methods. The code should be designed to modify the behavior of the application.
  3. Register your extension with the application so that it is notified when we call those methods.
  4. Provide documentation or examples of how your extension can be used to modify the behavior of the application.

talhahahae avatar Mar 04 '23 10:03 talhahahae

Here is a general overview of how an extension that uses hooks might work:

-Identify the point in the system where the extension needs to modify behavior. This could be an input or output point, an action, or a decision. -Determine if a hook is available at that point. If so, review the documentation to understand how to use the hook and what input/output parameters are required. -Write the extension code to use the hook. This could involve writing a new function or modifying an existing one to incorporate the hook. -Test the extension to ensure that it works as expected. This could involve testing with various input/output scenarios or testing the extension with the system in different configurations. -Provide documentation for the extension so that other developers know how to use it. -Share the extension with others who may benefit from it. This could involve publishing it to a repository or marketplace or sharing it directly with other developers.

abduu11aahh avatar Mar 19 '23 02:03 abduu11aahh

We will begin by identifying the available hooks in the MariaDB application, which can be in the form of functions or methods. Next, we will write our own code that will be executed within these hooks to modify the behavior of the application as desired. After writing the code, we will need to register our extension with the application to ensure that it is notified when the relevant methods or functions are called.

abdulmanann avatar Mar 19 '23 15:03 abdulmanann

In order to get started with the extension for using the hooks we need to look for points where there is need of hooks and after identifying those points we will create hooks which will be user-defined functions to perform required actions at those points. Lastly, we need to verify the results of our hooks whether it's producing the desired results after which we need to integrate those hooks in our extension after which there will be a need for documentation of all the functionalities in the extension and ultimately the extension will be made public by publishing it to some repository and share with extension marketplace.

umer200 avatar Mar 19 '23 15:03 umer200

To write an extension to use hooks in MariaDB, you will need to have a good understanding of the MariaDB architecture and how the various hooks work.

So, I am sharing a link with you from which you can learn MariaDB architecture. Architecture Readme

waleedahmed0001 avatar Mar 25 '23 18:03 waleedahmed0001

This issue is stale because it has been open 45 days with no activity. Remove "Abondoned" label or comment or this will be closed in 7 days.

github-actions[bot] avatar May 12 '24 00:05 github-actions[bot]