As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Is there a good tutorial or something similar for learning how to write Stored Procedures (for a PostgreSQL database). I'm a definite newbie when it comes to writing Stored Procedures at all, so the clearer and simpler things are explained, the better...
Thanks in advance...
You almost had it, but better start here plpgsql
Some will point that PL/pgSQL is not the only way to write Stored Procedures for PostgreSQL and they will be right (that's one of the advantages of Postgres), but on the other hand PL/pgSQL is nice and relatively easy to start with.
Note that obviously, here's a good place to start:sql-createfunction
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am Oracle guy with no experience in SQL Server and have been hired to make ERDs/DDLs for a job in SQL Server. I've finished the ERD and have presented DDL statements, but am now additionally being requested to do application logic as well. I enjoy doing application logic in PL/SQL and figure it won't be so hard for me to translate the logic into TSQL procs without much studying. Is this an accurate belief?
I know absolutely no TSQL.
TSQL is not difficult to learn. You should be up to speed in a day if you are serious about it. Just learn the basics and then the differences. Pick up some tutorials on the internet and do some practices.
You can pay attention to these and more
Conditional statement - IF, Loops
Cursors
Variable declaration
Assignment statement
Stored Procedures
Functions
and more
Like you could do a comprehensive search - TSQL vs PL/SQL, or Differences between PL/SQL and TSQL
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
My question seems to be dump, but because i was studying this new technique, i've found that NoSql has changed from its beginning, for example, in the beginning there was the problem of see your own update, and for example Facebook dident let users to update their comments due to the write once, read many
So, do i change all concepts that i've read in 2010-2012 tutorials?
Has NoSql beat the CAP theorem ?
I agree this can easily turn into discussion. I'll give brief answers from my experience to your two questions:
No, the concepts haven't changed. The landscape seems to be growing quite a bit as lots of companies get into the NoSQL space. Beware vendor promises!
No way. Just read this article this morning, it is a great explanation on some of the issues with the CAP theorem: http://codahale.com/you-cant-sacrifice-partition-tolerance/
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I've been looking around for a Mortgage Payoff calculator and it looks like the ones that are available are primarily commercial. Does anyone know if it already exists somewhere in script form that could be translated into another language?
If not, is anyone familiar enough with the logic that wouldn't mind sketching up the pseudo-code? I'll be able to script everything together once it's laid out but all searching I've done so far has only turned up results for creating an Mortgage (not payoff) calculator.
In addition to the obvious utility, hopefully putting this logic out there will help people better understand how their mortgage is being calculated.
http://www.r-bloggers.com/mortgage-calculator-and-amortization-charts-with-r/
The amortization shows you the remaining principal which is the same as the payoff amount.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Can you please help to choose from Coredata or sqlite ??
Which one is better ? As I have complex query in database.
This blog will help you a little
http://blog.mcohen.me/2010/06/19/why-i-chose-sqlite-instead-of-core-data/
The answer, of course, is that "it depends". They both have their advantages and disadvantages depending on what you want to achieve.
Check out this article, and others, on choosing between the two: http://answers.oreilly.com/topic/1959-when-to-use-sqlite-instead-of-core-data-on-the-iphone/
Sqlite is a RDMS system and involves SQL and while CoreData is a object-oriented programming within xcode.. Both deal with a lot of data in the database. Both have their own way of writing and saving to the database. You need to know their specific ways... On deciding on which to use, it really depends on the circumstance you are in.. If you are using a simple query or have very little data in the database, you could use plist or userdefaults. The choice is yours because you know best what you need...
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Where ever I read I see experts writing to stay away from typed datasets and use the entity framework or similar.
On the other hand almost every ado.net book I read will show first how to use datasets and some of them only use datasets, that gives me the impression that its not bad. if it is why teach it for the new programers?
All depends on what you want to do with the data you're pulling from your DB.
I use a DataSet to load data in to a Crystal Report because it plays well together. Anywhere else in my app i use mostly anonymous types. Either way i use the EntityFramework to pull the data from my DB. I get results much faster that way than using ADO.NET and DataSets. If i need raw performance I use ADO.NET. For batch updates for example.