02242005 1155 GMT-6
If you have a mysql database created and used on a newer version of
mysql and you have a computer with an older version (created on 4.1 and
backward to 3.23.49) can the db be used in general?
Wade
--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org
--=_alternative 0063539085256FB2_=
Content-Type: text/plain; charset="US-ASCII"
I am not sure what you mean by the term "used in general". Do you mean
"can you copy the 4.1 generated files from one machine to another and
expect the 3.23.49 server to handle them?" That answer would be "no".
Can you provide some details on the setup you are trying to implement or
what you meant by "used in general"? I am sure we can help you to work out
the details or at least point you to documentation that explains any
conversion issues in better detail.
Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine
Wade
> 02242005 1155 GMT-6
>
> If you have a mysql database created and used on a newer version of
> mysql and you have a computer with an older version (created on 4.1 and
> backward to 3.23.49) can the db be used in general?
>
> Wade
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=sgreen@unimin.com
>
--=_alternative 0063539085256FB2_=--
--=_alternative 0065DC3785256FB2_=
Content-Type: text/plain; charset="US-ASCII"
Now, that's a horse of a different color. You should be able to run the
same (or almost the same) data structure on both versions. Check the docs
to see if there have been any data field types added or changed between
the two versions. The data files themselves are not compatible between
those versions but that is not what you are asking about, is it?
mysqldump will be your friend. There is an option to tell it which version
of MySQL you are generating the dump to be read into. Don't forget about
max_packet_size and I do not know off the top of my head if 3.23 accepts
the "extended INSERT" format. So, you may need to use a lot of different
options/settings to get the dump file compatible with a 3.23 server but I
know it is possible.
Here's the manual for mysqldump:
http://dev.mysql.com/doc/mysql/en/mysqldump.html
Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine
Wade
> 02242005 1220 GMT-6
>
> Well, you answered my question. I was thinking .... well... anyway,
> I have this customer database I created for this guy and I have 4.1
> and he has the 3.23 and he thought that Was the latest release. He
> didnt know and I just didnt question him hard enough about it.
>
> Thanks.
>
> Wade
>
> SGreen@unimin.com wrote:
> I am not sure what you mean by the term "used in general". Do you mean
> "can you copy the 4.1 generated files from one machine to another and
> expect the 3.23.49 server to handle them?" That answer would be "no".
>
> Can you provide some details on the setup you are trying to implement or
> what you meant by "used in general"? I am sure we can help you to work
out
> the details or at least point you to documentation that explains any
> conversion issues in better detail.
>
> Shawn Green
> Database Administrator
> Unimin Corporation - Spruce Pine
>
>
> Wade
>
>
> 02242005 1155 GMT-6
>
> If you have a mysql database created and used on a newer version of
> mysql and you have a computer with an older version (created on 4.1 and
> backward to 3.23.49) can the db be used in general?
>
> Wade
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=sgreen@unimin.com
>
>
>
>
--=_alternative 0065DC3785256FB2_=--