Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internal function to send SMS from select, trigger or procedure [CORE2145] #2576

Closed
firebird-automations opened this issue Oct 25, 2008 · 8 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Valdir Marcos (valdir_marcos)

This internal function would be very important in those cases where database managers or company directors need to be informed as soon as possible.
It also could be used for normal things like "product is now available on stock".
As an internal function it could be used to send SMS from select, trigger or procedure.

To send SMS, this internal function could be similar to:
SendSMS(
Numer_To_Get_Line, -- 0 or Null
National_or_International_Call, -- 00 or 0 or Null
Country Number, -- 55 or Null
Area_Number, -- 11 or Null
Number_Phone, -- 1234-1234 or 1234-ABCD (some companies like this letter aproach)
Message_Text)

And the return could be VarChar "Sent" or "Error message..."

Thanks,

Valdir

@firebird-automations
Copy link
Collaborator Author

Modified by: Valdir Marcos (valdir_marcos)

summary: Internal function to send email / SMS from select, trigger or procedure => Internal function to send SMS from select, trigger or procedure

@firebird-automations
Copy link
Collaborator Author

Commented by: @cincuranet

How the server will communicate with GSM module? Do we really to add SMS PDU logic into server? How hard is to do it via events?

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

You may write your own UDF

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

The functionality that Valdir is requesting is already part of some other database servers (MS SQL for one) but is implemented via a "server manager" function which is responsible for actually delivering the messages. It is this same "server manager" which would provide/enable the scheduled tasks / procedures functionality.

So, the request is not invalid but would require Firebird to develop a new set of management functions and change the nature of a Firebird environment, which for some installs requires a "richer" installs.

@firebird-automations
Copy link
Collaborator Author

Commented by: @cincuranet

I know, that MS SQL has similar functionality. But this is easily solvable via events.

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

This is a task for UDR/UDF or external application listening to events.

@firebird-automations
Copy link
Collaborator Author

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant