design - Coding Database web apps -
This is something misleading from me to explain here. When I try to learn a new language, I go with some of these steps:
1) Simple Hello World Program, Math Program, Counter Program
2 ) The interplay between pages is using data (RSS / Atom) from other websites using their APIs.
3) Storing or manipulating the data (mysql / postgresql may call you as database).
Now the third part of handling and manipulating data is a bit confusing to me and it seems that I can not go into the coding. Developers may be, but I want to know how I can imagine this structural way so that the programming database app is easy and I can move without fear of codes and database connections. I mean that even if the language is not used, the steps to make the database web app are quite normal (driver / failing table data / storage etc.) but I can not see it.
For example, how can I create an APL which stores certain information like adobei using JSP / circlet or PHP. What do I need to think before creating a web app? I hope my question is clear.
I've always made data access content very difficult, so I try to make a good one The intangible data access layer that works most for me is a typical database call like this (and I think it's mostly fit for web oriented platforms):
- Create a database connection and Open
- Create a database command object
- What you do to the object (I.e. give this a SQL command, or name a stored procedure to execute)
- Give the parameter the parameter to work (
- execute the command
- Do something with the results
- At some point,
to create a Data Access object for yourself, Does stuff, do your cleaning (including disposal of items, database transactions) No connection clamp etc.) only to have the required standard database operations should be some public methods, such as "Akgikyutstorprokras" or "Akgikyutsclstetment". In this way, working with a database is boiled to work rather than a big, tedious disturbance.
Comments
Post a Comment