Hi all !
It would be a great idea that integrate a fully odbc compliance for SQL Server or Mysql Database. I wish organize all my mp3 in a server database and i would appreciate that VDJ "knows" how to find my store of mp3 !
Thanks for all who want to discuss about that !
It would be a great idea that integrate a fully odbc compliance for SQL Server or Mysql Database. I wish organize all my mp3 in a server database and i would appreciate that VDJ "knows" how to find my store of mp3 !
Thanks for all who want to discuss about that !
Posted Sun 26 Jun 05 @ 4:38 pm
That's a really great idea (and fun mainly). Would be great to create a computer with mysql and php to view and edit your song information, and vdj tap into that same database and use it in it's program.
All vdj has to do is tell us what fields it will look for (song_name, artist_name, etc.) and you could make the database as alaborate as you want to keep thing maintainable at your own computer.
As I said, would be fun, could be great...
All vdj has to do is tell us what fields it will look for (song_name, artist_name, etc.) and you could make the database as alaborate as you want to keep thing maintainable at your own computer.
As I said, would be fun, could be great...
Posted Mon 27 Jun 05 @ 4:51 am
maybe a little off topic, but mysql is for direct filesharing? i need a way to share mixes that are fairly large in size, and not pay if i can avoid it. any other suggestions to do this?
Posted Mon 27 Jun 05 @ 5:50 am
mysql is a database software, not a filesharing program
bbj
bbj
Posted Wed 29 Jun 05 @ 12:08 am
ta :)
Posted Wed 29 Jun 05 @ 1:20 am
clownius, DC++ may be what u r looking for
http://dcplusplus.sourceforge.net/
bbj
http://dcplusplus.sourceforge.net/
bbj
Posted Wed 29 Jun 05 @ 2:30 am
Virtual dj has the SMARTEST (is the word right?) database system, with 2 separete databases allowing you to build/rebuild the database faster than any other dj program...
...changing paths outside of the program, swap hard drives, no problem..
You'll be ready again in minutes, just by rebuilding the search database.
The FASTEST search engine by far.
Please leave it the way it is.
My only suggestion : to add a "user" (or 2) column for rating tracks etc.
The comment column is not enough..
...changing paths outside of the program, swap hard drives, no problem..
You'll be ready again in minutes, just by rebuilding the search database.
The FASTEST search engine by far.
Please leave it the way it is.
My only suggestion : to add a "user" (or 2) column for rating tracks etc.
The comment column is not enough..
Posted Wed 29 Jun 05 @ 2:55 am
yes a 5 star rating thing would be cool...
cheers for the link also dj bbj, what i was looking for :)
cheers for the link also dj bbj, what i was looking for :)
Posted Wed 29 Jun 05 @ 4:42 am
But now, a few years later, the demands on a XML-Database are grown.
I would be nice, if it would be changed in a (my-)SQL-Database in order to achieve the performance, the database had, as it was a little smaller.
The search for a title takes me 5 seconds after typing each single letter, so I can“t work with this.
I would be nice, if it would be changed in a (my-)SQL-Database in order to achieve the performance, the database had, as it was a little smaller.
The search for a title takes me 5 seconds after typing each single letter, so I can“t work with this.
Posted Sun 23 Mar 14 @ 3:14 am
You could write a php/ruby/node ect.. script to read the xml library then add the tracks to an sql database. but I don't know how you would ever load a track from sql without an interface on your computer that allows you to drag and drop files. Best advice is to section your library into different occasions and have VDJ ignore some of the drives when they aren't needed. You would just need to create a few new drive letters.
I think SQL is only a serverside database, Another option could be to use a NoSQL database like mongodb which stores everything in JSON and can be read in any programming language. Reading JSON would be much quicker than XML or SQL
I think SQL is only a serverside database, Another option could be to use a NoSQL database like mongodb which stores everything in JSON and can be read in any programming language. Reading JSON would be much quicker than XML or SQL
Posted Sun 23 Mar 14 @ 5:48 am
5 seconds each letter is way too long.
I have never experienced this long delay.
I have never experienced this long delay.
Posted Sun 23 Mar 14 @ 12:48 pm