It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
i'm just curious. so i ask this particular question about SQLite. I haven't use this type of database extensively. but care to explain what is the basic different between SQLite and Mysql ?
The reason behind all of this is i just want to know whether it possible to use it to store wordpress data and act as a database ?
SQLite is a file database. There is no running process or anything, it's literally just a regular file on your disk. MySQL is a full fledged database server, something that has to be run independently. SQLite is best suited for when applications need a small database to store settings or data.
You could do it with SQLite, but SQLite isn't really meant to be used concurrently (ie, by multiple users accessing it at once). So unless it's some dinky internal site that will only be accessed by a couple people, I wouldn't recommend it.
Currently, the only database supported by WordPress Version 2.9 is MySQL version 4.1.2 or greater.
Technically, you can use WordPress with SQLite. If you don’t have much traffic it is an option.
SQLite is an in-process or desktop class database. MySQL is a server class database. I'm a little notorious here for promoting server-class engines over desktop or in-process -class engines for web sites, because no matter how well you do at your in-process database engine you are going to have concurrency problems when a whole bunch of people try to access your site at the same time.
However, I think in this case you might do just fine with SQLite, as long as you are very careful about what plug-ins you install. The reason is that you're likely only going to have one person updating your wordpress blog, and probably in-frequently at that. So as long as you're careful about using plug-ins that don't get to write to the database for every visitor, sqlite should do fine.
It's trivially easy to install a copy of MySQL and a webserver onto any machine, so while you could use SQLite, it would be a lot more difficult than simply grabbing a copy of MySql and installing it.
WordPress does not support anything but MySQL out-of-the-box, but it is possible for a database-plugin to replace that support with just about anything, if it really wanted to.
If you want to test this locally or something, just grab a copy of XAMPP and install WordPress on that. Easy.
Related
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'm not going to make a big long rattle on this question about what I've tested and number crunching. I'm more interested in actual up-to-date practice performances.
I've read tons of articles already and some of them are pretty skeptical or either very pro to one library. I'm currently testing a bit with gorp, yet I have no clue how to compare the performances of such a library towards others.
I know gorp is an extra layer that tries to add ORM to the basic SQL driver/implementation, but seeing Go's extremely clear code and being it very close to the bone on everything it does. It's not like with PHP/Python/JAVA what I'm used too, where you have to navigate through endless layers of complexity to actually see what a package does in its essence.
So my question is if anyone can share (benchmarks are always welcome :) ) their experience and knowledge on this subject.
I don't think a NoSQL-type solution is an option for my projects. All my projects always strongly depend on business logic and intertwined relationships. I also wonder if Postgres will be a win over MySQL. With Django (Python) I noticed significant performance gain using Postgres, but I never found prove on that matter if it was due to the Postgres core implementation or just Django's way of using the wrapper.
Small update
After rereading the question I noticed I kind of missed the actual goal of it. I'm actually looking for the most suitable SQL solution that will least slow down Golang itself. I know the SQL runs concurrent, but also concerning heavy traffic when running it as a web service. I won't be really bothered to drop the ORM part again if that will get me major gain on performance.
If you need to use an ORM sqlx or gorp are good Go options. Personally, I am a bit old school and I would rather for a given type Foo, I would rather write a FooDB struct that implements a FooDS interface. Everything in your app just uses FooDS. (DB = database, DS = datastore)
Your FooDB implementation could be using any number of underlying technologies MongoDB, LevelDB, SQL, etc and it can change as your app changes and this change is transparent to the rest of your app (since the rest of your app uses FooDS).
I would default to using database/sql (Prepared statements, etc) and the most mature Go SQL driver is Julien Schmidt's MySQL driver: https://github.com/go-sql-driver/mysql
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
I'm making an app witch allows you to make a video call from one device to another. I've done a bunch of searching around and I haven't been able to find something that tells me how to get the video and audio from the iPhone camera and send that live stream to a web server to connect to another device. I have finished every other element of the app so this is all I need to finish.
This is very complicated! I assume you don't really want to code the whole thing because that would take you forever.
I'll try to brief what you need to have to make that happen:
1. Client code - You must implement an iPhone client, Client would have to connect to some SIP server, initiate calls, rings (through push) and so on...
2. SIP server - This could be really simple (if you buy this service, Usually you pay per time or for number of calls your system could support in parallel) or really complex if you want to build this service yourself (there are companies that sells those products/services and do just that).
Where to start?
If you are willing to use open-source (if your client-side could be also that's the simplest way), Or just understand the scale of what you are trying to do I suggest you try linphone(https://www.linphone.org).
They have open-source SIP Client for iPhone (and almost for every platform) you can use for free (if you are willing to open-source yours, Check the license there). You could also buy the code so you can keep your code secret but that is very expensive!
For server side there are a lot of services you can use, Also linphone has their own Server you can use for test free. So you can try and use before you go to a big server.
In case you don't want to implement the technology and want to start building your app with your wonderful idea, I suggest you use 3rd party that gives you everything including a simple iOS SDK, So you can integrate in minutes. Check those out: Rebtel, Twilio etc. I don't know if they have video yet but I'm sure if not they would have soon. Btw, Rebtel is totally free so there is no reason not to start with it (to be honest I never used Rebtel and don't know if it's great or not).
In my opinion if you are just starting and you don't have a big team with experience with this it would probably be a good thing to start with the last option (3rd party full service) and start building your idea because otherwise you would spent your time too much with a very complex technology.
Hope this helps.
It's complicated, likely more than you imagined.
You may need to license and encode H.264 and AAC.
You'll need to understand RTP and SRTP.
You may need your own servers for SIP, STUN, TURN, and ICE.
i'm not happy with this answer but I don't want you to underestimate the magnitude of your project - it is not trivial.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
This semester, I'm learning database using the isql*plus (oracle10g), but that needs to install a server on the pc first so it will function well. That really lags my pc, and I just need to write simple code snippets, and view the output.
I've searched the internet for the isql*plus, found something called (altova database), but needs money.
Searched again for a C compiler, but found an old compiler (that's fine by me!) and found the dll libraries for the openGL, but don't know how to bind the library with that lousy compiler program I'm using; maybe a C compiler suitable for game programming is the best.
And I've been starving to find a C programming language compiler (World Widely Known), with the suitable OpenGL dll libraries.
If you have to have Oracle, then check with your school to see if they've got a test Oracle server setup for students to use. If not, then get together with some friends in the same class and dedicate one machine to be your shared Oracle server. Alternately, just spin up the Oracle instance on your local box when you need it, and spin it back down when you don't.
If you are just learning SQL, then try something lighter like MySQL or SQLite. Both are free and much less resource intensive than Oracle. From a student perspective, the SQL language is similar enough. When you get into big applications and database administration, the differences between the different flavors of SQL servers becomes more important.
GCC is your go-to C/C++ compiler. Whether there is OpenGL support for it depends on the platform you are using. I can't tell if Visual Studio is free for students or not, but there is a 90-day free trial. That should be more than sufficient for a semester's worth of coding.
This semester, I'm learning database using the isql*plus (oracle10g),
but that needs to install a server on the pc first so it will function
well.
Every version of Oracle you install locally will need to install a server to function at all, not just to function well.
And I've been starving to find a C programming language compiler
(World Widely Known), with the suitable OpenGL dll libraries.
iSQLPlus is a web-based utility that you can use to a) connect to a server, not necessarily running on your local PC, and b) enter SQL statements to be run on that server. It's not a compiler in any sense of the word. Whether you can connect to an instance of Oracle running on a different computer depends on a lot of TCP/IP and database security settings.
As a rule of thumb, it's pretty odd to need a C compiler when your goal is learning any SQL database, including Oracle.
Closed. This question is opinion-based. It is not currently accepting answers.
Closed 9 months ago.
Locked. This question and its answers are locked because the question is off-topic but has historical significance. It is not currently accepting new answers or interactions.
I read this term a lot. What exactly is a legacy database? I ask because I had thought it meant an old database like dbase or rdb, but I don't think I'm right.
When looking at RoR or Django and "legacy database" integration, what does legacy database really mean? Is it different than a generic term "legacy database"?
In the general context, it can refer to any of the older database technologies.
In a more specific context, it can refer to a database system that was inherited by a team from previous project owners.
legacy: anything from the past that keeps coming around to haunt you.
A legacy database is generally something that you will have to inherit and base some of your design decisions around. Most companies that put out work may already have some other (usually horrible) solution and you need to give them a bigger and better product...
BUT
It has to work with all of their old legacy data. The company is not going to want to manage two different applications just so they can keep all their old records. You will need to develop your solution to be able to migrate the data from the legacy system over into your system. This can have a massive impact on the overall design of the new database, because it cannot stray too far from the previous without introducing a lot of problems in terms of data integrity.
It's usually derogatory in my experience:
Something no-one wants to touch in case it breaks
Databases that can't be maintained (say that SQL 6.5 box lying around)
Someone else's badly designed and implemented database
Something that someone is trying to replace
Supported by the 93 year old wierdo
If it's in-use but still has maintenance or development activities, it can't be legacy...
Edit:
Given the age of the SQL language and the RDBMS, everything is legacy (including my new system due next year) compared to the software listed. At what point does Ruby turn legacy from the database perspective..?
We mostly use the term 'legacy database' as a db schema we can not 'easily' modify without breaking other software/systems using this schema.
this sums it up pretty well.
[edit] Broken link. Here's the quote from FOLDOC:
Legacy System -- A computer system or application program which continues to be used because of the cost of replacing or redesigning it and often despite its poor competitiveness and compatibility with modern equivalents. The implication is that the system is large, monolithic and difficult to modify.
If legacy software only runs on antiquated hardware the cost of maintaining this may eventually outweigh the cost of replacing both the software and hardware unless some form of emulation or backward compatibility allows the software to run on new hardware.
Flat file, hierarchy, and network databases are usually referred as legacy databases. They represent the ways people used to organize information in prehistoric times — about 30 years ago.
Legacy is used to denote the old thing. legacy database is something which continues to be used because of it cost of replacing and redesigning it.
In general context refers to old code inherited. Tipycally cobol code.
It is used for code which it is still used for historcal reasons.
It applies also for DB schemas
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
Ok, let's put it in a more mildly: Is cgi (common gateway interface) legacy?
yes? no?
Under what circumstances would a project starting today (one that does noot have to interact with legacy systems or libraries) use cgi?
It's far from dead actually. Despite the overheads, many virtual web hosting companies are now running PHP as CGI for security considerations, because it can be used with suEXEC. suEXEC means that your scripts execute under your actual Unix user privileges, and thus are restricted by the operating system's privilege separation. This is a much more robust security model than the PHP-specific open_basedir alternative.
Also, CGI is a really simple and quite versatile interface, support for it is never going out from web servers. Many newer interfaces like FastCGI and SCGI inherit the way that CGI passes HTTP headers and other variables to the web application and back. Even PHP's SAPI mimics this with its $_SERVER variable. So CGI is not going away, it is just being built upon.
Legacy? Absolutely. Dead? Well, it's on life support. I doubt it will really "die" in the forseeable future. You might still use CGI to write a very small sort of script if you've got a server with no other means of running a webapp and you're too lazy to configure it up.
What's another reason? Maybe you've got a program that leaks memory or resources like a sieve but you need to run it anyway, so you make sure everything is cleaned up by ending the process every single request...
But seriously, for things that really matter, I think the benefits of moving to any sort of system with persistent processes outweigh the costs by quite a bit. And in my experience, it encourages writing better-organized code as well, because the kind of initialization you need to have a nicely modular application translates to "unacceptable startup time" in a CGI environment.
It is not quite dead. But fcgi looks like much better approach. Though not officially supported by, say, Apache. You need to use side mods to get it to work.
I wouldn't consider CGI dead either. After all, it is supported by all major web servers.
One reason not mentioned for starting a CGI project might be Intellectual Property protection. For example you may decide to write a CGI program in C++ and allow your customer to install the application on a server not controlled by you.
Maybe your legacy product has tons of business implemented as libraries. (.dll, .so. .lib. .a etc) In this case, it may actually be faster to market to stick with c/c++ when implementing a web interface.
Perhaps, you work in a Delphi shop? If 10 out of 10 engineers in your shop write Delphi, writing your new application in PHP may not be your fastest path to market.
So, in short, many variables come into play when deciding what tech to use for you new product including:
Who's your customer?
What is your starting point?
What are your assets and resources?
What do you enjoy?
What does your software need to interface with?
How will the application be deployed?
CGI is not very well suited for high performance.
But my advice is to ignore that, write for a language or library that supports multiple SAPIs, and then use what fits best for each situation.