Re: [foxboro] client server
- From: <Adam.Pemberton@xxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 28 Mar 2007 09:52:20 +1000
> Let's assume that we arrange to allow a command to publish the data
> in the configurators database. What format(s) should we consider?
>
> 1) SQL Tables
> 2) XML files
> 3) Excel workbook
> 4) Delimited ASCII files with headings
Alex
Thanks for requesting feedback on this issue. It has certainly
generated a lively debate from which some interesting ideas have come
out.
My first thought in response to your query was to say SQL Tables because
I would like to see it in Microsoft SQL Server. However what do you
really mean by SQL Tables? Some sort of ODBC interface? Some sort of
simple database that can be picked up by Microsoft Access? Or does it
mean SQL Server?
After watching the debate, my 2-cents worth is:
The priority has to be a format that everyone can use. Hence I think you
guys should publish in ASCII delimited files and XML. My reasons are:
1. Ascii delimited files can be used by all the UNIX gurus with
scripting or c-coding skills while XML is excellent for those who are
Microsoft .NET-centric.
2. Using either of these ASCII formats conforms to the KISS
principle which has to be good for everyone. Going Excel or SQL Tables
increases the complexity by an order of magnitude.
3. I would have no trouble writing utilities to convert XML to
Excel or SQL Server. Microsoft Visual Studio .NET has wonderful tools
for making this a straight forward task. I would be happy to publish
these tools on Cassandra. I'm sure the Unix gurus would similarly not
have too much trouble extracting data from the ASCII delimited files
into one of the common Unix relational databases.
Hope this helps.
Regards
Adam Pemberton
Site Electrical & Control Systems Engineer
Lihir Gold Limited
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
- Follow-Ups:
- Re: [foxboro] client server
- From: Corey R Clingo
Other related posts:
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- » Re: [foxboro] client server
- Re: [foxboro] client server
- From: Corey R Clingo