Point taken Anthony.
Naturally you are not going to work for me for free.
But I’m a bit
confused about the statement that “I’m rude”. That’s
not my purpose to be. And I certainly do hope that this is not just a question
of a cultural clash between an elderly man with a Phd in black holes from a
European background and a young American FS genius.
But frankly, I did
believe that focus regarding changes and new developments was somewhat guided
by the input you get from the users list, including changes which makes the FS
easier to access for newbies, but maybe I’m wrong.
That’s my last
comment, hope we can continue the exchange of views in a good spirit.
Jon Brüel
Consiglia Telecommunications
DK-2960 Rungsted Kyst
Tel: +45 45 16 1000
Mob: +45 26 15 30 60
CVR: 27047882
From:
freeswitch-users-bounces@lists.freeswitch.org
[mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale
Sent: 8. december 2009 17:28
To:
Subject: Re: [Freeswitch-users]
Lua and database access to core_db
One last bit of free
consulting advice for you:
You are again being rude because you want us to work for you for free.
The code is free sir, the support here is voluntary and based on our
willingness to help and comments like that are all it takes to get us to ignore
you completely.
On Tue, Dec 8, 2009 at 5:46 AM, Jon Bruel <jbr@consiglia.dk> wrote:
I
got the combination Lua with direct access to the core Sqlite database to work.
Hurray, maybe I’m not as stupid as A.M II hints…
The
problem was that Lua did not “like”:
require "luasql.sqlite"
env = luasql.sqlite()
con = assert(env:connect("/usr/local/freeswitch/db/core.db"))
After
changing it to
require "luasql.sqlite3"
env = luasql.sqlite3()
con = assert(env:connect("/usr/local/freeswitch/db/core.db"))
And
seeing that there was a symlink in one of the right directories called with the
name: sqlite3.so, it worked.
Changing
the core db into a MySQL via ODBC caused some problems even after it seemed to
work. For instance, console help caused an error with an error description
indicating that a SQL SELECT query including the reserved word key has been
fired.
It
this problem likely to be solved if I used another version of the MySQL?
Jon Brüel
Consiglia Telecommunications
DK-2960
Rungsted Kyst
Tel: +45 45 16 1000
Mob: +45 26 15 30 60
CVR: 27047882
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
--
Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org
pstn:213-799-1400