[Informatics] Database choices for U3AoS1

Vella, James jvella at mackillop.vic.edu.au
Mon Jan 11 14:16:54 AEDT 2016


Hi Richard

My gut feeling would be to ditch FileMaker and go with either an SQL or Access backend for your database. My reading of U3O1 is that a solution is required to be produced (ie. Backend and UI). While the learning curve may seem big this year, you could always introduce SQL or Access as part of U2O3 this year and not have such a steep one next year.

My guess would be that Access is used more than FileMaker (given the widespread availability of Office products) and follows a similar syntax to SQL when you get past the wizard-based stuff.

For the U3O1 SAC, as I said, my reading is that a solution is required to be developed using a RDBMS - that comes directly from the Outcome statement.

Hope that clears it up for you.

James.





[http://www.mackillopwerribee.com.au/webimages/email_sig_logo.png]


James Vella
Digital Technologies Learning Area Leader eLearning Leader
MacKillop College
Russell Street Werribee VIC 3030

T:  +61387345200
F:  +61387345261

webpage<http://www.mackillop.vic.edu.au/>    |    map<https://www.google.com.au/maps/place/MacKillop+Catholic+Regional+College/@-37.898495,144.667368,14z/data=!4m2!3m1!1s0x0:0x86ef7579bb65ae76?hl=en>


Please consider the environment before printing.
________________________________
From: informatics-bounces at edulists.com.au [mailto:informatics-bounces at edulists.com.au] On Behalf Of Fox, Richard R
Sent: Monday, January 11, 2016 12:56 PM
To: informatics at edulists.com.au
Subject: [Informatics] Database choices for U3AoS1

Hi, Happy New Year everyone!

I'd like to thank everyone for the excellent contributions made by members of the list, it's a great community.

I'm interested to see what choices people are making for the database to be used in U3O1. Last year I used FileMaker Pro, which I have some previous experience in from many years back, but I have been working extensively in mySQL since then for my own projects.

It seems the choices are:
1) FileMaker Pro - easy to get started, good for form design, but confusing when trying to separate database design (tables, fields, types, validation) from UI which is done through layouts. Using portals as an abstraction for relationships is also confusing. I found students could get up to speed quickly with layout design but explaining queries was really hard because it is all UI-driven, and finds are stored rather than scripted. Also, it is very relaxed with data validation, so it will happily let you do calculations with price values for example that have been stored as a Text data type. Also, I don't think it is really used much in the real world these days?

2) SQL - I think this is really a better way to teach how a database is structured, so that one can see it is just a data store and then one sets up relationships between tables. It also enforces data types properly. I found even whilst teaching FileMaker last year it was still easier to explain queries using SQL statements. But is it too steep a learning curve?

3) Microsoft Access -  I have not used this before, and really don't want to invest time to learn it when I have other choices. From my understanding it is not widely used anymore, much like FileMaker?

Of these, I'm still leaning towards using mySQL because (a) it lets one concentrate on correct RDBMS design, without UI complications or abstractions, (b) it is easier to check SQL scripts for correct operation (c) it is far more relevant these days being the common foundation of web apps using PHP and mySQL back ends, (d) it is free and cross-platform.

Where I'm still not clear is whether the study design says they have to build a full application using a database (so, it has a UI), or whether they only have to demonstrate correct table and relationship design. If they are expected to make an end-user application then they would need to use PHP in web pages to interact with the database, which would increase the complexity of the task. But correct design, use of queries and validation can be demonstrated through interaction with the SQL interpreter. The other design requirements of the outcome could still be met by layout diagrams, test plans, etc.

Looking forwards to some insights from others.

Thanks,
Richard
--
Richard Fox
Teacher of IT and Science
eLearning Coordinator
Learning Technologies and ICT Infrastructure
Diamond Valley College
9438 1411

Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Training.

CONFIDENTIALITY NOTICE
This e-mail contains confidential information intended only for the use of the name addressee. It may also be subject to professional privilege. If you are not the named recipient any disclosure, copying, forwarding or using any part of this e-mail or its attachments is prohibited. If you have received this e-mail in error, please notify us by telephone on 0387345200. MacKillop College does not warrant that this e-mail or any attachments are error or virus free and recommends that all attachments be checked for viruses and other defects. Similarly, MacKillop College does not warrant that this e-mail has been free of interception by a third party and may store the content sent to us, if we believe that we have a legal requirement to do so.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.edulists.com.au/pipermail/informatics/attachments/20160111/5bee3225/attachment-0001.html 


More information about the informatics mailing list