Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I'm making a website for a group that needs a database. The data is going to store user information among other things. I already know PHP and could easily do it in PHP, but to further myself as a developer, I'd like to learn a language like Ruby. I know how to use databases in PHP. But, when writing Ruby, can I use SQL databases?
We don't know how you call your database in PHP.
Many PHP users use MySQL and call sql statements with the embedded mysql driver,
and then iterate over the results.
You can do this also in Ruby. The mysql driver is not embedded, But you can easily install it with RubyGems. You need the mysql2 gem.
https://github.com/brianmario/mysql2
But if want to be more object-oriented, there is the framework "Ruby On Rails" with "ActiveRecord" for database connection. Here you don't write SQL directly, instead you specify what objects you want to have or store (except in rare edge cases, where you still can write sql)
This needs some learning time. But then it is lot less coding, code is better readable, and security errors like are also easier to avoid.
The basic answer is yes - you can do something like that using Ruby and a framework like ActiveRecord or Sequel, but this far too broad for StackOverflow.
Good afternoon.
Depends on the speed you need .
1) If you need quickly - write on PHP
2) If you have some time and want learn Ruby On Rails, ActiveRecord etc. ... buy some book for beginner, read doc and step by step create application
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I understand that in general PDO scripts are cross compatible i.e. generally changing the connection string should work.
In the past I've spent hours searching online after changing a PDO script connection string from MySQL to SQLite as this isn't the case, some things don't work the same (I remember an issue with row counting or something).
So should changing from MySQL to Oracle be generally simple, or are there things to watch out for as in the SQLite case?
So should changing from MySQL to Oracle be generally simple, or are there things to watch out for as in the SQLite case?
There are things to watch out.
More seriously, beside basic SQL query, each RDBMS has its own set of specific features that have to be taken into account. Just to give one example, if you want to limit the result set to one row only, MySQL provides the LIMIT clause. But for Oracle up to 11g, you need a sub-query for that purpose.
If you really need cross-vendor support, you probably should take a look at some library providing database abstraction layer whose job is to allow you to write database-agnostic code. PDO isn't such a library. But Doctrine DAL, Zend_db and many other are.
It is now considered as off-topic to request suggestions for a tool here, but take a look at this old question if you need few pointers: Best PHP DAL (data abstraction layer) so far
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm in the process of learning ASP.NET and I'm having a few difficulties with certain things. The main difficulty I have right now is accessing data from a database. Usually in PHP in the model I'd just write an SQL query for a specific model function and then that'd query the DB and return the results I want to the calling controller. Is doing this fine in ASP MVC? And if so how do you do it? The tutorial I was following started using scaffolding and I want to avoid that as I want to fully understand how it all fits together.
I myself started in PHP and gradually moved to .NET. The way I manage my database is via Entity Framework. I know it may sound like you've got to learn yet another useless thing, but it is actually very simple. If you just want to learn the concept: use code first approach.
This is how it works: you create a bunch of models (that you will need anyway its called Model-View-Controller for a reason) that are nothing but objects. Those models are used to build your database. So you no longer need to set up the database manually (e.g. phpMyAdmin). It sounds quite amazing but that's how it works and then you use LINQ (or LINQ-to-SQL) to get queries.
This an example of a LINQ-to-SQL query:
var query = from u in dbContext.User where u.UserID == 1 select u;
This will come useful later on as well when you want to validate information etc. Here is a great starting tutorial (just watch the first 4 of those videos):
https://www.youtube.com/watch?v=Z7713GBhi4k&list=PL6n9fhu94yhUPBSX-E2aJCnCR3-_6zBZx
Moving from PHP to .NET is a big move, but it is really worth it.
Good Luck!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am planing to create a project in PHP which will be connected with MongoDB due to the MongoDB flexiblity. The goal is to store in the MongoDB some documents that can vary during the time and with MongoDB we can add extra data without changing the structure of the DB, which is not the case with MySQL.
My question is: Is it a good idea to use MongoDB as the unique DB, or should I use it together with MySQL. The MySQL for the data as user login info etc, and the MongoDB for documents.
I am planning to use the Symfony2 framework or the CakePHP.
Thank you in advance.
I think it's a good idea to use MongoDB as the unique DB. It's a lot easier to use one database and MongoDB can handle the user login info just fine. You may want to change some collections over to MySQL in the future though.
MongoDB is pretty new compared to MySQL so it does have some drawbacks. For one, MongoDB is not as reliable as MySQL so your bound to run into a few bugs. It will also be harder to find answers to your questions as MySQL is far more popular.
MongoDB is great, but you must make sure you have the time to get to know it. If your short on time or are making it for a client, MySQL is probably a better option.
If a single DB server can handle the job, I'd stick to MySQL. The frameworks you are going to use have this DB in mind.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am new to web development. I wanted to know what DB will be best suited for PHP for a requirement of Web Application. Till date i have worked with Oracle database and have found it bit slow for applications which need quick response time.
I was looking into MongoDB and MySQL and couldn't decide which to pick.
Please suggest which will be the best option also if any other option will be better suited.
Thanks in advance.
I am new to web development. I wanted to know what DB will be best
suited for PHP for a requirement of Web Application. Till date i have
worked with Oracle database and have found it bit slow for
applications which need quick response time.
The answer is quite subjective as there are lot of factors need to be considered before jumping to a conclusion. I will lead you to good articles which can add some points in taking a decision.
http://www.mysqlperformanceblog.com/2013/10/22/designing-one-many-relations-mongodb-vs-mysql/
mongoDB vs mySQL -- why one is better than another in some aspects
MySQL vs MongoDB 1000 reads
There is nothing called best, every technology has its own pros and cons. It all depends upon what you are comfortable in working with. I would choose PHP/Java with MySQL anytime ahead of DOT NET with Sql Sever, just because i know the former well than latter.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
since about two years ago, I did find my interest in code (Hardware/Sytems/Web) and now, I've found a project which motivates me a lot (It takes all my free time indeed).
Starting this point and because my project could soon switch from a free time project to a daily job, I'm currently developing a mockup of this project based on PHP/MySQL and JQuery.
Even if I'm a true Python/MongoDB lover and a System Engineer, I did prefer those technologies to build up my mockup because of their simplicity to build a complete functional private stack at home.
I'm pretty advanced on my mockup and it seems to work as I want it.
Now I'm wondering if, about your point of view, would have been better to start to build my mockup using directly the targeted technologies (Python/MongoDB) rather than to use the easy PHP/MySQL couple to do it?
Obviously, because I plan to made this project my daily job, I had to have something visually functionnal to be able to raise a little bit of money, and about me, using an easier stack it's more easy, but I would like to have your feedback on this kind of question.
The idea that PHP/MySQL is easier or simpler than say Python/MongoDB is just inconsistent.
If you compare for example, Django (the most popular python web framework) with symfony(PHP) you will find that they are almost identical in terms of features and architecture (symfony is actually slightly more complex but also has more very advanced features).
For mockups, if I were you, I would use solely HTML/jQuery/CSS.
Build your pages just like you would like to have them in your beta version, use jQuery to load sample data written in json.
That's all you need. You can even find WYSIWYG application to speed up the process.
Later on, you can build the back-end application using either python or php, it won't matter.
The integration process will be identical, create your models, create the controllers, and use the HTML you already have as templates.
Building your app in php/mysql then convert it to python/mangodb will make you rewrite almost all the code simply because python is so much different from php (easier I would say too, but that's just my opinion) and because mangodb is not a relational database meaning you will have also to rethink partially your architecture.