Re: [Asterisk-Users] Realtime sipbuddies table structure why?????
At 01:21 PM 12/23/04, you wrote: Greg - Cirelle Enterprises wrote: Read it, makes no difference, it's broken :) Also, it doesn't say why the table structure is the way it is. just poor data modeling. God, I'm sure everyone on the list must be thinking, "Oh, why oh why didn't *Greg* write Asterisk instead of Mark; he seems so very much smarter. . . " B. Don't claim to be smarter, just pointing out the obvious greg ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Realtime sipbuddies table structure why?????
Greg - Cirelle Enterprises wrote: Read it, makes no difference, it's broken :) Also, it doesn't say why the table structure is the way it is. just poor data modeling. God, I'm sure everyone on the list must be thinking, "Oh, why oh why didn't *Greg* write Asterisk instead of Mark; he seems so very much smarter. . . " B. ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Realtime sipbuddies table structure why?????
I also have additional columns in my MySQL sip_buddies table with no problems. If there is a problem updating, selecting, or inserting into your table then you should check your MySQL Configuration or verifiy that it is working properly. On Thursday 23 December 2004 05:10 pm, Matthew Boehm wrote: > > Dec 23 09:24:57 NOTICE[12406]: chan_sip.c:7742 handle_request: > > Registration from '' failed for '192.168.70.26' > > > > happens with app_realtime, doesn't happen without realtime > > > > there are previous posts identifying issues with this. > > All I can say on this is that I am using todays CVS and I've got no > problems with phones registering using RealTime. > > > for example, host, secret, context, ipaddr, port, regseconds > > should not be column names, they should be data points with an > > associated column to contain the related value(s) > > Why? How is that an optimization when the data is specific to each row? > Out of personal curiosity can you give me a sample schema? > > > From what I can see, i can't add a column say musicclass = something, > > or pedantic = yes like I could in the conf file and have it mean > > anything. > > Yes you can. If you wanted to add the following in the flat file: > > [sipname] > mycustomkeya = valuea > mycustomkeyb = valueb > > all you have to do is add 2 columns, mycustomkeya and mycustomkeyb. I've > added 4 custom columns to my sip table. No problems. Granted they have > nothing to do with SIP itself.. > > -Matthew > > ___ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users -- Brian Wilkins Software Engineer [EMAIL PROTECTED] Heritage Communications Corporation Melbourne, FL USA 32935 321.308.4000 x33 http://www.hcc.net ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Realtime sipbuddies table structure why?????
> Dec 23 09:24:57 NOTICE[12406]: chan_sip.c:7742 handle_request: > Registration from '' failed for '192.168.70.26' > > happens with app_realtime, doesn't happen without realtime > > there are previous posts identifying issues with this. All I can say on this is that I am using todays CVS and I've got no problems with phones registering using RealTime. > for example, host, secret, context, ipaddr, port, regseconds > should not be column names, they should be data points with an > associated column to contain the related value(s) Why? How is that an optimization when the data is specific to each row? Out of personal curiosity can you give me a sample schema? > From what I can see, i can't add a column say musicclass = something, > or pedantic = yes like I could in the conf file and have it mean anything. Yes you can. If you wanted to add the following in the flat file: [sipname] mycustomkeya = valuea mycustomkeyb = valueb all you have to do is add 2 columns, mycustomkeya and mycustomkeyb. I've added 4 custom columns to my sip table. No problems. Granted they have nothing to do with SIP itself.. -Matthew ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Realtime sipbuddies table structure why?????
> So, providing a uniform access model that doesn't depend on file paths, > capitalization, or numbering is a bad thing? I'm just speaking from that "store-binary-data-in-database war" that went on on the -dev list. I personally have no experience in storing binary data in a database so I guess I shouldn't have said anything =/ > >>Read it, makes no difference, it's broken :) > > Whats broken? > > The table structure, did you miss it? I guess so. I don't understand/see how it is broken. It works great over here. > I don't claim to know everything about database structure, Same. Its my understanding that RealTime db schema was created for ease of use, ease of upgradability, and ease of understanding. Add ease of GUI too cause its alot faster/easier to delete 1 row than several in multiple tables. -Matthew ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Realtime sipbuddies table structure why?????
At 10:32 AM 12/23/04, you wrote: > just poor data modeling How so? How would you change it? Are you aware that they have written code into app_voicemail.c that allows you to store the actual soundfiles for voicemail in the database itself? You want to talk about poor database design...sheesh.. because it works, doesn't make it right > Read it, makes no difference, it's broken :) Whats broken? from tons of previous posts.. Dec 23 09:24:57 NOTICE[12406]: chan_sip.c:7742 handle_request: Registration from '' failed for '192.168.70.26' happens with app_realtime, doesn't happen without realtime there are previous posts identifying issues with this. > Also, it doesn't say why the table structure is the way it is. It most certainly does. Seems you didn't read the REAME after all. Quoted from README.extconfig: It is designed to provide a flexible, seamless integration between Asterisk's internal configuration structure and external SQL other other databases the columns in your tables should line up with the fields you would specify in the given entity declaration. For example, an entity that looks like: [foo] host=dynamic secret=bar context=default context=local could be stored in a table like this: +--++---+--+--+-+---+ | name | host | secret| context | ipaddr | port| regseconds| +--++---+--+--+-+---+ | foo | dynamic| bar | default;local| 127.0.0.1| 4569| 1096954152| +--++---+--+--+-+---+ Seems pretty simple and easy to use. This way if new config options are ever added, all you have to do to support them is to add a new column. And if all you are storing in most columns is 1 byte, it can't take up that much space. -Matthew I think you are still missing the point. for example, host, secret, context, ipaddr, port, regseconds should not be column names, they should be data points with an associated column to contain the related value(s) From what I can see, i can't add a column say musicclass = something, or pedantic = yes like I could in the conf file and have it mean anything. regards greg - Original Message - From: "Greg - Cirelle Enterprises" <[EMAIL PROTECTED]> To: "Asterisk Users Mailing List - Non-Commercial Discussion" Sent: Thursday, December 23, 2004 9:00 AM Subject: Re: [Asterisk-Users] Realtime sipbuddies table structure why? > At 09:53 AM 12/23/04, you wrote: > >It was written the way it is because that is how RealTime works. =P If you > >don't like the schema design, talk to Mark so he can rewrite RealTime for > >you. > > > >Read up some more on how RealTime works then you will understand why all the > >tables are designed the way they are. > > > >Read docs/README.extconfig > > > >-Matthew > > > Read it, makes no difference, it's broken :) > > Also, it doesn't say why the table structure is the > way it is. just poor data modeling. > > greg > > > ___ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users Regards Greg Cirino ___ Cirelle Enterprises Inc. 603-425-2221 www.cirelle.com Web Application Development & Design www.cirelle.net ProSpeed High Speed Dial-up - 6 Times Faster www.cedata.com Web, FTP, Email Hosting Services www.mlsbot.com NNEREN MLS IDX Services When You Want It Done Well, Just Call Cirelle It's not just a Rhyme... There's a Reason! ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Realtime sipbuddies table structure why?????
Matthew Boehm wrote: How so? How would you change it? Are you aware that they have written code into app_voicemail.c that allows you to store the actual soundfiles for voicemail in the database itself? You want to talk about poor database design...sheesh.. So, providing a uniform access model that doesn't depend on file paths, capitalization, or numbering is a bad thing? Read it, makes no difference, it's broken :) Whats broken? The table structure, did you miss it? Also, it doesn't say why the table structure is the way it is. It most certainly does. Seems you didn't read the REAME after all. Seems pretty simple and easy to use. This way if new config options are ever added, all you have to do to support them is to add a new column. And if all you are storing in most columns is 1 byte, it can't take up that much space. "are ever added" That's entertaining. Developers working on special tasks add fields that may not ever make it into CVS stable. I think I've read of two or more that are in CVS-HEAD right now. Flexible table structure isn't "we'll just add a field". Especially when the likelihood of new pieces of data needing to be tracked is high. I don't claim to know everything about database structure, but that is my job, and I don't believe a flat table is the way to go. Trust me, I just added six fields to a flat table that I wish now that I had never created. If I can't get the time to rewrite it, I am sure I'll need to add six more fields within the next few months. -- Andrew Thompson http://aktzero.com/ ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Realtime sipbuddies table structure why?????
> just poor data modeling How so? How would you change it? Are you aware that they have written code into app_voicemail.c that allows you to store the actual soundfiles for voicemail in the database itself? You want to talk about poor database design...sheesh.. > Read it, makes no difference, it's broken :) Whats broken? > Also, it doesn't say why the table structure is the way it is. It most certainly does. Seems you didn't read the REAME after all. Quoted from README.extconfig: It is designed to provide a flexible, seamless integration between Asterisk's internal configuration structure and external SQL other other databases the columns in your tables should line up with the fields you would specify in the given entity declaration. For example, an entity that looks like: [foo] host=dynamic secret=bar context=default context=local could be stored in a table like this: +--++---+--+--+-+---+ | name | host | secret| context | ipaddr | port| regseconds| +--++---+--+--+-+---+ | foo | dynamic| bar | default;local| 127.0.0.1| 4569| 1096954152| +--++---+--+--+-+---+ Seems pretty simple and easy to use. This way if new config options are ever added, all you have to do to support them is to add a new column. And if all you are storing in most columns is 1 byte, it can't take up that much space. -Matthew - Original Message - From: "Greg - Cirelle Enterprises" <[EMAIL PROTECTED]> To: "Asterisk Users Mailing List - Non-Commercial Discussion" Sent: Thursday, December 23, 2004 9:00 AM Subject: Re: [Asterisk-Users] Realtime sipbuddies table structure why? > At 09:53 AM 12/23/04, you wrote: > >It was written the way it is because that is how RealTime works. =P If you > >don't like the schema design, talk to Mark so he can rewrite RealTime for > >you. > > > >Read up some more on how RealTime works then you will understand why all the > >tables are designed the way they are. > > > >Read docs/README.extconfig > > > >-Matthew > > > Read it, makes no difference, it's broken :) > > Also, it doesn't say why the table structure is the > way it is. just poor data modeling. > > greg > > > ___ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Realtime sipbuddies table structure why?????
At 09:53 AM 12/23/04, you wrote: It was written the way it is because that is how RealTime works. =P If you don't like the schema design, talk to Mark so he can rewrite RealTime for you. Read up some more on how RealTime works then you will understand why all the tables are designed the way they are. Read docs/README.extconfig -Matthew Read it, makes no difference, it's broken :) Also, it doesn't say why the table structure is the way it is. just poor data modeling. greg ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [Asterisk-Users] Realtime sipbuddies table structure why?????
It was written the way it is because that is how RealTime works. =P If you don't like the schema design, talk to Mark so he can rewrite RealTime for you. Read up some more on how RealTime works then you will understand why all the tables are designed the way they are. Read docs/README.extconfig -Matthew - Original Message - From: "Greg - Cirelle Enterprises" <[EMAIL PROTECTED]> To: Sent: Thursday, December 23, 2004 8:01 AM Subject: [Asterisk-Users] Realtime sipbuddies table structure why? > > Is there some reason the sipbuddies table structure was > designed with sip config values as column names? > > Doesn't look very flexible > > It really should take the form of ast_config so when > a new sip feature is implemented, you don't have to > re-write the entire data structure too. > > > Regards > Greg Cirino > > > ___ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Realtime sipbuddies table structure why?????
Is there some reason the sipbuddies table structure was designed with sip config values as column names? Doesn't look very flexible It really should take the form of ast_config so when a new sip feature is implemented, you don't have to re-write the entire data structure too. Regards Greg Cirino ___ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users